Building apps using Kotlin Native
summary
Practical walkthrough of using Kotlin Native to share business logic across Android and iOS: compiler via LLVM produces an Objective‑C framework imported by CocoaPods using a Gradle task, Kotlinx.serialization + Ktor (iOS engine = NSURLSession) handle JSON and HTTP, SQLDelight generates SQLite code, and tests compile/run on each platform. Concurrency relies on workers, freezing and atomic references and can throw runtime capture errors. Examples include GitNotes and Yava; recommendation: expect/actual for platform APIs, Gradle → CocoaPod integration, Kotlinx.serialization for models.
AI-written summary · about
chapters (23)
- 0:00Introduction and speaker background
- 1:29Open source projects overview
- 2:34Why cross-platform technology matters
- 7:33Wish list for multiplatform solutions
- 14:43What is Kotlin Native
- 18:41Hello World with Kotlin Native
- 20:49Project structure and dependencies
- 23:58Expect and actual keyword abstractions
- 28:11Building an entire app with Kotlin Native
- 30:00JSON serialization with Kotlin X
- 32:11HTTP client with Ktor
- 34:20Testing multiplatform code
- 36:28MVP architecture implementation
- 38:13View and presenter contracts
- 40:16Interactor and database layer
- 41:18SQLDelight for persistence
- 42:23iOS integration and Xcode setup
- 43:04iOS view controller implementation
- 44:54Concurrency challenges in Kotlin Native
- 46:02Workers and thread safety
- 49:41Third-party libraries and trade-offs
- 50:47Kotlin Native vs Flutter comparison
- 51:48Summary and closing remarks
related talks
48mKotlin for Android, iOS & the mobile web
18mKotlin native
43mThe Triumphs and Tribulations of Kotlin-Native in Practice
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
30mReusable Cross-Platform Frameworks with Kotlin/Native
44mShipping a Mobile Multiplatform Project on iOS & Android
41mKotlin Multiplatform Mobile: From Hello World to Production
40mKotlin goes global
