navigation-event
Intercept back gestures and run Predictive Back animations using the
Install / Use
npx skills add android/skills --skill navigation-eventInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of navigation-event
navigation-event scores 93/100 on our quality scale, 597th of 4,698 Development & Engineering skills we index (top 13%).
Its SKILL.md is 13 KB long, well organised into 20 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
With 7,514 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so navigation-event is actively maintained.
- Our last check on 2026-10-26 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
navigation-event compared with similar skills
All 4 of these similar skills score higher than navigation-event; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| navigation-event (this skill)by android | 93 | 7.5k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install navigation-event?
- Run
npx skills add android/skills --skill navigation-event. The install tabs above show the steps for each supported agent. - Which AI agents does navigation-event work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is navigation-event safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is navigation-event still maintained?
- The repository was last updated about 2 months ago, so navigation-event is actively maintained.
Skill content
View source on GitHubname: navigation-event
description: Intercept back gestures and run Predictive Back animations using the
NavigationEvent (androidx.navigationevent) library in Compose Android. Handles Activity
setup, parent-child dispatcher scoping in ViewPagers or tabs, Compose NavigationBackHandler,
and migration from legacy BackHandler on SDK 36+.
license: Complete terms in LICENSE.txt
metadata:
author: Google LLC
last-updated: '2026-09-01'
keywords:
- Android
- Navigation Event
- Jetpack Compose
- Back Navigation
- Dispatcher
- Guidelines
- Troubleshooting
- ComponentActivity
- Dialog
- ViewPager
Common guidelines
- For architecture concepts : To understand the foundational architecture, continuous gesture event lifecycles, or class definitions of the Navigation Event library, read Navigation Event overview.
- For Android target : If compile SDK is lower than 36, set it to
36or higher inbuild.gradle.kts. - For Compose Android target: The project must use Jetpack Compose for Compose-specific APIs. This skill is scoped exclusively to Compose Android (Android Views and non-Compose implementations are excluded).
- For activity dispatchers :
ComponentActivityautomatically implementsNavigationEventDispatcherOwnerout-of-the-box. You must use the built-innavigationEventDispatcherwithout creating anonymous delegate owners or overriding member properties. - For dialog scoping : Floating windows (Compose
Dialog,ModalBottomSheet,ComponentDialog) automatically provide aNavigationEventDispatcherOwner. You don't need manualCompositionLocalProviderpropagation for dialogs. - For parent-child dispatcher hierarchies : When scoping navigation handling to
ViewPagers, tabbed interfaces, or nested navigation containers in Compose, userememberNavigationEventDispatcherOwner()to create a child owner linked to the parent. Disabling the owner (enabled = false) automatically cascades to disable all child handlers. - For Compose handlers : A one-to-one relationship between
NavigationEventStateand handlers is strictly enforced. Never bind the sameNavigationEventStateto multiple activeNavigationBackHandlerinstances (IllegalArgumentException).
Step 1: Plan
To complete this step, you MUST ensure the following:
- Identify the target platform : Verify the app is targeting Compose Android. If
compileSdkis lower than 36, set it to36or higher inbuild.gradle.kts. - Navigation check: Check if Navigation 3 is in use. If it is in use, use Navigation 3's built-in back navigation support rather than manually implementing low-level dispatchers from this skill.
- Hierarchy check : Identify host Activities,
ViewPagers, tabbed interfaces, or nested navigation hosts that require back gesture interception or parent-child dispatcher linking. - Migration check : Check if the project is migrating from back handling (
OnBackPressedCallback,BackHandler,onBackPresser) toNavigationEventandNavigationBackHandler. - Input interception : Detect where the app is intercepting navigation events from gestures or hardware button presses requiring translation to
NavigationEvent.
Step 2: Set up dependencies
To complete this step, you MUST ensure the following:
- For setting up compile SDKs, declaring catalog versions, and adding dependencies, follow setup guide.
Step 3: Configure dispatcher and inputs
To complete this step, you MUST ensure the following:
- To configure your dispatcher, leverage automatic
ComponentActivityorComponentDialogowner resolution. - Link parent-child dispatchers in Compose following dispatcher guide.
Step 4: Handle back navigation and UI transitions
To complete this step, you MUST ensure the following:
- To create navigation event handlers, integrate back gesture interception in Compose, animate UI components during swipes, and migrate from legacy back handlers, follow handle back guide.
Step 5: Clean up resources
[!WARNING] Warning: Compose APIs perform teardown automatically. When using Compose APIs such as
NavigationBackHandlerandrememberNavigationEventDispatcherOwner(), handler removal and dispatcher disposal occur automatically when the composable leaves the composition.
You MUST perform explicit manual cleanup only when managing custom dispatchers or non-Compose handlers:
- Call
remove()on active handlers during teardown. - Call
isEnabled = falseto temporarily disable navigation subtrees. - Call
dispose()on dispatcher instances when hosting components are destroyed. Disposing a parent dispatcher automatically cascades to all child dispatchers.
Core troubleshooting guidelines
1. Activity dispatcher setup (StackOverflowError recursion)
ComponentActivity implements NavigationEventDispatcherOwner automatically
out-of-the-box. Don't override navigationEventDispatcher or wrap it in an
anonymous delegate owner.
RIGHT
Why this is RIGHT : Compose apps use ComponentActivity as the host.
LocalNavigationEventDispatcherOwner.current automatically resolves the
Activity's built-in dispatcher.
// RIGHT
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
MyApplicationContent()
}
}
}
<br />
WRONG
Why this is WRONG : Implementing NavigationEventDispatcherOwner directly on
MainActivity and overriding navigationEventDispatcher with a new instance
shadows the library's extension property, causing a recursive infinite loop
crash on launch (StackOverflowError). Creating redundant anonymous delegate
owners (object : NavigationEventDispatcherOwner) is unnecessary.
// WRONG
class MainActivity : ComponentActivity(), NavigationEventDispatcherOwner {
override val navigationEventDispatcher = NavigationEventDispatcher() // Shadow loop crash
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
MyApplicationContent()
}
}
}
<br />
2. Floating window and dialog scoping (automatic ComponentDialog owner)
Floating windows (Compose Dialog, ModalBottomSheet, and any window backed by
ComponentDialog) automatically provide a NavigationEventDispatcherOwner.
Don't manually re-provide LocalNavigationEventDispatcherOwner using
CompositionLocalProvider inside dialogs.
RIGHT
Why this is RIGHT : ComponentDialog handles navigation dispatchers
automatically. Compose Dialog components resolve their dispatcher owner
out-of-the-box without manual propagation.
// RIGHT
@Composable
fun MyDialog(onDismiss: () -> Unit) {
Dialog(onDismissRequest = onDismiss) {
val navigationState = rememberNavigationEventState(currentInfo = NavigationEventInfo.None)
NavigationBackHandler(
state = navigationState,
onBackCompleted = onDismiss
)
}
}
<br />
WRONG
Why this is WRONG : Wrapping dialog content in a manual
CompositionLocalProvider creates redundant boilerplate and obscures the
automatic dispatcher resolution provided by ComponentDialog.
// WRONG
@Composable
fun MyDialog(onDismiss: () -> Unit) {
val dispatcherOwner = LocalNavigationEventDispatcherOwner.current!!
Dialog(onDismissRequest = onDismiss) {
// Redundant: ComponentDialog provides NavigationEventDispatcherOwner automatically
CompositionLocalProvider( LocalNavigationEventDispatcherOwner provides dispatcherOwner) {
val navigationState = rememberNavigationEventState(currentInfo = NavigationEventInfo.None)
NavigationBackHandler(
state = navigationState,
onBackCompleted = onDismiss
)
}
}
}
<br />
3. Parent-child dispatcher hierarchy (ViewPagers and nested navigation)
When managing nested UI hierarchies such as ViewPagers, tabbed
interfaces, or custom navigation containers in Compose, use
rememberNavigationEventDispatcherOwner() to create a child owner linked to the
composition hierarchy. Setting enabled = false on the child owner
automatically disables its dispatcher and all registered child handlers.
RIGHT
Why this is RIGHT : Using rememberNavigationEventDispatcherOwner(enabled = isSelected) creates a scoped child dispatcher linked to the parent from
LocalNavigationEventDispatcherOwner.current. Providing it using
CompositionLocalProvider ensures non-visible tabs or pages automatically stop
intercepting back gestures without leaking handlers.
// RIGHT: Scoping child navigation in a ViewPager or Tab interface
@Composable
fun TabPage(isSelected: Boolean) {
val childOwner = rememberNavigationEventDispatcherOwner(enabled = isSelected)
CompositionLocalProvider(LocalNavigationEventDispatcherOwner provides childOwner) {
val navigationState = rememberNavigationEventState(currentInfo = NavigationEventInfo.None)
NavigationBackHandler(
state = navigationState,
onBackCompleted = { /* Handle page back navigation */ }
)
// Page content
}
}
<br />
WRONG
Why this is WRONG : Creating unlinked standalone dispatchers, instantiating
raw dispatchers without remembering them across recompositions, or attempting to
use non-existent methods like .addChild() breaks hierarchy routing and leaves
child handlers active even when the page is inactive.
// WRONG
@Composable
fun TabPage(isSelected: Boolean) {
val parentDispatcher = LocalNavigationEventDispatcherOwner.current?.navigationEventDispatcher
val childDispatcher = NavigationEventDispatcher() // Unlinked and not remembered across recompositions
// WRONG: Method does not exist
parentDispatcher?.addChild(childDispatcher)
}
<br />
4. Compose multi-handler registration (IllegalArgumentException)
You must not bind the same NavigationEventState to multiple active
NavigationBackHandler instances, as this throws an IllegalArgumentException
at runtime. To handle conditional workflows (such as checking for unsaved
changes versus navigating back immediately), you must register a single unified
handler and branch logic inside onBackCompleted.
RIGHT
Why this is RIGHT : Using a single NavigationBackHandler with internal
branching logic inside onBackCompleted maintains a strict 1:1 mapping between
NavigationEventState and the handler, preventing state collisions.
// RIGHT
val navigationState = rememberNavigationEventState(currentInfo = NavigationEventInfo.None)
NavigationBackHandler(
state = navigationState,
isBackEnabled = true,
onBackCompleted = {
if (hasUnsavedChanges) {
showDiscardDialog()
} else {
onNavigateUp()
}
}
)
<br />
WRONG
Why this is WRONG : Attaching multiple NavigationBackHandler composables to
the same navigationState instance attempts to bind duplicate handlers to a
single state object, which throws an IllegalArgumentException at runtime.
// WRONG
val navigationState = rememberNavigationEventState(currentInfo = NavigationEventInfo.None)
NavigationBackHandler(
state = navigationState,
isBackEnabled = hasUnsavedChanges,
onBackCompleted = { /* Discard changes */ }
)
NavigationBackHandler(
state = navigationState,
isBackEnabled = !hasUnsavedChanges,
onBackCompleted = { /* Navigate up */ }
)
<br />
Checklis
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
