How to roll out an app update safely to a group of Android test phones in stages

In short: For test phones on your own bench, install the new build on a few canary phones, run your checks there, then install it on the rest. BenchFleet's group actions install an APK on a group at once, and its deployments run the new version of a workflow on canary phones before every phone, with one-click rollback. Both need Pro, at £12 a month + VAT.

A staged rollout limits the damage of a bad build: a few devices get it first, you check them, and only then does everyone else. On Google Play this is built into the release tracks. On a bench of test phones you do it yourself, or let a tool keep the stages for you. Google Play facts checked on 23 October 2026 in its Play Console help.

Free for up to 3 phones, with no account. Pro adds workflows, schedules and AI for up to 25 phones from £12 a month + VAT.

Download free See pricing

The options compared

Option	Who gets the update	How stages work	Rollback	Website
BenchFleet	Phones on your bench, by USB or Wi-Fi	Group actions install an APK on a canary group, then the rest; deployments run a new workflow version on canary phones first	Roll back a workflow version in one click; reinstall the previous build on the group	benchfleet.com
Google Play internal testing	Up to 100 testers per app	New builds reach testers within minutes	Publish another build	support.google.com
Google Play closed testing	Email lists or Google Groups you choose	Separate tracks for separate groups	Publish another build	support.google.com
Google Play open testing	Anyone who joins; unlimited, or capped at 1,000 or more	One public test track	Publish another build	support.google.com
Google Play staged rollout	A percentage of production users you choose	You raise the percentage; it never rises on its own	Halt the rollout; users who have the update keep it	support.google.com
An MDM or EMM	Enrolled company devices	Depends on the product's app-deployment policies	Depends on the product	Your MDM's own documentation

Google Play's staged rollouts work for updates, not for an app's first release.

Stages on your own test bench with BenchFleet Pro

BenchFleet is a desktop app that runs the Android phones connected to your computer. A staged rollout to those phones looks like this:

Make a canary group. Pick two or three phones that cover your users' Android versions and screen sizes, and put them in a group by hand or by rule.
Install the build on the canaries. A group action installs the APK on every phone in the group at once and shows the result for each phone. BenchFleet asks you to type the number of phones before an action on many phones runs.
Run your checks there. Start your recorded workflows on the canary group, or let a schedule run them. When an app that a deployed workflow uses is updated on a phone, BenchFleet suggests running that workflow on that phone first.
Look at the results. Replay any failed run step by step with the screens before and after each step: see replaying an automation step by step.
Install on the rest. Run the same group action on the remaining phones, or on every phone.

New workflow versions follow the same rule

Your checks change too. A deployment decides which version of a workflow runs where: the stable version everywhere, and a new canary version on the canary phones while the canary runs.

Promotion is earned. A canary version can be promoted to every phone after a run of successes on the canary phones, a minimum time and no attention items: by default 5 successful runs in a row and 24 hours. Promotion then needs a person's approval, even for the owner.
Rollback is one click and needs no approval: during a canary it ends the canary, after a promotion it restores the previous stable version.

Who it is for

QA teams that install every build on a bench and want a bad one caught on two phones, not twenty. See managing a bench of Android test devices.
Teams that run routine jobs on company phones and need a changed workflow tried on a few phones first. See scheduling jobs on a group of phones.

Google Play is a trademark of Google LLC. BenchFleet is not affiliated with Google.

Questions

How do I roll out an Android app update in stages?

For users on Google Play, publish to internal or closed testing first, then use a staged rollout in production, where you choose the percentage of users and can halt and resume. For phones on your own bench, install the build on a few canary phones, check it there, then install it on the rest.

How many testers can Google Play's internal testing track have?

Up to 100 testers per app, according to Google's Play Console help. Closed testing uses email lists or Google Groups, and open testing can be unlimited or capped at 1,000 or more.

What is a canary phone?

One of a few phones that gets a new version first. If it behaves, the rest follow; if not, only the canaries were affected and you roll back.

Does BenchFleet promote a canary on its own?

No. A new workflow version becomes eligible for promotion after enough successful runs on the canary phones, a minimum time and no attention items, by default 5 runs in a row and 24 hours, and promotion then needs a person's approval. Rollback needs no approval.

Does BenchFleet notice when an app is updated on a phone?

Yes. When an app that a deployed workflow uses is updated on a phone, the deployment suggests running that workflow on that phone first, as a canary for the app update, and the Attention page shows it.

Start with the Free plan