navigation3

Migrate from Navigation 2 to 3 by replacing NavHost with NavDisplay, defining @Serializable NavKey data classes for type-safe routes, and wiring back stack decorators to ensure ViewModels are scoped per NavEntry. Use included scripts to validate setup.

Type-safe navigation in Jetpack Compose uses @Serializable NavKey data classes to define destinations instead of string routes. This ensures compile-time safety for navigation arguments and integrates with NavDisplay to manage UI state preservation.

Yes, you can integrate Hilt ViewModels with Navigation 3 by using back stack decorators. These decorators ensure ViewModels are scoped per NavEntry and that UI state is preserved during multi-stack navigation flows across your app.

The best way to manage multi-stack navigation in Compose is using Navigation 3 patterns with NavDisplay. It provides modern back stack management and decorators to scope ViewModels per NavEntry, ensuring predictable navigation behavior and easier maintenance.

Navigation 3 supports saving UI state by wiring decorators for ViewModels and Saveable state. Using back stack decorators ensures that ViewModels remain scoped per NavEntry and UI state is preserved during navigation flows.

Upgrade to Navigation 3 when you need predictable navigation behavior and easier maintenance in a large Android Compose app. It is ideal for adopting type-safe routes, multi-stack navigation, and robust ViewModel integration with Hilt.