Adopting Kotlin Multiplatform In Brownfield Applications
summary
Team of ~16 mobile devs ships Kotlin Multiplatform into brownfield Android and iOS apps, starting by publishing one string constant to validate end to end. Build pipeline produces .jar/.aar and a Swift package by generating an XCFramework binary, CI publishes artifacts to an Artifactory server and a GitHub repo. Work scales to analytics, networking and deep linking for apps in 40 locales with several hundred thousand MAUs. Pain points: long XCFramework build times, M1 SwiftPM tooling, and a repo swelling to ~6–7 GB; zip hosting fixes sync slowness.
AI-written summary · about
chapters (5)
- 0:00Start
- 17:20Configuring Build Targets
- 23:49Building iOS Swift Package
- 26:33Deploying Android Artifacts
- 28:30Deploying Swift Packages
related talks
41mAdopting Kotlin Multiplatform In Brownfield Applications
36mIntroducing Kotlin Multiplatform in an existing project
52mIntroducing Kotlin Multiplatform in an existing project
26mKotlin Multiplatform in an MVVM World
31mKotlin Multiplatform for iOS: Myths vs Reality
39mAnd That, Folks, is How We Shared Code Between Android, iOS and the Backend
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
52miOS Architecture with Multiplatform