Back to the catalog

published by nexus-labs-automation

18 listings on this page, in order of arrival. Each one has its own page with README, repository facts and source links.

  1. interaction-latency ★ 116
    Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggere
  2. instrumentation-planning ★ 116
    Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
  3. symbolication-setup ★ 116
    Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (Re
  4. navigation-latency ★ 116
    Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
  5. session-replay ★ 116
    Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
  6. network-tracing ★ 116
    Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debuggi
  7. crash-instrumentation ★ 116
    Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
  8. user-journey-tracking ★ 116
    Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you
  9. symbolication-setup ★ 116
    Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (Re
  10. crash-instrumentation ★ 116
    Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
  11. symbolication-setup ★ 116
    Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (Re
  12. network-tracing ★ 116
    Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debuggi
  13. crash-instrumentation ★ 116
    Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
  14. navigation-latency ★ 116
    Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
  15. interaction-latency ★ 116
    Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggere
  16. network-tracing ★ 116
    Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debuggi
  17. interaction-latency ★ 116
    Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggere
  18. navigation-latency ★ 116
    Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.