From mobile-observability
Measures navigation latency from tap to interactive screen load. For tracking transitions, deep links, tab switches in iOS, Android, React Native apps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mobile-observability:navigation-latencyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Time from tap to destination screen interactive (TTI).
Time from tap to destination screen interactive (TTI).
TAP → TRANSITION → VIEW_INIT → DATA_LOAD → INTERACTIVE
|_____________________________________________|
Navigation Latency
| Rating | Duration |
|---|---|
| Good | <400ms |
| Acceptable | <1s |
| Poor | >1s |
onNavigationStart - user taps (source screen)onViewAppear - destination view visibleonContentReady - data loaded, interactiveSee references/ui-performance.md (Navigation Latency section) for:
skills/interaction-latency for button/tap response times (vs full screen loads)skills/user-journey-tracking to correlate navigation with user intentnpx claudepluginhub dorucioclea/mobile-observabilityMeasures navigation latency from tap to interactive screen load. For tracking transitions, deep links, tab switches in iOS, Android, React Native apps.
Systematically identifies mobile performance bottlenecks using platform-native metrics (Android Vitals, MetricKit). Profiles cold start, frame rendering, memory, network, and battery impact on real devices before optimizing.
Profiles and optimizes mobile app performance: eliminates jank, reduces startup time, fixes memory leaks, shrinks bundle size, and targets 60 FPS. Use when the app feels slow, drops frames, drains battery, or installs slowly.