Introducing Kotlin Multiplatform in an existing project
summary
Explains how Kotlin Multiplatform (alpha but production-used) is introduced incrementally: start by sharing small, boring or DTO code then expand to persistence with SQLDelight; Android artifact is an AAR published to Maven, iOS is an XCFramework packaged and distributed via CocoaPods; Gradle tasks automate developer vs main releases and tagging; handles Kotlin 1.5.20/1.5.30 tooling quirks and native concurrency via freeze until the new memory model arrives; approach works — validated in a real company and scaled successfully.
AI-written summary · about
chapters (4)
- 0:00Start
- 40:19Question How difficult was it to find out what to write in order to make the publish Gradle task work?
- 42:28Question How does the memory model changes affect when you are using Kotlin code from Swift?
- 45:59Question Does KMM support plugins like Flutter and React Native does?
related talks
36mIntroducing Kotlin Multiplatform in an existing project
52miOS Architecture with Multiplatform
41mKotlin Multiplatform In Production
41mKotlin Multiplatform Mobile: From Hello World to Production
35mIntro to Kotlin Multiplatform
36mKotlin Multiplatform at five years
21mIt's Time for Kotlin Multiplatform Mobile
26mKotlin Multiplatform in an MVVM World