KMP for Mobile Developers
summary
Kotlin Multiplatform compiles common Kotlin into an iOS framework and Android AAR/jar so UI stays native while business logic is shared; examples use expect/actual to provide platform code, create KLIBs, and use SQLDelight and kotlinx.coroutines plus atomicfu and kotlinx-io for buffering. Beware Objective‑C interop limits: suspend functions, exhaustive enums, default args and Codable don’t map cleanly and objects must be dot‑frozen to share threads. Surveyed projects put 30–70% of code in KMP and 85% adopt within six months with ~98% satisfaction.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker
- 1:11Why KMP over cost savings
- 3:20Kotlin and JetBrains benefits
- 5:48KMP definitions and models
- 7:11Technical overview of KMP
- 9:58Expect and actual keywords
- 11:02Logging library example
- 12:49KMP ecosystem libraries
- 15:17C routines and KotlinX.io
- 16:42AtomicFu and SQLDelight
- 17:46Serialization and preferences
- 18:29Object freezing in KMP
- 18:52iOS development limitations
- 21:59Adopting KMP challenges
- 23:03Architecting KMP apps
- 24:29KMP survey insights
- 25:33Case studies and production readiness
- 26:39Future of KMP and frameworks
- 27:44Personal advice on KMP
- 28:24Further resources and closing
related talks
29mKMP for Mobile Developers
33mGetting started with KMP
35mThe Art of KMP: what you need to know as a multiplatform developer
48mModern KMP adoption for native mobile teams
21mIt's Time for Kotlin Multiplatform Mobile
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
26mKotlin Multiplatform in an MVVM World
35mIntro to Kotlin Multiplatform