Why Use This
This skill provides specialized capabilities for nexus-labs-automation's codebase.
Use Cases
- Developing new features in the nexus-labs-automation repository
- Refactoring existing code to follow nexus-labs-automation standards
- Understanding and working with nexus-labs-automation's codebase structure
Install Guide
2 steps - 1
- 2
Install inside Ananke
Click Install Skill, paste the link below, then press Install.
https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/navigation-latency
Skill Snapshot
Auto scan of skill assets. Informational only.
Valid SKILL.md
Checks against SKILL.md specification
Source & Community
Updated At Jan 15, 2026, 08:45 AM
Skill Stats
SKILL.md 64 Lines
Total Files 1
Total Size 0 B
License NOASSERTION
---
name: navigation-latency
description: Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
triggers:
- "deep link performance"
- "measure TTI"
- "screen load time"
- "slow screen navigation"
- "tab switch latency"
- "track screen transitions"
priority: 2
---
# Navigation Latency
Time from tap to destination screen interactive (TTI).
## Phases
```
TAP → TRANSITION → VIEW_INIT → DATA_LOAD → INTERACTIVE
|_____________________________________________|
Navigation Latency
```
## When to Use
- Tab bar taps
- List item → detail screen
- Deep link → target screen
- Any screen-to-screen transition
## Key Thresholds
| Rating | Duration |
|--------|----------|
| Good | <400ms |
| Acceptable | <1s |
| Poor | >1s |
## Measurement Points
1. `onNavigationStart` - user taps (source screen)
2. `onViewAppear` - destination view visible
3. `onContentReady` - data loaded, interactive
## Implementation
See `references/ui-performance.md` (Navigation Latency section) for:
- iOS: NavigationLatencyTracker with os_signpost
- Android: Fragment/Activity lifecycle hooks
- React Native: React Navigation listeners
## Common Mistakes
- Measuring only view appear (missing data load)
- Not correlating source → destination
- Ignoring warm vs cold screen loads
## Related Skills
- See `skills/interaction-latency` for button/tap response times (vs full screen loads)
- Combine with `skills/user-journey-tracking` to correlate navigation with user intent