How to send test builds to testers who'll actually open them
Most beta programs don't die from bad builds. They die from silence: twenty testers recruited, three replies received. The cause is rarely your app — it's the obstacle course between "new build is ready" and the app running on a tester's screen. Here's how to send test builds to testers with almost nothing in the way.
Friction is the silent killer of beta feedback
Walk the usual path from a tester's chair. They get an email saying a build is available on a testing track. They need the Google account they actually use added to a list — maybe it is, maybe it's their other address. They follow an opt-in link, wait for the store to show the build, install it, and only then see your app. Every one of those steps sheds people, and it sheds them quietly: nobody writes back to say "step three lost me."
Sideloading a file isn't better. The tester downloads an APK, hits Android's block on unknown sources, has to allow "install unknown apps" for their browser or file manager, finds the file again, and installs — assuming they trust a bare file enough to go through with it.
Your testers are volunteers with jobs. The builds that get tested are the ones that open in one tap.
The options, compared honestly
| Route | Tester must | Where it shines |
|---|---|---|
| Play internal / closed tracks | Be on a tester list, accept an invite, install from Play | Long-running betas; store updates and real install behavior |
| Firebase App Distribution | Accept an invite, install a tester app or download builds | Teams already in the Firebase ecosystem |
| File / cloud-drive link | Download the APK and sideload it | One-off sends to technical testers |
| Browser preview link (PreviewAPK) | Open a link — nothing else | Fast feedback rounds; non-technical and iPhone-carrying testers |
None of these is "the wrong tool" in general. Store tracks earn their friction when a beta runs for months and updates need to arrive like the real store. But for the question "does this build work and make sense?" — asked weekly, of busy people — the link that opens instantly wins. Many teams run both: links for fast rounds, a store track for the formal beta.
Step by step: send a build as a link
- Export the APK you want tested — the exact build, not a near-identical rebuild.
- Upload it to PreviewAPK. Choose the Android version (10–15) and device profile (Pixel 9 Pro or Galaxy S24) your testers most resemble — or your lowest-supported version, if compatibility is the question.
- Copy the session's share link once the device boots (seconds) and your app is running.
- Send the link with a short ask — what to try, what changed, what to ignore (next section). Testers can open it on any device, including an iPhone, and drive the app in their browser. Nobody installs anything.
- For testers who need it on real hardware, enable that build's QR code/download option. Everyone else stays on the zero-install path.
More on the sharing mechanics: share an APK with anyone, technical or not.
Collect feedback that points at the exact build
Opening the build is half the system. The other half is feedback you can act on without a follow-up investigation:
- One link per device, one thread per link. Each session's link dies with the session, so a tester thread always maps to the build that was live in it. Note the build number in the thread — "the total is wrong on build 14" — and when build 15 ships, its own new link opens the new thread.
- Ask three specific questions. "Did signup complete without help?" beats "thoughts?" Give testers a task ("add two items and check out as a guest"), not a tour.
- State what's known-broken. Testers who find the bug you already know about feel ignored; testers told about it spend their time finding new ones.
- Make replying effortless. The thread they already have — the message with the link — is the feedback channel. New forms and portals are more friction, pointed the other way.
Try it with a live device
PreviewAPK is in private beta. Get early access to test your own builds.
FAQ
Do testers need a Google account or a store invite?
Not with a link-based preview. Store tracks require the tester's email on a list and a Google account signed into Play. A PreviewAPK link opens in any browser — no account, no invite, no install — which is why casual testers follow through on it more often.
Can testers also install the build on their real phone?
Yes, if you enable it. Each build has an optional QR code and APK download, off by default. Turn it on for testers who need the app on their own hardware — scanning the code walks them to the same APK with Android's standard install prompts.
How do I know which build a piece of feedback refers to?
Send each build with its own session share link and ask testers to reply on that link's thread. Feedback then maps to exactly one build — no "which version were you on?" follow-ups, and no one testing a build you already replaced.
What does PreviewAPK cost for a beta program?
$19 per month per device with unlimited testing and unlimited link viewers — no per-tester or per-minute charges. It's in private beta; join the waitlist to lock in the launch price.
Keep going
- Share an APK — one share link per session, view-only.
- Share an APK with clients — the approval-build version of the same playbook.
- Test an Android app online — run your own pass before testers ever see the build.