Process
Setup
Integrate into your existing dev cycle processes:
- Build:
Android - Gradle, iOS - XCode & iOS - Bazel - Distribution:
iOS - App Distribution - CI/CD:
Android - Gradle - User Flow Annotation API - Manually mark user flows: Android - Usage Instructions

Build
Run build with our plugin locally or in CI to create an automatically instrumented version of your app.

Review
Record traces and screen recordings of your app and upload them to our platform to diagnose performance improvement opportunities of any user flow in your app.
Best Practices
Set the baseline
Initial app diagnostics and performance benchmarking. Set initial benchmarks or improve your existing performance metrics: analyze the most critical user flows of your app - look for the biggest delays between function calls in the critical execution path to set prioritization
- How often: once
- Effort: avg 15-30 min per user flow per trace
Recurring
Analyze the root cause of any performance regression: Detect/remediate the root cause for reported performance regressions before shipping to users. Debug performance regression and crashes
- How often: recurring
- Effort: avg 15-30 min per user flow per trace
- Who: Typical/recommended users
- Engineer: Empower engineers to debug root-cause of the performance of their own code
- Performance Engineer: Give performance-focused teams a powerful tool to investigate underlying factors of performance
- QA: Elevate QA team's effectiveness with the ability to capture and convert experiential performance issues into actionable, quantitative reports
Product
Prioritize performance work and increase engagement for the most impactful user flows of your app