Navigation in a Multiplatform World
summary
Kotlin Multiplatform reaches production maturity (stable since 1.9.2) and ecosystem size jumps to roughly 1,200 KMP libraries in 2023, Jetpack Compose multiplatform exists but lags feature parity, and Jetpack Navigation adds type safety via kotlinx.serialization in September and an alpha multiplatform artifact so Android nav can be reused. Alternatives shown: Decompose for lifecycle-aware child stacks, Circuit (used at Slack) for compose-first UDF and rememberRetained to replace ViewModel, plus Voyager and others; examples compile and run, migration is practical but architecture-dependent.
AI-written summary · about
chapters (7)
- 0:00Navigation challenges
- 4:19Android navigation complexity
- 12:05Multiplatform with Kotlin
- 17:00Compose Multiplatform trade-offs
- 24:45Circuit library navigation
- 33:09Choosing navigation libraries
- 33:53Q&A
related talks
28mNavigation in a Multiplatform World
42mWhat’s New in Compose Multiplatform
46mMultiplatform UI with Compose
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps
45mThe Adventures of Kotlin And Compose Through the Multiplatform World
58mMultiplatform UI: Compose outside Android
26mKotlin Multiplatform in an MVVM World
22mDecompose your Kotlin Multiplatform project into feature modules