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, and replace NavHost with NavDisplay. The migration guide walks through each step with code.

Maintain a separate back stack per top-level route and track the current top-level route in a state holder. The common-ui and multiple-backstacks recipes show a TopLevelBackStack class that flattens the stacks for NavDisplay while preserving each tab's history.

Navigation 3 is designed exclusively for Compose destinations. To use Fragments and Views, you must wrap them using Compose interoperability APIs such as AndroidView, as described in the Views-in-Compose documentation.

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

The guide does not cover more than one level of nested navigation, shared destinations that move between back stacks, or custom destination types. Projects using those features need custom solutions beyond the provided recipes.

Deep links are defined independently of the navigation UI using DeepLinkMatcher instances such as UriDeepLinkMatcher. You match incoming intents in your Activity's onCreate and onNewIntent to construct the initial back stack.