Decompose your Kotlin Multiplatform project into feature modules
summary
A concrete recipe for splitting a Kotlin Multiplatform app into lifecycle-aware feature modules using the Decompose library and a tree of parent/child scopes, with runnable samples (a multiplatform to‑do app and navigation demo). Navigation uses a transformer on a stack of parcelable configurations, components receive a component context for lifecycle, state and back handling, and UI plugs in via Compose/SwiftUI/React. Claim: smaller modules, fewer merge conflicts, faster parallel builds, and tests run as plain unit/integration tests.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:35Problems with monolithic modules
- 4:22Thinking in scopes approach
- 8:16Requirements for implementation
- 9:06T-Compose library overview
- 11:12Core concepts of Decompose
- 13:43Managing child components
- 14:48Stack navigation explained
- 17:58Initializing child stack
- 19:23Other navigation models
- 20:05UI integration with components
- 21:48Summary and resources
related talks
22mDecompose your Kotlin Multiplatform project into feature modules
40mNavigation in a Multiplatform World
22mArchitecting a Kotlin Multiplatform App
27mAn Android Dev start to Kotlin Multiplatform
48mEffective Multiplatform Kotlin Development
36mBest Practices for Developing Amazing Kotlin Multiplatform Apps
32mKotlin Multiplatform in Action
46mGoing Multiplatform with Your Android App