navigation-3

Migrate Android Compose apps from Jetpack Navigation 2 to Navigation 3 with typed NavKey routes.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill navigation-3-premex-ab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: navigation-3
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-navigation-3/skills/navigation-3
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill navigation-3-premex-ab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Android developers migrate from Jetpack Navigation 2 to Navigation 3 by turning the upgrade steps into a structured plan, so you can update types, navigation state, and UI wiring without getting lost or breaking routing.

Core Features & Use Cases

  • Navigation 2 → Navigation 3 migration guide: Update dependencies, convert routes to NavKey, redesign navigation state, replace NavHost with NavDisplay, and remove Navigation 2 dependencies.
  • Typed routing and safer argument handling: Move from string routes to type-safe @Serializable route objects and handle arguments via typed navigation keys.
  • Migration support for advanced patterns: Learn how to implement deep links, conditional navigation flows, multi-backstack navigation, dialog/bottom sheet scenes, Hilt-based modular navigation, ViewModel integration, and returning results from flows.

Quick Start

Use the navigation-3 guide to migrate your app by following the official Navigation 2 to Navigation 3 migration steps and implementing type-safe NavKey routes with NavDisplay.

Frequently Asked Questions about navigation-3

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from Jetpack Navigation 2 to Navigation 3 in Compose?

To migrate from Jetpack Navigation 2 to Navigation 3, update your dependencies, convert string routes to type-safe @Serializable NavKey objects, replace NavController and NavHost with Navigator and NavDisplay, and map destinations into an entryProvider.

How do I handle deep links and multiple backstacks with Compose Navigation 3?

Compose Navigation 3 handles deep links and multiple backstacks by mapping destinations into an entryProvider with scene strategies, allowing you to maintain complex navigation flows and preserve state across destinations.

How do I implement typed routes with NavKey for Android Compose navigation?

You implement typed routes in Android Compose navigation by creating @Serializable route objects as NavKey instances, replacing string-based routes to provide type-safe argument handling and safer navigation state management.

Can I use ViewModel integration and Hilt modular navigation with Navigation 3?

Yes, Navigation 3 supports ViewModel interoperability and Hilt-based modular navigation by mapping destinations into an entryProvider, enabling dependency injection and state management across your Compose UI scenes.

How do I show dialogs and bottom sheets using NavDisplay in Compose?

You show dialogs and bottom sheets in Compose by configuring NavDisplay with specific scene strategies, mapping these overlay destinations as entries within your Navigation 3 architecture.

Why does my Navigation 2 to Navigation 3 migration break routing and state?

Navigation 2 to Navigation 3 migrations break routing and state when teams fail to refactor typed routes, back stack handling, and Compose UI integration, requiring updates to dependencies and NavController replacements to fix.