SDK Design and Publishing For Kotlin Multiplatform Mobile
summary
Kotlin multiplatform code exports to iOS through Objective‑C, so default parameters get lost, generics and suspend/Flow APIs become awkward, and sealed classes/enums don’t map cleanly. A practical pattern is a two-API solution (Kotlin‑first API + thin iOS adapters) or generate Swift wrappers. An experimental tool generates templated Swift, relinks it into the framework and records Objective‑C header transforms; the demo works this morning, targets early‑September release, and saves size with simple fixes (marking internals cut one sample’s binary ~20%).
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 3:16Why Kotlin Multiplatform Mobile
- 11:24Kotlin through Objective-C lens
- 14:10Two API solutions for iOS
- 24:43Swift generation library demo
- 28:54Practical issues with two APIs
- 32:03Modularization challenges
- 34:51Limiting exposed API
- 40:28Binary size and packaging
- 41:54Team dynamics and tools
- 42:56Future improvements and feedback
related talks
33mSDK Design and Publishing For Kotlin Multiplatform Mobile
37mKotlin/Multiplatform for iOS developers : state & future
36mWriting Kotlin Multiplatform libraries that your iOS teammates are gonna love
41mThe Kotlin Swift boundary
31mKotlin Multiplatform for iOS: Myths vs Reality
52miOS Architecture with Multiplatform
33mKotlin Multiplatform Alchemy: Making Gold out of Your Swift Interop
29mKMP for Mobile Developers