I work with DuoPlus, and this is the release check we run for the small client apps our team maintains. It's not fancy. It exists because we shipped a broken permission prompt on Android 12 once, and the client found it before we did. That was a bad Friday. (The workflow below is real; the anecdotes are a composite of a few releases, simplified.)
The idea: before an update goes to the store, the build gets installed on four long-lived cloud phones, one each on Android 10, 11, 12 and 15, and two people walk the same short script. The phones never get wiped between releases, which turns out to be the useful part.
Why long-lived phones instead of fresh emulators
Fresh emulators are clean, and clean is exactly what your users are not. Our users upgrade from the previous version with old data, old settings and old permissions. When we kept the same four phones around for months and just installed each new build on top of the last one, we started catching upgrade-path bugs: a migration that silently dropped a setting, a notification channel that kept its old name, a cached token that the new version didn't expect.
So the rule is: never reset the release-check phones unless a test specifically needs a first install. For first installs we have a fifth phone we do reset.
The setup (about 20 minutes, once)
- Create four cloud phones: Android 10, 11, 12 and 15. In DuoPlus each one is its own isolated device environment, so app data on one doesn't leak into another.
- Name them plainly:
rc-a10,rc-a11,rc-a12,rc-a15. Clever names lose meaning by month three. - Set the region on each to the client's main market. If the client sells in two countries, we split: two phones in each region.
- Install the current production version from the store and log in with the client's test account.
- Share all four with the second QA person. Sharing is per device, so they see the exact logged-in state I left, without me handing over a password.
The script (about 25 minutes per release)
We keep it on one page. If it gets longer, we cut something.
- Install over the top. Upload the release APK and install it on all four at once using bulk install. Don't uninstall the old version first.
- Cold start. Force-stop and launch. Time it roughly; we only care about "noticeably slower than last time".
- Permissions. Trigger every runtime permission the app asks for. Newer Android versions changed how notification and location permissions are requested, and that's the area where our Friday bug lived.
- Background and return. Leave the app for five minutes, come back. Check the session is intact.
- Notifications. Send a test push from the client's backend. Check it lands, the channel name is right, tapping it opens the right screen.
- Sign-up flow on the reset phone only. For the app's own OTP step we use a cloud number to receive the verification SMS on the fifth phone. This is our own client's app and their own test environment; we're checking that their flow works, nothing else.
- Region check. Prices, date formats and store links in the right locale.
Each person takes two phones, then we swap. Swapping is the whole trick: the second pair of eyes catches what the first got used to.
What we write down
One line per phone per release in a shared sheet: version installed, pass/fail, and a note if anything felt off. "Felt off" notes are allowed. Two of our better catches started as "this screen feels slower?" and turned into real regressions after we compared against the previous row.
Costs and habits
DuoPlus bills per minute, so the phones are on only during the check. We switch all five off at the end, and that's on the checklist too, because the one time we forgot, nobody noticed until the next release. If you prefer a flat monthly cost for always-on devices, this workflow still works, it just changes the habit.
What this doesn't cover
It's not a replacement for automated UI tests or a device farm with hundreds of models. We have neither the budget nor the need. It covers the one thing small teams keep missing: the upgrade path on the Android versions real users are on. If you're in the same spot, four phones and a one-page script is a cheap place to start.
If you want to look at the cloud phones we use: https://www.duoplus.net/share/market

