navigation-3

To migrate from Navigation 2 to Navigation 3, replace string routes with typed @Serializable NavKey models, move destinations into an entryProvider, and swap NavHost for NavDisplay to manage explicit back stacks and Compose entry resolution.

Implement multiple backstacks for bottom tab UIs by redesigning navigation around explicit back stack management, pushing strongly-typed NavKey objects onto specific stacks to preserve state across tab switches in Compose.

Scenes in Jetpack Compose navigation handle specialized UI displays like dialogs, bottom sheets, and two-pane list-detail layouts, managed through scene-based strategies integrated with an entryProvider-driven NavDisplay for NavEntry resolution.

Handle deep links by parsing incoming URIs into typed @Serializable NavKey implementations, which are then pushed onto the explicit back stack to resolve the corresponding Compose destination via the entryProvider.

Return results between navigation destinations by applying event- or state-based approaches within your navigation flows, passing data back through the explicit back stack management system in Compose.

Yes, conditional navigation for auth or onboarding flows is supported by checking user states and pushing specific typed NavKey objects onto the back stack to route between logged-in and anonymous Compose destinations.