How to catch performance regressions before a release — Articles
Blog post from Expo
Performance regressions can be caught before broad release by defining P90 budgets for key metrics such as startup time, bundle load, rendering, interactivity, and frozen frames, then comparing each candidate release with the prior production release on real devices. Effective budgets combine an absolute ceiling with a relative-change limit, since a release may remain below a fixed threshold while still substantially worsening performance, and release-based comparisons avoid the misleading effects of time-indexed dashboards during low-adoption rollouts. Native builds should be evaluated by app version, while React Native over-the-air JavaScript updates require tracking by update ID because multiple updates can share one native version. Staged rollouts provide enough real-user data to assess a release before full deployment, allowing teams to expand a successful rollout or hold and revert a failing one. Automation requires machine-readable metrics, a scheduled or CI-driven comparison script, and clear actions for pass or failure; Expo’s EAS Observe and EAS Workflows can support this process through production telemetry, JSON CLI output, staged update rollouts, and workflow approvals, although teams must define their own budgets and scripts.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.