Skip to content

Early Adopter Offer:Get 40% off Core & Scale for your first year with code EARLYQFView pricing

Mobile Testing

Staged rollout

Also known as: phased release, percentage rollout

A staged rollout releases a mobile app update to a growing percentage of users over days rather than to everyone at once, so field stability can be observed before full exposure.

Both major stores support it: Google Play offers staged rollouts with a percentage the developer raises over time and can halt, and App Store Connect offers phased release, which steps a version out over seven days. The purpose is the same — limit the blast radius of a defect that only appears under real usage on real hardware.

It is the mobile answer to a constraint web deployments do not have: you cannot roll a shipped binary back from users’ devices, only forward with a new build that must itself be reviewed and downloaded. That asymmetry makes pre-release signal unusually valuable, and makes the rollout percentage a genuine quality gate — crash-free session rate during the first slice decides whether the next one happens.

  • Google Play staged rollout and App Store Connect phased release both step exposure up over days.
  • There is no rollback on mobile — only a new build through review.
  • Crash-free session rate during the first slice is the gate for widening.
0

See it in your own test results

Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.

Start free with Qualflare

← Back to the testing & observability glossary.

Last reviewed September 10, 2026