DEV Community

Growth Marketing
Growth Marketing

Posted on

Setting up bulk app install and launch across a group of cloud phones before a release check

I work with DuoPlus, and the thing I get asked about most by small QA teams isn't some fancy feature. It's this: "How do I get the same build onto a dozen phones without doing it twelve times?"

So here's the routine I use before a release check. Most of the value is in doing the boring parts in the same order every time.

One note before starting: I'll describe the steps generically. Menus and labels change, so I'll say "in the DuoPlus console" rather than pretend to quote exact button names. If something looks a bit different on your screen, the idea still holds.

What you need first

  • A set of cloud phones you're going to test on. For a typical check I want a spread of Android 10, 11, 12 and 15.
  • Your build file (APK) and, if you have them, any companion apps the test depends on.
  • A short test script. Even five lines in a doc is fine. "Open app, log in with test account, go to checkout, back out." Something everyone runs the same way.

If you're testing your own app's sign-up flow, a cloud number that receives verification SMS can be useful here too. Keep that strictly to your own app.

Step 1: Make a group just for this release

Don't install onto "all phones." That's how a client's long-running device ends up with a test build on it, which you'll then have to explain.

In the DuoPlus console, put the phones you want into a group and give it a name that says what it is. I use something like release-2026-11-qa.

I keep client devices and test devices completely separate. Client phones are long-term, fixed device environments; they don't get pulled into release groups. Test phones are the ones I'm happy to wipe.

Step 2: Check each phone's basics before anything goes on

This is the step people skip, and it's the step that saves the most time later.

Open each phone in the group (or at least skim through them) and check:

  1. Android version is what you think it is.
  2. Region and proxy settings are set per device the way your test needs. If you're checking a German storefront, that phone should actually be set up for Germany.
  3. No leftover version of your app from the last check. If there is, remove it now, not halfway through testing.
  4. Storage isn't nearly full.

A few minutes here beats finding out on phone nine that it's on the wrong region.

Step 3: Bulk uninstall old builds

If several phones still have last week's build, select the group in the console and use the bulk uninstall option to clear the old version from all of them at once.

I do this as its own step rather than relying on "install over the top," because occasionally an upgrade path hides a bug that a fresh install would show, and vice versa. Decide which one you're testing. For a normal release check, I want fresh instalss.

Step 4: Upload the build and bulk install

Upload your APK through the console, then pick the group and run a bulk install.

A few things I've learned the hard way:

  • Name your file with the version in it. myapp-3.4.1-rc2.apk, not app-release.apk.
  • Install companion apps in the same pass if your test needs them, so every phone ends up in the same state.
  • Wait for it to finish on every phone before moving on. If one fails, deal with that phone on its own rather than re-running the whole group.

Step 5: Bulk launch and eyeball the first screen

Now launch the app across the group in one go. Then go phone by phone and just look at the first screen.

You're not testing yet. You're checking that it opened, it didn't crash on start, and the first screen looks sane on each Android version. This catches the obvious stuff (missing permission prompt on one version, a layout that's clearly broken on another) before anyone starts working through the script.

If you're using root for debugging logs, this is a good moment to grab startup logs from any phone that looked off.

Step 6: Hand phones out to testers

If more than one person is running the check, share phones to teammates from the console. One-click sharing means they open the device already in the state you left it, app installed and launched, no re-logging in.

I split it by Android version: one person takes 10 and 11, another takes 12 and 15. Clear ownership, no two people tapping on the same phone at the same time.

Step 7: Run the script, write things down

Everyone runs the same short script on their phones. Notes go into one shared doc, with the phone name and Android version on every line. "Checkout button cut off — release-qa-03, Android 12" is useful. "Button looks weird" is not.

Step 8: Clean up when you're done

After the check:

  • Take back shared access from testers.
  • Decide whether to keep the build on the phones for a follow-up check or bulk uninstall it now.
  • If you won't need the test phones for a while, remember billing is per minute, so there's no point leaving phones running for nothing.

Optional: do it with the API

Once you've run this by hand a few times and the steps stop changing, it's worth scripting. DuoPlus has an API, so install, launch and uninstall can be wired into whatever you already use for builds. I wouldn't start there, though. Do it manually until you trust the routine, then automate the routine you trust.

A short hypothetical

Made-up example, to show the timing: a two-person team has a release candidate on Thursday morning. They group eight test phones across four Android versions, clear old builds, bulk install, bulk launch, and spot that the app opens to a blank screen on one version. They catch it before lunch instead of after a client emails about it. That's really the whole point.

If you want to try it on a small group first, the console is at https://www.duoplus.net. Start with four phones, one per Android version, and run the eight steps once. You'll find your own shortcuts quickly.

Top comments (0)