Introducing Kotlin Multiplatform in an existing project
summary
Explains how a Kotlin Multiplatform library is actually delivered into three repos: Android artifacts published with the Maven Publish plugin, iOS packaged as an XCFramework + CocoaPods repo, and a Gradle task automates build, branch switching, moving binaries, versioning and git tagging. Calls out Kotlin versions (XCFramework support since 1.4.30, embedded Xcode task from 1.5.20), runtime pain with Kotlin/Native concurrency and need to freeze objects, and reports success starting with DTOs then reusing SQL persistence across Android and iOS.
AI-written summary · about
chapters (9)
- 0:00Welcome and introduction
- 1:06What is Kotlin Multiplatform
- 3:56New vs existing project setup
- 9:35Choosing code to share
- 14:52Creating a KMP library
- 17:25Publishing Android library
- 19:14Publishing iOS framework
- 29:34Concurrency in KMP
- 32:46Key takeaways and next steps
related talks
52mIntroducing Kotlin Multiplatform in an existing project
26mKotlin Multiplatform in an MVVM World
35mIntro to Kotlin Multiplatform
52miOS Architecture with Multiplatform
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
27mKotlin: Multi-Platform
39mAdopting Kotlin Multiplatform In Brownfield Applications
36mGoing Multiplatform with Kotlin