Kotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
summary
Two KMM apps get built over two years, one sharing only networking and local storage and the other sharing a coroutine ViewModel layer, and both ship successfully though iOS integration costs more time. The stack uses Ktor, SQLDelight, OkHttp, Kotlin coroutines and flows, Jetpack Compose on Android and SwiftUI on iOS. Sharing networking saves duplicate work and met a tight deadline; sharing ViewModel works for UI‑heavy apps but requires expect/actual shims, parallel platform development, disciplined code reviews and multiplatform‑capable developers.
AI-written summary · about
chapters (8)
- 0:00Introduction and KMM overview
- 3:01Why choose Kotlin Multiplatform
- 7:17Skills needed for KMM development
- 9:52First KMM app experience
- 12:29Second KMM app with shared ViewModel
- 15:42Team and communication in KMM
- 18:58Future of Kotlin Multiplatform
- 22:20Key takeaways and conclusion
related talks
23mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
32m10 myths about crossplatform mobile development with Kotlin
26mKotlin Multiplatform in an MVVM World
36mKotlin Multiplatform at five years
38mKMM story - from first feature to Mobile mono-repo at Sphere
35mThe Art of KMP: what you need to know as a multiplatform developer
46mKotlin Multiplatform Mobile for Teams
21mIt's Time for Kotlin Multiplatform Mobile