What problem does it solve?
Navigation 3 migration turns app navigation code into a new model with custom back stack control, Scenes, and typed routes, which commonly causes regressions when teams rely on Navigation 2 patterns like string routes and NavHost graphs.
Core Features & Use Cases
- Navigation 2 to Navigation 3 migration guidance: update dependencies, replace routes with NavKey implementations, rebuild navigation state, and swap NavHost for NavDisplay.
- Type-safe navigation and route modeling: migrate from string-based destinations to serializable Kotlin types that provide compile-time safety for arguments.
- Advanced Navigation 3 patterns: deep links (including deep link recipes), conditional navigation flows, multiple back stacks (top-level tabs), Scenes (dialogs, bottom sheets, list-detail, two-pane), Hilt/Kotlin architecture integration, ViewModel argument passing, and returning results as events or state.
Quick Start
Ask the AI agent to generate a step-by-step migration plan for moving your Jetpack Compose app from Jetpack Navigation 2 to Navigation 3, including deep links, multiple back stacks, Scenes, Hilt integration, and returning results.