Jumping into KMP — But at What Cost?
summary
The talk examines using Kotlin Multiplatform (KMP) and Compose Multiplatform in a real project: what was required to bring a multiplatform codebase up on Android and iOS, how long adding a Desktop target took, and practical costs measured in build sizes, build times, and time spent polishing multiplatform integrations. It presents concrete experience and numeric measurements to assess the trade-offs of adopting Kotlin + Compose Multiplatform.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:35About the speaker
- 2:47What is KMP and CMP
- 4:30Project goals
- 7:25Library integration metrics
- 9:54Dependency results
- 11:59App size after integration
- 13:51Size and build conclusions
- 16:02Module experiment
- 18:47Linear app size growth
- 19:29Design system on KMP
- 23:21App launch time
- 25:49Desktop Android app
- 28:41Retrospective and savings
- 32:02Build and parallel dev conclusions
- 35:00Umbrella modules benefits
- 36:24Final recommendations
- 37:28Convincing the team
- 40:22Q&A
related talks
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
35mThe Art of KMP: what you need to know as a multiplatform developer
46mGoing Multiplatform with Your Android App
40mBuilding a Modern Kotlin Multiplatform Application with Compose Multiplatform and Koin
29mKMP for Mobile Developers
33mGetting started with KMP
29mKMP for Mobile Developers
46mKotlin Multiplatform in a Large Project