The Art of KMP: what you need to know as a multiplatform developer
summary
Describes using Kotlin Multiplatform to build two production apps that shorten time and cut costs while KMP is still experimental, requiring Gradle multimodule configuration and special shared-module source sets. Recommends sharing the data layer or view models and streaming updates with Kotlin Flow (with iOS bridging via publishers), pairs Compose with SwiftUI for easier cross-platform UI, and relies on libraries like Koin, SQLDelight, and Ktor. Emphasizes backend sharing with Kotlin and that clear communication and project management determine success.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 3:20Why research tools before coding
- 5:32Gradle setup for KMP projects
- 11:12Architecture choices in KMP
- 15:30Reactive UI with Compose and SwiftUI
- 20:51Streaming data with Kotlin Flows
- 22:40Learning Swift and Kotlin together
- 25:30Essential KMP libraries
- 27:40Backend development with Kotlin
- 29:05Soft skills for KMP teams
- 33:01Summary and learning roadmap
related talks
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
48mModern KMP adoption for native mobile teams
29mKMP for Mobile Developers
33mGetting started with KMP
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
45mJumping into KMP — But at What Cost?
29mKMP for Mobile Developers
36mBest Practices for Developing Amazing Kotlin Multiplatform Apps