菜单
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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 |
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 intentConfigure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.