![]() ![]() 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. Your engineers are still on their tech stack. They would need to learn a bit but they wouldn’t have to learn something from the ground up. You can share your networking logic, caching logic, business logic, and application logic according to your needs. You can configure it depending on your use case but in this article, we’ll cover how we can share all of those. That’s it! This has been what came out on my journey in Kotlin Multiplatform. Thanks for reading! I hope you enjoyed! Resources I hope someone gets something out of this or maybe make someone try it out.Clean Architecture example with Kotlin Multiplatform.Kotlin Multiplatform for Clean Architecture.Targeting iOS and Android with Kotlin Multiplatform. ![]() Kotlin Multiplatform Project for Android and iOS: Getting Started. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |