Mobile app testing on Android devices.
Run your build on cloud Android phones, Android 12 to 17, and see where it breaks.
Ready in about a minute. No hardware.
A device lab you do not have to keep
Phones on every Android version, ready when your build is.
One task on many phones
- Send the same task to several phones in one call.
- Each phone reports its own result.
- Compare Android versions side by side.
Like new before every run
- Reset a phone with one call or one click.
- Apps and data are wiped, the Android version stays.
- Every run starts from the same clean state.
ADB, when you need to go lower
- Open ADB per phone, for the addresses you list.
- It closes by itself after the time you set.
- Install builds, read logs and run your own scripts.
Watch every run live
- See the screen while a test runs.
- Every task keeps a replay with a frame per step.
- Share a phone with a teammate to look at a failure.
Start in three steps
- 1
Create a phone
Pick the Android version and the country.
- 2
Install your build
Upload the APK or install it over ADB.
- 3
Run your checks
By hand, from CI or as a task.
Other use cases
Questions about app testing
Can I choose the Android version?
Yes, per phone: Android 12 to 17. Every version is included in every plan at the same price.
How do I reset a phone between test runs?
One API call: POST /v1/devices/{id}/reset wipes apps and data and brings the phone back like new, on the same Android version, in 1 to 5 minutes.
Can I run a suite in parallel?
Yes. Give the same task to many phones in one call to POST /v1/runs, and each phone reports its own answer with a replay of every step.
Is ADB open to the internet?
No. ADB is off by default. You open it per phone for an allow-list of up to 20 IPs or CIDRs and for a set time (24 hours by default, up to 7 days), sign in with a one-time code, and every session is logged.
Can I install my own APK?
Yes: upload it in the dashboard, send it to POST /v1/devices/{id}/apk, or adb install it through the relay.
Blog
Guides on this topic
One build, three Android versions, the install errors you will meet and the logcat commands that find the crash, without a drawer of test phones.
·7 min readVersion by version, what changes for your app from Android 12 to 17, how to try target-gated behavior before you raise targetSdkVersion, and a checklist for every release.
·8 min read"Country" is four separate signals in an Android app. How to set each one in a test, why mismatches find the best bugs, and how to check store listings and prices per market.
·7 min read