Kotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
summary
Two production apps use Kotlin Multiplatform Mobile to share networking and local storage and later the view‑model layer; networking uses Ktor and local DB uses SQLDelight, with platform-specific OkHttp and WebView cookie workarounds. Build pain comes from Gradle, sparse docs and experimental APIs, but parallel Android/iOS development catches mismatches early. The second app shares ViewModel logic via Kotlin Flows and expect/actual coroutines, driving UIs with Jetpack Compose and SwiftUI; both apps ship and save development time.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 3:38What is Kotlin Multiplatform Mobile
- 5:49Why choose KMM over others
- 7:12First challenges with KMM
- 9:46First app development experience
- 12:34Second app and deeper sharing
- 14:44Team and communication in KMM
- 18:12Future of KMM and key takeaways
related talks
25mKotlin 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
52miOS Architecture with Multiplatform
40mKotlin goes global
43mLevel up on Kotlin Multiplatform
41mKotlin Multiplatform Mobile: From Hello World to Production
48mEffective Multiplatform Kotlin Development