Kotlin Multiplatform Alchemy: Making Gold out of Your Swift Interop
summary
Kotlin/Swift interop currently maps via an Objective‑C bridge so Swift Export Tool aims to replace the ugly ObjC surface and already generates nicer Swift sources for classes, nullability, lists/maps and extension functions while still lacking coroutines, preserving generics, or supporting inheritance. Practical fixes include renaming and hiding APIs, exporting KDOC and using should refine in swift plus KMP native coroutines or community libs to get proper cancellation for suspend functions; data classes, inline functions and varargs remain risky.
AI-written summary · about
chapters (5)
- 0:00Kotlin Swift interop challenges
- 4:42Current state of interop
- 10:05Eight techniques to improve interop
- 26:07Future of interop with Swift Export
- 30:30Key takeaways
related talks
49mEffective Kotlin-Swift Interoperability
37mKotlin and Compose Multiplatform patterns for iOS interop
45mSDK Design and Publishing For Kotlin Multiplatform Mobile
36mWriting Kotlin Multiplatform libraries that your iOS teammates are gonna love
41mThe Kotlin Swift boundary
37mKotlin/Multiplatform for iOS developers : state & future
34mKMM survival guide: how to tackle everyday struggles between Kotlin and Swift
31mKotlin Multiplatform for iOS: Myths vs Reality
