giftsposa.blogg.se

Kotlin Multiplatform Mobile used in production: If you are already using Clean Architecture with one of the MV* presentation patterns you’re good to go with KMM. You can share everything from the data access layer by Interactors/UseCases to the data presentation layer (ViewModel). If you structure your code properly, you can share up to 85% of the code between platforms. You write everything once, test it once, and then you can distribute it across the platforms you need.īut not only that. Kotlin Multiplatform’s libraries let us implement a data access layer. KMM gives developers access to many well-tested and well-tried libraries that let us: Android Architecture Components (primarily ViewModel)Īs always, PRs or suggestions for better way of implementing any of this are very welcome (can respond to tweet shown at bottom of post)! iOS SwiftUI Code struct ContentView : View Update Īdded commit that starts to make use of new Kotlin/Native multi-threaded coroutine support ( 1.3.Even though Kotlin Multiplatform Mobile is in the alpha stage a lot of components are stable.The Kotlin/Swift code below constitutes majority of code used in the project (I did say it was minimal!!). Note: You need to use Android Studio v4.0 (currently on Canary 6) to build Android app. The project uses very basic API to show list of people currently in Same approach outlined in SwiftUI meets Kotlin Multiplatform!). To try out use of Jetpack Compose for the Android app (with UI being developed on iOS Project and thus PeopleInSpace was created. However I thought there’d be value in creating a more minimal project that would allow clearer illustration of key moving parts of a multiplatform Of various explorations I’ve done in to the use of Kotlin Multiplatform. In previous posts I’ve used GalwayBus repo to illustrate results