Android testing for remote QA — every version, no device lab

Your users run Android 10 through 15 on Pixels, Galaxies, and everything in between. Your desk has one phone, and it isn't the one in the bug report. PreviewAPK gives remote QA testers a real device in the browser for any build: pick the version and profile, and the app is installed, launched, and ready to test in about a minute.

The matrix is bigger than your desk

Android fragmentation is not an abstraction when you're the one holding the ticket queue. A crash reported on Android 12 tells you nothing if the only phone you own runs Android 15. Layout bugs live at specific screen sizes and densities. "Works on my device" is the most expensive sentence in QA — it closes a ticket that reopens two releases later.

The traditional answer is a device lab: shelves of phones that need charging, updating, wiping, and replacing, in one office, while your testers are in three other cities. For a remote QA tester or a testing agency working across client projects, the lab is either unaffordable or in the wrong building. So coverage quietly shrinks to whatever hardware happens to be nearby — and the gaps ship.

Pick the configuration, get the device

• Upload the build, choose the target. Android 10, 11, 12, 13, 14, or 15, on a Pixel 9 Pro or Galaxy S24 profile (or stock). A real device boots in the cloud in about a minute, app installed and launched.
• Run the same build across versions back to back. Verify the fix on the version it was reported on, then spot-check the oldest and newest versions you support — no emulator images to maintain, no hardware to swap.
• Work from anywhere. The device is in your browser, so a tester in another timezone starts testing the moment a build lands, not when a physical phone gets shipped or a lab slot opens.
• Sessions clean up after themselves. A session auto-stops after 15 minutes idle, so forgotten sessions don't linger — and the build's link stays valid for the next round.

Bug reports with a link beat bug reports with a paragraph

Every session gets its own share link. Attach it to the ticket. Now the developer opens the exact build you tested — not the latest build, not a rebuild from source, the same APK — and the environment ambiguity that eats the first day of every investigation is gone. No "which build were you on?", no "can you reproduce it on the current one?"

Reproduction sessions get shorter, too. Open the link on a call: you drive the device in your browser, the developer watches the same session live, and the bug either reproduces in front of both of you or it doesn't. Steps to reproduce still matter — but they stop carrying the entire weight of describing a device, a version, and a build in prose.

An honest scope note: what this doesn't replace

PreviewAPK complements your existing setup rather than replacing it. Automated suites should keep running your regression checks — they're faster and they don't get tired. Physical devices remain the final word for hardware-dependent behavior: Bluetooth, NFC, camera quality, biometrics, sensors, and GPU-heavy paths.

Where browser devices win is the wide middle: exploratory testing, version and layout coverage, fix verification, and reproducing user reports on the version they actually run. And when a check does need real hardware, the device can carry a QR code (off by default, enabled per device) that installs the exact same APK on a physical phone — so the hardware pass runs the identical build you already tested.

What it costs

PreviewAPK is a flat $19/month per device with unlimited testing — no per-minute metering ticking while a session sits open during a long investigation, no per-device or per-seat pricing. It's in private beta now; the waitlist locks in the launch price.

Exploratory testing your tools can drive too

Manual sessions in the portal are the core, but the same device answers to a CLI, a REST API, and an MCP server. A script can push the build under test and start the session; an AI agent can drive an exploratory pass — tapping flows, typing into forms, capturing screenshots — and leave the session, with its notes, for a human to continue. Driver modes keep it sane: exactly one side, human or agent, has the wheel at any moment.

FAQ

Can scripts or AI agents drive PreviewAPK sessions?

Yes, through the account API key: push a build, start a session, tap, swipe, type, and capture screenshots via the CLI, REST API, or MCP. A session is either agent-driven (the API drives; the owner watches) or user-driven (the owner drives in the portal; API input is refused), and control can be handed over mid-session without a reboot.

Which Android versions and devices can I test on?

Android 10 through 15, on Pixel 9 Pro and Galaxy S24 device profiles. Version and profile are device settings, so the same build can be checked across the matrix by switching the device between runs.

How does a preview link improve a bug report?

Each build's run has its own link, and while it runs it opens that exact build. Attach it to the ticket and the developer starts from the same build and configuration you tested — and can watch live in the browser while you reproduce the issue.

Does PreviewAPK replace automated testing or real phones?

No — it complements both. Keep automation for regression suites and physical devices for hardware-dependent checks like Bluetooth, NFC, camera, and biometrics. PreviewAPK covers fast manual and exploratory testing across versions; a build's QR code can install the same APK on a real phone for the hardware pass.

How much does PreviewAPK cost for QA testing?

$19 per month per device with unlimited testing — no per-minute metering, which matters when a session sits open during an investigation. PreviewAPK is in private beta; join the waitlist to lock in the launch price.

Keep going

• For client approvals — builds clients review without sideloading.
• For freelance developers — deliver builds clients actually open.
• For agencies — preview links across every client project.