You can share your networking logic, caching logic, business logic, and application logic according to your needs. They would need to learn a bit but they wouldn't have to learn something from the ground up. Your engineers are still on their tech stack. Instead of moving into another framework, you just have to share what you need to share and stay true to the platforms that you're building on. Kotlin Multiplatform is Jetbrain's take on the cross-platform world. This is where Kotlin Multiplatform would come in. If you want to do something at the native level, you won't be able to because you're tied to what their framework can give. Also, the new framework is just a bridge to the native world. This would require you to re-train your engineers to get them accustomed to the new framework. There's no doubt that it can do its job however, it would require you to rewrite all of your existing code and move on to their world.
One not-so-new kid on the block has been gaining traction. To address these problems, we have different cross-platform technologies such as React Native and Flutter, two of the most notable cross-platform frameworks as of this writing. You may or may not have the knowledge of Android and iOS development but having them would help you grasp the topic.Īndroid and iOS apps are usually the same when it boils down to their functionalities yet we still end up writing them both in different languages and tools just so we can have it on one platform and the other. This article aims to discuss code sharing between Android and iOS using Kotlin Multiplatform.
0 kommentar(er)
