calubecalube/mobile-observability/skills/navigation-latency/SKILL.md

navigation-latency

Skill116 starsChanged 11 months agoMITView on GitHub

Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.

In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crash-instrumentationSkill
- instrumentation-planningSkill
- interaction-latencySkill
- network-tracingSkill
- session-replaySkill
- symbolication-setupSkill
- user-journey-trackingSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Not correlating source → destination
line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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 visible
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free