android-navigation-deeplinks

Android Navigation Deep Links

When To Use

• Use this skill when the request is about: android navigation graph, deep link into android app, back stack issue in compose nav.
• Primary outcome: Handle navigation graphs, back stack behavior, app links, intents, and destination ownership for Android apps.
• Handoff skills when the scope expands:
• android-permissions-activity-results
• android-testing-ui

Workflow

1. Confirm the user-visible journey, target device behavior, and failure states that matter.
2. Identify the owning screens, activities, destinations, and state holders for the flow.
3. Implement the flow with explicit loading, success, empty, and error handling.
4. Validate accessibility, configuration changes, and back-stack behavior in the showcase apps.
5. Escalate data, architecture, or release concerns to the specialized skills called out in the handoff notes.

Guardrails

• Treat loading, empty, error, offline, and permission-denied states as first-class UI states.
• Do not hide navigation or permission side effects inside reusable UI components.
• Prefer lifecycle-aware APIs over manual callback chains.
• Keep deep links, intents, and permission prompts testable and observable.

Anti-Patterns

• Assuming the happy path is enough for product flows.
• Hard-coding request codes or route strings in multiple places.
• Triggering navigation directly from repositories or network layers.
• Shipping flows without recovery UI for denied permissions or broken state.

Remediation Examples

Centralize route ownership

sealed interface OrbitRoute {
    data object Board : OrbitRoute
    data class Task(val taskId: String) : OrbitRoute
}

Preserve expected back-stack behavior

navController.navigate(OrbitRoute.Task(taskId)) {
    launchSingleTop = true
    restoreState = true
}

Parse deep-link arguments in one place

val taskId = intent?.data?.getQueryParameter("taskId")
require(!taskId.isNullOrBlank()) { "Missing taskId deep-link argument" }