How to share an APK with testers (2026 guide)

Sending an APK is easy; making sure every tester installs the right, newest build without errors is the hard part. Here are the options and what to watch out for.

1. Chat or cloud drive

Quick for one tester, but files pile up (app-release-final-v2.apk), testers install old builds, and nobody knows which one is current.

2. Google Play testing tracks

Internal testing on Play is reliable and supports in-app purchases, but needs a Play Console listing, testers with Google accounts on the list, and an app bundle signed with your upload key.

3. Firebase App Distribution

Free and solid if you already use Firebase. Testers join through an email invitation or invite link and sign in before installing.

4. One install link per app

Tools like Digidropp give each app one link (and a QR code) that always installs the newest build. Testers bookmark it once; no accounts needed.

• Upload from the dashboard, your terminal (digidropp deploy) or GitHub.
• Every pull request can get its own link, so reviewers test before merging.
• Each build is checked before testers install it.

Avoid “App not installed”

Most failed installs come from two things, both of which Digidropp checks on every upload:

• The new build is signed with a different key than the one installed (common when builds come from different machines).
• The new versionCode is lower than the installed one.

Warnings testers may see

Chrome warns about APKs downloaded outside Google Play, and Play Protect may ask for confirmation. Since 2026, some countries also require apps from registered developers; see the Android developer verification guide.

Digidropp · Guide · Docs · Alternatives