Lessons Learned from Using Kotlin Multiplatform internally
summary
OLX migrates the posting flow using Kotlin Multiplatform starting with shared data models and Kotlin serialization, planning to add Ktor and SQLDelight later; Android ships the MPP code in production behind a feature flag while iOS rejects full adoption so far. Practical blockers: enum-serialization bugs, no release dSYM, Kotlin/Native concurrency limited to the main thread, coroutines require callback wrappers, and multi-arch fat framework generation plus CocoaPods integration is used to deliver iOS binaries. The approach works for Android and as an internal iOS experiment.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 3:53Why Kotlin Multiplatform
- 9:28Team concerns and resistance
- 13:23Android implementation steps
- 20:26iOS team feedback and challenges
- 25:44Technical limitations and fixes
- 30:23iOS integration and deployment
- 32:56Future plans and advice
related talks
52mIntroducing Kotlin Multiplatform in an existing project
26mKotlin Multiplatform in an MVVM World
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
21mIt's Time for Kotlin Multiplatform Mobile
32m10 myths about crossplatform mobile development with Kotlin
52miOS Architecture with Multiplatform
31mKotlin Multiplatform for iOS: Myths vs Reality
29mKMP for Mobile Developers