App Updates and Phased Rollouts
Releasing an update is a moment of risk: a bug that slips through can reach every user at once. Phased rollouts let you release gradually, watching for problems before everyone gets the new version.
This simple practice dramatically reduces the impact of any issue that testing missed.
Why Not Just Release to Everyone
It is tempting to push every update straight to your whole user base, but that turns any missed bug into an instant, large-scale problem. A phased rollout buys you time and information: you see how the new version behaves in the real world on a small slice of users before committing to all of them. It is one of the simplest, cheapest forms of insurance we can give a release.
How a Phased Rollout Works
- Release to a small percentage of users first.
- Monitor crash rates and feedback closely.
- Increase the percentage in steps if all looks healthy.
- Pause or roll back instantly if a problem appears.
Why It Matters to You
A bug caught at five per cent of users is an inconvenience; the same bug at one hundred per cent is a crisis. Phased rollouts protect your reputation and give us a safety net on every release.
Frequently Asked Questions
Does this slow down releases?
Only slightly, and the safety is well worth it. Urgent fixes can still be released to everyone immediately when needed.
Can users force the update sooner?
Yes, users updating manually from the store may receive it ahead of the automatic rollout schedule.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.