KMM Against Everyone
summary
Panelists discuss Kotlin Multiplatform Mobile (KMM), evaluating its current state, JetBrains’ roadmap, and real production usage stories. They compare KMM to other mobile frameworks and SDKs, examining where KMM fits well and where its limitations or competitors matter.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:01What is KMM and multiplatform
- 2:28Multiplatform popularity and challenges
- 3:37Work distribution across platforms
- 5:03Flutter multiplatform approach
- 7:08Code sharing in teams
- 8:15KMM developer requirements
- 10:40KMM alternative approaches
- 11:44Common components and standardization
- 13:12Native integration complexity
- 14:38Testing in KMM
- 16:23Flutter and native integration
- 17:06Flutter performance
- 18:10Version migration
- 18:55KMM risks and changes
- 20:19Flutter backward compatibility
- 21:48Migrating to Flutter from native
- 23:58Flutter migration case
- 25:01Migrating existing apps
- 26:27Adding Flutter to native apps
- 27:54Politics of adoption
- 28:58Flutter modules usage
- 30:24KMM and Flutter integration
- 31:48Rewriting iOS in KMM
- 32:51Shared business logic and Swift
- 34:19Swift and Kotlin interop
- 36:10KMM and Flutter competitors
- 37:56Conclusion
related talks
46mWhy KMM Is Not a Cross-Platform Framework
46mKotlin Multiplatform Mobile for Teams
29mKMP for Mobile Developers
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
34mKMM survival guide: how to tackle everyday struggles between Kotlin and Swift
29mKMP for Mobile Developers
21mIt's Time for Kotlin Multiplatform Mobile
33mGetting started with KMP