https://developer.android.com/agents/skills/navigation/navigation-3/skill

Migrating from Navigation 2 to Navigation 3 involves updating dependencies, changing routes, and adjusting state management to preserve existing navigation flows and UI behavior in your Compose app.

Type-safe navigation in Navigation 3 replaces string-based destinations with strongly typed objects. This approach integrates with Jetpack Compose to provide compile-time safety for your navigation routes, arguments, and deep links.

Yes, you can preserve multiple back stacks during your Navigation 3 migration. The transition includes specific recipes for handling back stack behaviors to maintain expected UI state and navigation flows across different tabs.

Navigation 3 supports deep links and Scenes-based layouts for dialogs, bottom sheets, and custom layouts. The migration guide maps these specific patterns to ensure your UI components function correctly.

The best way to handle ViewModel argument passing in Navigation 3 is by using targeted recipe patterns. These patterns ensure correct argument passing and result returning while integrating with modularized DI navigation logic.

You should delay migrating to Navigation 3 if your app relies heavily on complex string-based destinations that cannot easily map to type-safe navigation, or if you lack the resources to test state restoration across multiple back stacks.