Unlocking Scalability: Power Up Your Native App with KMM
summary
Shows how Kotlin Multiplatform (KMM/KMP) shares 100% of business logic while keeping native UI, using an MVI stack with a 70/30 shared/native split. Two real cases: a large sports app with several hundred REST endpoints, CMS-driven theming and live scores, and a payments SDK that centralizes auth and payment flows for third-party apps. Builds include an iOS facade and XCFramework distribution for clients, onboarding about a dozen contractors, and practical caveats: cryptic errors, Xcode 15 requirement and Gradle version tinkering.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:32KMM/KMP for mobile
- 8:00Hybrid solutions vs KMM
- 11:38KMM use cases
- 15:38Why not hybrid
- 18:32MVI architecture
- 21:06ViewModel in KMM
- 28:03iOS interoperability
- 31:36KMM challenges
- 33:07Scaling team for KMM
- 35:59Shared libraries
- 38:12KMM future
- 40:21Q&A
related talks
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
29mKMP for Mobile Developers
35mThe Art of KMP: what you need to know as a multiplatform developer
26mKotlin Multiplatform in an MVVM World
19mBuilding Bridges with Kotlin Multiplatform Mobile (KMM): How we added KMM to our established App
46mKotlin Multiplatform Mobile for Teams
48mModern KMP adoption for native mobile teams
34mKMM survival guide: how to tackle everyday struggles between Kotlin and Swift