skip to content

As a lead, would you make Firebase App Distribution or Play's internal testing track the team default for Android pre-release builds, and why?

level: principalimportance: should knowfreq 30%

answer

  1. who tests, and how many
  2. any variant versus the store artifact
  3. 500 per project versus 100
  4. iOS in the same place
  5. often both, at different stages

basics

~20 s

Usually App Distribution for day-to-day builds and Play's internal testing track for release candidates. App Distribution takes any signed variant on both platforms for up to 500 testers; the internal track delivers the store-signed bundle through Google Play to at most 100.

solid answer

~50 s

It depends on who is testing what. **Firebase App Distribution** takes APKs signed with a debug or app signing key, so every flavor and build type, plus AABs through a linked Play app and iOS builds, for up to 500 testers per project in groups, with per-tester status and no store listing. **Play's internal testing track** holds up to 100 testers per app and delivers the bundle through the Play Store, so it exercises Play's signing and per-device delivery. As a team default I would put nightly and feature builds for QA, product and clients on App Distribution, and send release candidates through the internal track to test what users will actually install. The costs to weigh: the full in-app SDK must stay out of Play builds, and an internal-track opt-in blocks closed and open tests.

go deeper

for a junior

Know that both App Distribution and Play's internal testing track give named testers a pre-release build, and that only the internal track installs through the Play Store.

for a middle

Compare the mechanics: tester limits of 500 per project versus 100 per app, which builds each accepts, and how testers install.

for a senior

Explain what each channel cannot prove: App Distribution never exercises Play delivery, and the internal track fits one package rather than every flavor.

for a principal

Set the team default by stage and audience, document the split, and own its edges: SDK out of Play builds, group ownership, tester budgets, and release candidates through Play.

## The decision a lead actually makes Both channels get a pre-release Android build to named people quickly, so the question is not which one works but which one the team uses **by default**, for which builds and which audiences. The answer changes with team shape: how many testers, whether they are inside the company, whether iOS ships in lockstep, and how much the team needs to test the exact artifact the store will deliver. ## What each channel is - **Firebase App Distribution** is a Firebase service outside the store. You upload a build, choose testers and groups, write release notes, and testers install through the Firebase App Tester app (Android) or a web clip (iOS). There is no listing and no review step. - **Play's internal testing track** is one of Play Console's release tracks. You publish a bundle to it, testers opt in through a link, and the Play Store installs and updates the app as it would for users. | Concern | Firebase App Distribution | Play internal testing track | |---|---|---| | Tester ceiling | 500 per Firebase project, 200 per group (increase on request) | 100 testers per app | | What you can ship | APK signed with a debug or app signing key; AAB via a linked, published Play app; iOS IPA | the bundle you would ship, delivered by Play | | Variants | any build type or flavor, each registered as its own Firebase app | the app's single package on the track | | Install path | App Tester / web clip; APKs need "install unknown apps" | Play Store, like production | | Signing on the device | your key for APKs; a test certificate for AABs | the signing Play applies to store releases | | Visibility | per-tester accepted and downloaded status per release | tester email lists in Play Console | | Retention | releases expire after 150 days; 1,000 per app | as long as the release stays on the track | | Side effects | in-app alert SDK must stay out of Play builds | an internal tester cannot also be in closed or open tests | ## Arguments for App Distribution as the default - **Every variant, every night.** A `staging` flavor pointing at a test backend, a debuggable build for QA, a `demo` flavor for a client: each is just another upload. The internal track serves one package and is shaped around builds you would publish. - **Both platforms, one place.** Android and iOS testers sit in the same groups and get release notes the same way, which matters when a PM and two external clients test both apps. - **People management.** Groups carry access to every release sent to them; the console shows who accepted and who downloaded. Five hundred testers per project leaves room for stakeholders. - **Nothing touches the store.** A broken nightly never sits on a Play track, and an AAB uploaded through App Distribution does not even appear in the Play developer account. ## Arguments for the internal track 1. **It tests the real artifact.** The release candidate goes through Play's signing and per-device delivery, which is where problems that never appear in a sideloaded APK show up: a missing split, a signature-dependent API, in-app updates. 2. **No sideloading friction.** Testers install from the Play Store; nobody enables unknown sources or the internal app sharing switch. 3. **It is on the path to release anyway.** The same release can move on to closed testing and production. 4. **Fast.** A new bundle on the internal track normally reaches testers within minutes. Its limits are real: 100 testers per app, and a user who opts into the internal test is no longer eligible for the app's closed or open tests until they opt out. ## A defensible default Most teams end up with **both, at different stages**: - **App Distribution** for continuous builds: nightlies, feature branches, QA and stakeholder builds across flavors and both platforms. Upload from CI with a service account; manage audiences as groups. - **Play's internal testing track** for **release candidates**, so the last checks run on what users will install, followed by closed testing and staged production rollout. The lead's job is to write that split down and enforce the edges: the full App Distribution SDK never ships in a Play variant (its self-update code can breach Google Play policy even unused), group membership has an owner, external testers' devices and accounts are budgeted, and nobody treats an App Distribution pass as proof that the Play-delivered build works. A team without iOS and with a handful of internal testers can reasonably use the internal track alone; a team with clients, several flavors and two platforms rarely can.

  • QA passed a build from Firebase App Distribution; why might the same version still fail once Play delivers it?
    The tested APK was sideloaded and signed by your own key, or for a bundle by App Distribution's test certificate, while Play delivers device-specific APKs signed for the store. Signature-dependent APIs, missing splits and in-app update flows can behave differently. That is the argument for running release candidates through Play's internal testing track before closed testing and production.
  • Your external clients test both apps; what does that change in the choice?
    It favours Firebase App Distribution for them: one place for Android and iOS builds, groups that grant access to every release sent to them, and per-tester accepted and downloaded status. Budget for iOS ad hoc device registration, and keep the internal track for the smaller internal group checking release candidates.

App Distribution is the rehearsal room where you hand scripts to whoever needs one, any draft, any cast; the internal track is the preview night on the real stage, with the house's lighting and ushers, for a smaller invited audience.

  • Play's internal testing track can hold 500 testers per app.
  • AABs uploaded to App Distribution land on Play's internal track.
  • An internal tester can join the closed test without opting out.
  • An App Distribution pass proves the Play-delivered build works.
  • Shipping the full App Distribution SDK in the Play build is harmless.