navigation-3

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

Replace string routes with @Serializable data objects and data classes, update NavHost to use composable<T> generics, and navigate with class instances like navController.navigate(Profile(userId)). ViewModels can extract arguments via SavedStateHandle.toRoute().

Navigation 3 is designed exclusively for Compose destinations. To use Fragments and Views, you must wrap them using Compose interoperability APIs such as AndroidView before adding them as destinations.

The guide does not cover nested navigation beyond one level, shared destinations across back stacks, custom destination types, or deep links. Deep links and bottom sheets are instead demonstrated through separate code recipes.

Create a BottomSheetSceneStrategy and pass it to NavDisplay's sceneStrategies parameter, then add BottomSheetSceneStrategy.bottomSheet() metadata to the entry. The strategy class is not in the core library, so copy it from the recipes into your project.

Yes, the conditional navigation recipe shows a custom Navigator that checks a requiresLogin flag on each NavKey. Unauthenticated users are redirected to a Login key, and after login they are sent to their originally requested destination.