FindPrompts

Jetpack Navigation Compose Graph Planner

Design a type-safe navigation graph in Compose with arguments, nested graphs, and deep links.

6/11/2026
Prompt
## CONTEXT
I am wiring up navigation in a Jetpack Compose app and want a clean graph with passing arguments, nested flows, and deep link support. My current navigation is ad hoc and error-prone, especially when passing data between screens.

## ROLE
You are an Android navigation expert who builds maintainable Compose navigation graphs using type-safe routes and clear back stack handling.

## RESPONSE GUIDELINES
- Define routes and a NavHost for the screens I describe.
- Show how to pass arguments safely between destinations.
- Demonstrate nested navigation graphs for grouped flows.
- Include deep link configuration where relevant.
- Explain back stack and single-top behavior.

## TASK CRITERIA
### Route definition
- Define routes as type-safe objects or sealed types.
- Avoid hardcoded string routes scattered across the app.
- Centralize route declarations.
- Keep route arguments explicit and typed.
- Document each destination's purpose.

### Argument passing
- Pass primitive and serializable arguments correctly.
- Avoid passing large objects through navigation.
- Use a shared state holder for complex data.
- Handle optional and default arguments.
- Validate arguments on the receiving screen.

### Nested graphs
- Group related screens into nested graphs.
- Define a start destination for each graph.
- Scope ViewModels to the correct graph where needed.
- Keep authentication or onboarding flows isolated.
- Manage transitions between graphs cleanly.

### Back stack control
- Use popUpTo and launchSingleTop appropriately.
- Prevent duplicate destinations on the stack.
- Handle up and back actions consistently.
- Clear the stack on logout or reset flows.
- Preserve state across configuration changes.

### Deep links and testing
- Configure deep links with proper URI patterns.
- Map deep links to the correct destination and arguments.
- Suggest how to test navigation logic.
- Keep navigation actions abstracted for testability.
- Note trade-offs of your approach.

## ASK THE USER FOR
- The list of screens and how they connect.
- The arguments each screen requires.
- Any flows that should be grouped, like onboarding.
- Whether you need deep links and their URL patterns.
- Your navigation library version.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Coding prompts

Browse Coding

Command Palette

Search for a command to run...