Kotlin Multiplatform Mobile for Teams
summary
Clear claim: teams are shipping KMM in production but integration choices shape success. Concrete tools and outcomes matter — Kotlin Multiplatform Mobile used as shared SDKs or as local shared architecture, with Cambridge (KMMBridge) for XCFramework/SPM publishing and local SPM dev flows. A Compose UI iOS build ships (Droidcon app) but is not yet polished. For smoother Swift APIs the team builds Skye interface enhancer that emits real Swift enums and maps suspend/flow to async patterns. Watch for tooling, CI, and ownership details.
AI-written summary · about
chapters (20)
- 0:00Kotlin Multiplatform Mobile intro
- 1:05KMM history at TouchLab
- 2:28KMM dev modes for teams
- 4:55Shared UI challenges & future
- 8:0180-20 rule for shared UI
- 9:46Kotlin & Compose UI future
- 12:13Shared everything vs optional UI
- 13:18Mobile dev team evolution
- 16:26KMM integration approaches
- 18:57SDK flow for KMM adoption
- 22:07Kotlin iOS tooling challenges
- 25:59Beyond SDK flow to shared code
- 27:25Large team coordination strategies
- 30:30Kotlin-Swift interop challenges
- 33:39Training & API anxiety in KMM
- 35:03Skye for Kotlin-Swift interop
- 37:10Skye alternatives & licensing
- 39:57Presenting KMM to iOS teams
- 42:00Best practices for KMM start
- 44:48KMM & Compose UI future
related talks
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
29mKMP for Mobile Developers
19mBuilding Bridges with Kotlin Multiplatform Mobile (KMM): How we added KMM to our established App
34mKMM survival guide: how to tackle everyday struggles between Kotlin and Swift
26mKotlin Multiplatform in an MVVM World
21mIt's Time for Kotlin Multiplatform Mobile
39mKMM Against Everyone
36mKotlin Multiplatform- From “Hello World” to the Real World