<< All versions
Skill v1.0.0
currentAutomated scan100/100nexus-labs-automation/mobile-observability/navigation-latency
──Details
PublishedSeptember 25, 2026 at 11:04 PM
Content Hashsha256:99219f4ee2fcf025...
Git SHA488c97f1247a
──Files
Files (1 file, 1.6 KB)
SKILL.md1.6 KBactive
SKILL.md · 65 lines · 1.6 KB
version: "1.0.0" 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
onNavigationStart- user taps (source screen)onViewAppear- destination view visibleonContentReady- 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-latencyfor button/tap response times (vs full screen loads) - Combine with
skills/user-journey-trackingto correlate navigation with user intent