navigation-3

Add the navigation3-runtime and navigation3-ui dependencies, make routes implement NavKey, create NavigationState and Navigator classes, move destinations from NavHost's NavGraph 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.

You need compileSdk 36 or later, minSdk 23, composable destinations, and strongly typed routes. String-based routes must first be migrated to type-safe navigation using Kotlin serialization before starting the Navigation 3 migration.

Navigation 3 is designed exclusively for Compose, so destinations must be composable functions. To use Fragments and Views, you must wrap them using Compose interoperability APIs for views in Compose.

The guide does not cover more than one level of nested navigation, shared destinations that move between back stacks, custom destination types, or deep links. Deep links are addressed separately in dedicated basic and advanced recipes.

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