Confessions of a Serial K–otlin Multiplatform–er
summary
Claim: Kotlin enables sharing real business logic across targets but is not a magic multiplatform UI. Evidence: examples of cross‑compiling to JVM and native, compiling to Dex art bytecode on Android, using SQLite as a pragmatic shared store, and decades of game engines versus app conventions. Tools compared: Kotlin MPP, React Native, Flutter paints directly on the screen. Outcome: engineer once and write platform specializations; teams see long‑term fewer replicated bugs and easier testing — it works, not instantly faster.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:40Welcome
- 2:20What is this
- 7:45What is native
- 10:00Why not multiplatform
- 17:05Java motto
- 17:54Engineer once
- 19:32Specialization
- 20:33Language
- 21:25Binary Code
- 22:16Multiplatform
- 25:53Multiplatform redesign
- 29:12Multiplatform for the wrong reasons
- 30:03Questions
- 31:48Separation
- 32:53MDI
- 35:05Databases
- 36:15Views
- 36:48Disadvantages
- 40:21Multiplatform calling
related talks
48mEffective Multiplatform Kotlin Development
32m10 myths about crossplatform mobile development with Kotlin
36mExploring Kotlin Multiplatform
48mEffective Multiplatform Kotlin Development
31mKotlin Multiplatform for iOS: Myths vs Reality
52miOS Architecture with Multiplatform
52mKotlin Multiplatform, a language to rule them all
34mKotlin Multiplatform: code sharing without compromise