Navigation in a Multiplatform World
summary
Navigation across Android, iOS and web proves surprisingly tricky so tool choice matters: Jetpack Navigation now has type safety via Kotlinx serialization, Compose Multiplatform is usable but nav is still navigation alpha for cross‑platform hosts, Decompose offers lifecycle‑aware child stacks and state persistence, Voyager gives a lightweight navigator, and Circuit uses the Compose runtime to model navigation as part of immutable state and moves away from lifecycle with support for overlays, predicted back, and presenter/UI separation so apps stay testable and deletable.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:45Navigation beyond backstacks
- 4:52Android navigation history
- 9:51Jetpack Navigation limits
- 12:03Kotlin Multiplatform intro
- 17:25Migrating navigation to KMP
- 18:51Reactive architectures evolution
- 21:18Circuit framework intro
- 25:46Navigation libraries overview
- 27:13Choosing navigation approach
- 28:16Q&A
related talks
40mNavigation in a Multiplatform World
49mNavigating with Jetpack Compose
31mModel-driven navigation with Jetpack Compose – From zero to hero
46mMultiplatform UI with Compose
50mAndroid Navigation at scale
06mType safe, multi-module best practices with Navigation Compose
02mJetpack Compose Navigation: Beyond The Basics
38mAdventures in Navigation