Modern KMP adoption for native mobile teams
summary
Kotlin Multiplatform works technically but teams hit a workflow mismatch that stops scale: most teams succeed adding a few KMP modules, but most fail when they try to share feature‑level code across many engineers. Problems include iOS devs unfamiliar with Kotlin, Gradle/SPM friction, and the library model creates a linear‑version bottleneck that blocks concurrent feature work. A practical mitigation is a branching strategy that coordinates a KMP repo with app repos via CI, letting apps edit app code while CI syncs shared changes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:57KMP adoption challenges
- 7:04Team structure mismatches
- 13:06Monorepo vs library
- 18:30Library vs feature dev
- 23:44Why library-only KMP fails
- 28:34Horizontal limit of KMP workflows
- 31:24Monorepo challenges
- 34:13Breaking team silos
- 37:25KMP for native mobile
- 39:47KMP success stories
- 41:55Why KMP scaling is hard
- 43:01Decoupling teams for KMP
- 46:11KMP branching strategy
related talks
35mThe Art of KMP: what you need to know as a multiplatform developer
29mKMP for Mobile Developers
45mHow Kotlin Multiplatform Changed Our Processes
46mKotlin Multiplatform in a Large Project
29mKMP for Mobile Developers
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
46mKotlin Multiplatform Mobile for Teams
44mHow our iOS devs adopted KMP