Agent skill
interaction-latency
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
Install this agent skill to your Project
npx add-skill https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/interaction-latency
SKILL.md
Interaction Latency
Time from user tap to action successfully completed.
When to Use
- "Add to cart" button tapped → cart updated
- "Submit" button tapped → form processed
- "Like" button tapped → state changed
- Any tap that triggers async work
Measurement Pattern
TAP → START_SPAN → [async work] → END_SPAN
- Capture tap timestamp
- Start span with operation name
- End span when action confirms success
- Include success/failure outcome
Key Thresholds
| Rating | Duration |
|---|---|
| Good | <300ms |
| Acceptable | <1s |
| Poor | >1s |
Implementation
See references/ui-performance.md (Entry Point Latency section) for platform-specific code.
Common Mistakes
- Ending span on API call start (not completion)
- Not tracking failure cases
- Missing the tap timestamp (starting late)
Related Skills
- See
skills/navigation-latencyfor screen-to-screen transitions (vs single-tap actions) - Combine with
skills/user-journey-trackingfor friction detection on key interactions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
crash-instrumentation
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
user-journey-tracking
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
navigation-latency
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
instrumentation-planning
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
Didn't find tool you were looking for?