Kotlin/Multiplatform for iOS developers : state & future
summary
Slides run as a Kotlin JS webpage in Chrome, proving Kotlin can target the web. Kotlin/Multiplatform exports Objective‑C headers so generics and interfaces break for Swift, flows lose element types, and coroutines compiler plugins are still unstable; a pragmatic fix is an MPFlow wrapper. Use SourceKitten to generate readable Swift APIs from Obj‑C headers. Deploy via Swift Package Manager with SPM binary targets and tools like KMBridge/Kotlin Gradle plugins; tooling gaps remain (IDE support, heavy Android SDK, poor Xcode stack traces).
AI-written summary · about
chapters (8)
- 0:00Kotlin Multiplatform intro
- 1:06Why KMP for iOS devs
- 4:37Better APIs for iOS
- 12:25Better communication with Swift developers
- 22:02iOS artifact deployment
- 25:55Swift API usability
- 29:06Engaging iOS teams
- 34:20Final thoughts
related talks
31mKotlin Multiplatform for iOS: Myths vs Reality
48mKotlin for Android, iOS & the mobile web
26mKotlin Multiplatform in an MVVM World
36mKotlin Multiplatform- From “Hello World” to the Real World
48mEffective Multiplatform Kotlin Development
48mEffective Multiplatform Kotlin Development
01h 07mDevelop Multiplatform Projects in Kotlin
35mIntro to Kotlin Multiplatform