I used to treat closed testing like the first real look at a build. That was a bad habit. You spend days rounding up testers, you wait on the clock, and then someone on Android 12 hits a crash you never saw because the only phone on your desk was already on 15.
These days I do a pre-flight pass first. Nothing fancy. I just want the APK to stand up on more than one OS version before I bother anyone else.
I work in growth marketing, close enough to the Android work that a build often lands in my chat before it lands in Play Console. Someone drops an APK and a short note about what changed. I used to install that file on whatever handset I could borrow. The borrowed phone was almost always the newest one in the office, so of course it looked fine. A local emulator missed a crash that only showed up on real ARM. I stopped treating either as the last stop before testers.
The pass I do now looks like this.
I open DuoPlus in the browser. There's a desktop client and a mobile client if I want a native window, but for a morning walkthrough I don't bother installing anything. Each cloud phone is a real ARM Android device, and each one is its own isolated environment. Nicer than a shared lab handset with someone else's test account still signed in.
Android 15 is there, which matters when a targetSdk bump is in the build. Older versions are there too. I usually start an Android 15 phone and at least one older one, often 12, sometimes 11 or 10 if a crash report already pointed at it. I don't spin up a full matrix every time. Two or three versions already catch the stupid stuff.
If the build is meant for a market I'm not sitting in, I pick a local environment from the 150+ country options before I install anything. I got burned once by a paywall that only appeared in a region we hadn't checked. I'm not going to pretend this covers every store quirk. It's still better than testing only on a Singapore handset and hoping.
Then I install the APK. When I've got more than one cloud phone running, I use the bulk install so I'm not doing the same upload three times. Same for launching the app after. Bulk uninstall is what I reach for on the next build, when I want the old package gone.
The pass itself is boring, which is the point. I walk the first-run screens, try a login, background the app and come back. If the changelog mentions a deep link, I hit that too. Purchase screens I take slowly. I keep a notes file open and write the OS version next to whatever I hit. Last week the Android 11 phone stalled on a permission dialog that Android 15 just skipped. Took maybe twenty minutes to notice. That's the kind of thing I want to find before a closed tester files it as a one-off.
If something only happens on one device, I don't try to describe the state in a long message. I use the one-click share and send that same cloud phone to whoever needs to see it. They can open it in a browser even if they haven't installed a client. We've wasted more time rebuilding a state than I want to admit.
A few of our test cases need root. DuoPlus supports that, so I don't keep a separately rooted personal phone around just for those. I only turn it on when the case actually asks for it. There's an API if you want to start devices from a script. I don't do that every morning, but on weeks where the same version matrix keeps coming back, I wish I'd set it up sooner.
Billing is per minute, which I care about because these sessions are often short. A pre-flight pass might be twenty minutes, not a whole afternoon. I'm not going to paste a rate here; look at the official site. I just like not leaving a physical lab powered all day for a walkthrough I could have finished before lunch.
After the pass, I still have to do Play closed testing the normal way. This doesn't replace testers, and it doesn't shorten Google's clock. It just means I stop handing people a build I haven't even opened on Android 12.
If you want to try the same setup I use, it's here:
https://www.duoplus.net/share/market
I still keep one physical phone in a drawer. I just don't let it stand in for every version we claim to support.
Top comments (0)