I work with DuoPlus, so take this as one operator's notes rather than a neutral review. Last month we brought in a freelance QA tester for a client's Android app. She'd always tested on a shelf of physical phones, and she came in skeptical. These are the questions she asked in the first call, more or less in her order, with the answers I gave.
"Is it a real phone or an emulator in a nicer wrapper?"
Fair question. DuoPlus cloud phones run on real ARM hardware, not x86 emulation, and each one is its own isolated Android device environment. For her that mattered for one reason: the client's app had a native library that behaved differently on emulators, and she'd been burned before.
"Which Android versions can I actually get?"
The versions I can point at are Android 10, 11, 12 and 15. She wanted 15 for the new permission prompts and 11 because the client's support tickets still came mostly from older devices. We set up one phone per version and left them running for the sprint, so she didn't rebuild state every morning.
"How do I test the signup flow without burning my own SIM?"
This was the part she liked. The client's app sends an OTP at signup. We used DuoPlus cloud numbers to receive the verification SMS for the client's own app, in the test build, on the cloud phone that was set to the target region. She could repeat the flow without asking me for a phone or waiting for a colleague in another country.
"What happens when I hand this over?"
Honestly, the question I'd want every contractor to ask. When her contract ended, we moved the phones to the next tester with team sharing. Same apps, same logged-in test accounts, same region settings. Nothing lived on her personal handset, so offboarding was removing her access, not chasing her for 2FA codes. That alone saved us an awkward week the last time a tester left.
"Can I script the boring bits?"
Partly. Bulk install, uninstall and launch across a group of phones handled the "push build 214 to all six devices" step. There's an API for teams that want to wire it into CI; we haven't gone that far yet, so I can't tell you how it holds up at scale.
What I'd flag before you try it
- It's Android only. If your app ships on iOS too, you still need another route for that half.
- Billing is per minute. Great for a two-week sprint, but if you leave a dozen phones on all month without thinking about it, you'll notice. Check the current details on duoplus.net before you plan a budget.
She ended the sprint with fewer "can't reproduce" tickets than the previous tester, though I won't pretend that's all down to the tooling. The bigger win was that the environment survived her leaving.
If you want to look at it: https://www.duoplus.net/share/market
Top comments (0)