How to Distribute an Android App to Testers Without the Play Store (2026)

You can distribute an Android app to testers without the Play Store by sharing a universal APK — via a direct link, a QR code, an OTA tool, or Play's own Internal App Sharing. The one gotcha that trips up most teams: you can't install an .aab directly. Google Play turns the App Bundle into APKs on its side, so for off-Play distribution you have to generate a universal APK yourself with bundletool.

Android distribution has fewer signing hoops than iOS, but the .aab confusion and some device-side settings catch people out. Here's the clean path.

The AAB gotcha

Since Google Play requires the Android App Bundle (.aab) for new apps, that's often what your build produces — but an .aab is a publishing format, not an installable one. To distribute off-Play you need an APK. Don't ship split APKs to testers either: they fail to install on Android 10+ when the companion splits are missing. Build a single universal APK:

bundletool build-apks \
  --bundle=app-release.aab \
  --output=app-release.apks \
  --mode=universal

# then extract the universal.apk from the .apks archive (it's a zip)
unzip -p app-release.apks universal.apk > app-release.apk

That app-release.apk installs on any tester's device. See .ipa vs .apk vs .aab for the format differences.

Ways to distribute off-Play

• Direct APK (link or QR) — host the universal APK and share the URL; simplest for one-offs.
• OTA tools — Appisto, Firebase App Distribution or Diawi give you tester groups, release notes and a CI/CD API so uploads are automatic. See the Diawi alternatives and best internal distribution tools.
• Play Internal App Sharing / Internal Testing — still Google, but review-free instant links for QA; covered in Play testing tracks explained.

The device side: unknown sources and restricted settings

Testers install from outside the Play Store, so they'll need to allow it:

• "Install unknown apps" — Android asks the user to permit the installing app (browser, files, or your OTA app) to install once.
• Android 13+ restricted settings — sideloaded apps can be blocked from sensitive permissions until the user explicitly allows them under App info → the three-dot menu → Allow restricted settings.

Heads-up: Android Developer Verification

Off-Play distribution is changing. Google's Developer Verification requirement starts September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, and rolls out globally in 2027. It means apps installed outside Google Play will need to come from a verified developer (a $25 registration plus identity verification), with a free tier that caps distribution at around 20 devices. If you distribute Android builds off-Play, plan for verification now rather than later.

Frequently asked questions

Can I install an .aab file directly? No — an .aab is a publishing format Play uses to generate APKs. Build a universal APK with bundletool and share that.

How do I send an APK to someone for testing? Share the universal APK via link, QR or an OTA tool; the tester allows installation from the source once and installs. A platform adds tester groups and release notes.

Why won't my APK install? Usually it's an .aab instead of an APK, a split APK missing its splits, blocked unknown-sources, or Android 13+ restricted settings. Use a universal APK and allow the installer.

Key takeaways

• You can't install an .aab; build a universal APK with bundletool for off-Play distribution.
• Share it via direct link, OTA tool, or Play Internal App Sharing.
• Testers must allow unknown-sources installs and, on Android 13+, restricted settings.
• Developer Verification arrives September 30, 2026 (BR/ID/SG/TH) and globally in 2027 — plan for it.
• Appisto handles Android and iOS from one workflow, with tester groups and a CI/CD API. See distributing iOS without the App Store for the other half.