Adopting Kotlin Multiplatform In Brownfield Applications
summary
Team of ~15 invests 1.5 years into Kotlin Multiplatform to share analytics and other libs, starting by shipping a single string constant to validate end-to-end. Build uses Gradle multiplatform, custom Gradle tasks to generate a Swift Package from an XCFramework, GitHub Actions for CI, Maven publish to Artifactory for jars/aar, and local Maven/Swift package workflows for fast iteration. Production use works but costs include long iOS link times, M1 SwiftPM issues, and a bloated 6 GB repo until remote hosting is implemented.
AI-written summary · about
chapters (13)
- 0:00Introduction and agenda
- 1:15Getting organizational buy-in
- 8:14Evaluating technical and human factors
- 13:07Start small with a single feature
- 14:09Think like a library developer
- 21:16Project structure and targets
- 24:26Distributing and building artifacts
- 27:36Local development and deployment
- 29:24Automating CI and production builds
- 34:40Current use cases and adoption
- 35:45Challenges and lessons learned
- 38:49Collaborate from the beginning
- 39:52Summary and closing tips
related talks
39mAdopting 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
36mKotlin Multiplatform- From “Hello World” to the Real World
29mMaking the Big Kotlin Multiplatform Decision
38mBuild a Multiplatform Future with Kotlin
32mKotlin Multiplatform in Action