navigation-3

Follow seven steps: add Navigation 3 dependencies, make routes implement NavKey, create NavigationState and Navigator classes, replace NavController calls, move destinations into an entryProvider, replace NavHost with NavDisplay, and remove Navigation 2 dependencies.

Use a state holder that keeps a separate back stack per top-level route and tracks the current top-level route. The common-ui and multiple-backstacks recipes show how to flatten these stacks for NavDisplay while preserving each tab's history.

You need compileSdk 36 or later, minSdk 23, Compose-based destinations, and strongly typed routes. If you use string-based routes, migrate to type-safe navigation with Kotlin serialization first.

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 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 through dedicated basic and advanced recipes.

Copy the BottomSheetSceneStrategy class into your project, pass it to NavDisplay's sceneStrategies parameter, and add BottomSheetSceneStrategy.bottomSheet() metadata to the entry. It is not part of the core Navigation 3 library.