Introducing Kotlin Multiplatform in an existing project

on YouTube ↗52m

" 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)

1. 0:00Start
2. 40:19Question How difficult was it to find out what to write in order to make the publish Gradle task work?
3. 42:28Question How does the memory model changes affect when you are using Kotlin code from Swift?
4. 45:59Question Does KMM support plugins like Flutter and React Native does?

" related talks

• 36mIntroducing Kotlin Multiplatform in an existing projectMarco Gomiero · droidcon Berlin 2021
• 52miOS Architecture with MultiplatformKevin Galligan · KotlinConf 2018
• 41mKotlin Multiplatform In ProductionTy Smith, Kevin Galligan, Joaquim Verges · droidcon San Francisco 2018
• 41mKotlin Multiplatform Mobile: From Hello World to ProductionPamela Hill, Tadeas Kriz · droidcon London 2022
• 35mIntro to Kotlin MultiplatformKevin Galligan · Øredev 2019
• 36mKotlin Multiplatform at five yearsRussell Wolf · droidcon New York 2022
• 21mIt's Time for Kotlin Multiplatform MobileEkaterina Petrova · Kotlin 1.4 Online Event
• 26mKotlin Multiplatform in an MVVM WorldZachary Sweigart · droidcon San Francisco 2024