Staged rollout is a Google Play release mechanism that ships a new app version to a configurable percentage of users before full rollout. The developer sets the initial percentage (commonly 1% or 5%), monitors crash-free rate and other quality metrics, and incrementally increases the percentage (e.g., 5% → 20% → 50% → 100%) over hours to days. If a critical issue is detected mid-rollout, the developer can halt the rollout, preventing the bad build from reaching more users.
Typical staged-rollout cadence
- 1-5%: first 24-48 hours. Check crash-free rate, ANR rate, key flow conversion. Pause if any regression > 0.1%.
- 5-20%: next 24-48 hours. Wider distribution validates that the build performs across more device + region combinations.
- 20-50%: next 2-3 days. By this point, severe regressions have surfaced. Continue if metrics are stable.
- 50-100%: final ramp. Complete rollout within 5-7 days of initial release.
Apple's equivalent: "Phased Release" in App Store Connect. Same concept, slightly different implementation. Apple's phased release follows a fixed 7-day schedule (1% → 2% → 5% → 10% → 20% → 50% → 100%) with daily automatic increments. Less granular control than Google Play's percentage-based system, but the underlying purpose is identical.
Critical capability: the ability to halt a rollout. If crash-free rate drops, ANR rate spikes, or a key conversion metric regresses, the developer halts the rollout from the Play Console. The build remains available to users who already updated, but no new users receive it. Hotfix release can then be staged as a new rollout, replacing the broken one.