For a large XML-based app, keep one host activity with one primary `NavHostFragment` and organize the graph into nested or included graphs, such as separate `nav_auth.xml` and `nav_main.xml` graphs. Nested graphs keep each feature’s destinations and actions readable while preserving a centralized `NavController`, back stack, SafeArgs contracts, and deep-link handling. Define explicit `<deepLink>` elements in the navigation graph rather than manifest intent filters. Use multiple `NavHostFragme...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill android-legacy-navigation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Android Legacy Navigation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-android-legacy-navigation-4aaac810)More formats (shields.io, HTML) on the badges page.
# Prefer nested navigation graphs
For a large XML-based app, keep one host activity with one primary `NavHostFragment` and organize the graph into nested or included graphs, such as separate `nav_auth.xml` and `nav_main.xml` graphs.
Nested graphs keep each feature’s destinations and actions readable while preserving a centralized `NavController`, back stack, SafeArgs contracts, and deep-link handling. Define explicit `<deepLink>` elements in the navigation graph rather than manifest intent filters.
Use multiple `NavHostFragment`s only when the UI genuinely needs independent navigation stacks at the same time—for example, separate simultaneously visible panes. They add coordination and back-stack complexity, so they should not be the default way to modularize a large graph.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
