Decompose your Kotlin Multiplatform project into feature modules
summary
Argues that a tree of feature modules reduces coupling and improves testability versus one huge shared module, demonstrates the Decompose library for lifecycle-aware component contexts, shows stack navigation implemented with child stack configurations and factories, and plugs platform UIs (Jetpack Compose, SwiftUI, React) into the same components. Claims this cuts merge conflicts and speeds builds, handles state preservation and back button, and scales where a single shared module would hit 100 view models and break.
AI-written summary · about
chapters (8)
- 0:00Introduction to KMP architecture
- 2:39Problems with monolithic shared modules
- 7:59Introducing scopes and decomposition
- 10:14Decompose library overview
- 13:26Component lifecycle and child management
- 15:09Stack navigation with Decompose
- 19:49UI integration and animations
- 21:38Q&A and resources
related talks
22mDecompose your Kotlin Multiplatform project into feature modules
22mArchitecting a Kotlin Multiplatform App
48mBuilding Multi Platform Projects with MVI
32mKotlin Multiplatform in Action
48mEffective Multiplatform Kotlin Development
36mBest Practices for Developing Amazing Kotlin Multiplatform Apps
27mAn Android Dev start to Kotlin Multiplatform
54mThe Golden Principles of Software Architecture Applied To Kotlin Multiplatform
