The build
In setup, choose Android and drop an APK. Builds up to 50 MB upload straight from the browser; if yours is bigger (real apps often are), tell us and we switch your workspace to the large-build upload. A new build replaces the old one: upload it again whenever you ship to staging.
Give Burhan a staging build: one that talks to your staging API, with the test accounts above. Debug or release both work; no Play Store listing needed. Apps that refuse to run on an emulator (root or emulator detection) need that check off in the staging build.
Where it runs
Your app runs on Android emulators on Burhan's own servers in Belgium (Google Cloud, europe-west1). Each test account is signed in on one phone at a time; more accounts, or twins, mean more phones on one run. The phone's location is set to where your users are, so maps and "nearest branch" behave. Staging that only lets in known IPs needs our servers' addresses allowed.
What Burhan can and can't tap
Burhan reads the screen's view tree (what accessibility tools see) and the screenshot, then taps, types, scrolls and swipes. It gets past Android's own dialogs by itself: permission prompts, intro slides, a field that already holds a value.
- Can: everything your app draws, including custom controls, scrolling lists, bottom sheets, date pickers and WebViews.
- Can: sign in with a password, an authenticator code, or an email or SMS code sent to the project's test inbox.
- Can't: pay with a real card, use the camera, NFC or fingerprint, or receive an SMS on a real number.
- Can't: finish Google or Apple sign-in on the device (they block automation): use a password account.
- Can't: follow a journey into another app (WhatsApp, the dialer, a bank). The step is reported as blocked, with the screen it reached.
Arabic UI
If your app has an Arabic version, tick it and each journey runs once per language, on the same phone with its language switched. Burhan reads Arabic screens and writes its notes in Arabic too; the Arabic and RTL page says what it looks for.
What you get
A run per journey: pass, fail or blocked, the failing step, what Burhan saw, and the video with taps drawn on it. An Android run costs 2 credits, a web run 1. Reds and blocked runs collect on the Attention page, where you file the ticket, say Not a bug, or tell Burhan why it was blocked, and it learns.