navigation-3

Add the navigation3-runtime and navigation3-ui dependencies, make routes implement NavKey, create NavigationState and Navigator classes, move destinations from NavHost into an entryProvider, replace NavHost with NavDisplay, then remove Navigation 2 dependencies.

Add DialogSceneStrategy or a custom BottomSheetSceneStrategy to NavDisplay's sceneStrategies parameter, then mark the destination's entry with DialogSceneStrategy.dialog() or BottomSheetSceneStrategy.bottomSheet() metadata.

Navigation 3 is designed exclusively for Jetpack Compose, so destinations must be composable functions. To keep existing Fragments or Views, use Compose interoperability APIs to embed them inside composables.

Your project needs compileSdk 36 or later, minSdk 23, strongly typed routes (migrate string-based routes to type-safe routes first), and composable destinations. Deep links, nested navigation beyond one level, and shared destinations are not covered by the migration guide.

Add the lifecycle-viewmodel-navigation3 add-on library and construct the ViewModel with viewModel() inside the entry content. Navigation arguments are read directly from the NavKey instance passed to the entry's trailing lambda.

Maintain a separate back stack per top-level route in a state holder, track the current top-level route, and expose a flattened list of entries to NavDisplay. The multiple-backstacks and common-ui recipes show complete implementations with state retention.