navigation-3

Migrate Android Jetpack Compose apps from Navigation 2 to Navigation 3.

Updated May 22, 2026
One-click install
npx skills add https://github.com/ekawijayasusilo/kmp_template --skill navigation-3-ekawijayasusilo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: navigation-3
Source: https://github.com/ekawijayasusilo/kmp_template/tree/main/.claude/skills/navigation-3
Command: npx skills add https://github.com/ekawijayasusilo/kmp_template --skill navigation-3-ekawijayasusilo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the challenge of upgrading an Android Compose app from Jetpack Navigation 2 to Navigation 3 without breaking navigation behavior, deep linking, back stack handling, and UI composition patterns.

Core Features & Use Cases

  • Navigation 2 to Navigation 3 migration guidance, including dependency and route-model changes.
  • Implementation patterns for Navigation 3 in real apps: deep links, multiple back stacks, scenes (dialogs, bottom sheets, list-detail, two-pane, supporting pane), conditional flows, and returning results.
  • Integration guidance with common architecture and tooling such as Hilt and ViewModels, including type-safe navigation and argument passing.

Quick Start

Ask the navigation-3 skill to produce a step-by-step migration plan for your Compose navigation, covering route type updates (NavKey), replacing NavHost with NavDisplay, and handling any dialogs, multiple back stacks, deep links, and result-return patterns.

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?▼

Migrate from Jetpack Navigation 2 to Navigation 3 by replacing NavHost with NavDisplay, converting routes to type-safe NavKey definitions, and implementing entryProvider for UI composition. This ensures back stacks, scenes, and routing models transition without breaking existing behaviors.

How do NavDisplay and type-safe NavKey routes work in Jetpack Compose?▼

NavDisplay and type-safe NavKey routes work by mapping navigation destinations to metadata-driven scene strategies and type-safe keys. This replaces string-based routing, enabling robust UI composition for two-pane layouts, dialogs, and bottom sheets.

Can I implement deep links and multiple back stacks with Navigation 3?▼

Yes, you can implement deep links and multiple back stacks with navigation 3. The migration process maps existing app navigation behaviors to navigation 3 primitives, supporting advanced patterns like conditional flows, deep linking, and returning results.

What is the best way to handle scenes and bottom sheets in Navigation 3?▼

The best way to handle scenes and bottom sheets in navigation 3 is using metadata-driven scene strategies. You map app navigation behaviors to navigation 3 primitives to manage dialogs, list-detail layouts, and supporting panes effectively.

Does Navigation 3 migration support integration with Hilt and ViewModels?▼

Yes, navigation 3 migration supports integration with Hilt and ViewModels. The migration includes guidance for type-safe navigation, argument passing, and connecting common architecture tooling with your new NavDisplay and entryProvider setup.