KMM story - from first feature to Mobile mono-repo at Sphere
summary
Kotlin Multiplatform Mobile powers a shared AppCore that migrates the domain layer into a database-first, unidirectional flow using Kotlin Coroutines and SQLDelight, integrating Apollo GraphQL, Firestore and WebSocket. A nine‑month incremental move yields 30% shared core across Android and iOS, delivers offline availability and instant cache-hit responses, implements optimistic updates via an operation queue and store actors, uses a mobile monorepo for coordinated releases, and enables parallel feature work — the approach proves workable and reduces duplicate domain effort.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:53Why Kotlin Multiplatform at Sphere
- 7:59Kotlin Native advantages explained
- 12:38Migration strategy and execution
- 26:47Architecture of AppCore
- 36:19Example use case implementation
- 37:49Q&A and resources
related talks
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
46mKotlin Multiplatform Mobile for Teams
21mIt's Time for Kotlin Multiplatform Mobile
26mKotlin Multiplatform in an MVVM World
46mUnlocking Scalability: Power Up Your Native App with KMM
27mAn Android Dev start to Kotlin Multiplatform
32m10 myths about crossplatform mobile development with Kotlin
36mKotlin Multiplatform at five years