Advanced Kotlin Native Integration
summary
Kotlin Multiplatform on iOS cannot safely include multiple native binaries because each framework duplicates the Kotlin stdlib and runtime, causes incompatible types, doubles GC heaps and raises crashes; the practical solution builds temporary dummy frameworks, produces and shares a static cache (prebuilt KLib/object files) via an export project, scans used Kotlin symbols to trim headers, and moves framework configuration toward a Kotlin package manager; a separate hot reload VM for Kotlin IR proves fast and works across iOS, Android and desktop.
AI-written summary · about
chapters (15)
- 0:00Kotlin Native integration intro
- 1:43iOS app modularization
- 3:27Native framework definition
- 5:10Risks of multiple KMP frameworks
- 10:06Single KMP framework limits
- 12:35Multiple KMP frameworks again
- 13:38Native compilation process
- 15:46Dummy frameworks for KMP
- 17:54When dummy frameworks help
- 19:17Static cache for Kotlin builds
- 22:49KMP export optimization
- 25:58Kotlin package manager intro
- 27:04KMP framework best practices
- 28:28Kotlin hot reload demo
- 31:42Kotlin hot reload benefits
related talks
30mReusable Cross-Platform Frameworks with Kotlin/Native
31mKotlin Multiplatform for iOS: Myths vs Reality
31mKotlin/Native for Multiplatform Development
39mDependencies and Kotlin/Native
26mKotlin/Native for Multiplatform Development
35mIntro to Kotlin Multiplatform
36mIntroducing Kotlin Multiplatform in an existing project
41mKotlin Multiplatform Mobile: From Hello World to Production