Firebase series · Part 3 of 4

Firebase App Distribution: Get Test Builds to Testers Fast

Khairul Alam·October 2026·~7 min read
FirebaseApp DistributionBeta testingCI

Before an app reaches the store, someone has to try it. App Distribution sends pre-release builds to your testers by email or link, so you can skip emailing APKs around. This is the overview; the official guide covers setup.

In 60 seconds
  • What: deliver pre-release Android and iOS builds to testers.
  • How: upload from the console, Gradle, the Firebase CLI or fastlane.
  • Who: individual testers or named groups.
  • Bonus: release notes, expiry, and tester feedback.
Contents
  1. What it is
  2. How a build reaches a tester
  3. Ways to upload
  4. Testers and groups
  5. Automating with CI
  6. Limits and good habits

1. What it is

App Distribution is a pipeline for test builds. You upload an APK, AAB or IPA, choose who gets it, and testers receive an email with a link. It supports Android and iOS, with no store review in between.

App Distribution · Releases 2.5.0 (build 412) Group: QA 2.5.0 (build 409) Group: QA 2.4.2 (build 398) Group: Beta 2.4.1 (build 390) Group: Beta
A sketch of a releases list: each build, its version and the tester groups it was sent to. (Illustration, not a screenshot.)

2. How a build reaches a tester

Developerbuild APK/AAB App DistributionGradle / CLI / CI Testers / groupsinvited by email Tester deviceApp Tester / link Feedback and crash reports flow back to you.
The path of a pre-release build, from your machine or CI to a tester’s phone.

Testers install the App Tester app (Android) or a web clip (iOS) and see every build you have shared with them. Each build carries a version, build number and release notes. On iOS, devices must be registered in your provisioning profile.

3. Ways to upload

MethodBest for
Console drag and dropOne-off builds, quick checks.
Gradle pluginAndroid developers; one command from the project.
Firebase CLIScripts and any CI.
fastlaneTeams already using fastlane for iOS and Android.

4. Testers and groups

Add testers by email and put them in groups such as QA, Design or Beta. Send a build to a group and everyone in it is notified. Writing short release notes helps testers know what to check.

5. Automating with CI

The real payoff is automation. Let the pipeline upload every successful build and notify the group.

Git push CI buildtest + assemble UploadGradle plugin QA
A common automation: every merge to a branch produces a build and notifies your testers.

Authenticate CI with a service account or a token as Google documents, and keep it in your CI secret store.

6. Limits and good habits

Setup steps change often, so follow Google’s own guides rather than a copy here.

← Back to all writing