Kotlin/Native for Multiplatform Development
summary
Kotlin/Native targets multiple platforms via LLVM and can compile a shared module into an iOS framework or JVM artifact, but the compiler in 0.9.3 beta is slow and the runtime has concrete limits: single-threaded coroutines, a memory model that requires freeze/frozen objects to share data across threads, and no direct C++ interop (C/Objective‑C/Swift only). Tooling includes Ktor, SQLDelight, atomicfu and multiplatform settings; practical advice is to use Kotlin/Native for core logic and libraries, not UI, and adopt it progressively rather than rewrite whole apps.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker intro
- 1:23Motivation for multiplatform development
- 3:53Multiplatform development paradigms
- 5:58Why Kotlin/Native
- 8:45Current Kotlin/Native status
- 10:51Sharing architecture not UI
- 11:57Technical details of Kotlin/Native
- 13:49Memory management in Kotlin/Native
- 15:12Interoperability with C and Objective-C
- 16:38Kotlin libraries and tooling
- 17:21Ecosystem and community libraries
- 19:08Getting started with expect/actual
- 20:53Threading and frozen objects
- 22:16How to start using Kotlin/Native
- 23:26Compilation time and practical use
- 24:53Limitations and future of Kotlin/Native
- 27:05Personal recommendations and conclusion
- 29:11Q&A
