All posts

Firebase App Distribution: test builds without the store

· 6 min read

You have a build and a handful of people willing to try it. You don't want to wait for a store review, or you're not ready for Play closed testing or TestFlight yet. Firebase App Distribution is one way to get the build onto phones. This post covers what it is, how testers get the build on Android and iOS, what it costs, and when another route is the better pick.

What it is, and what it isn't

I read Google's Firebase App Distribution overview on 10 November 2026. It describes the service as a way of sending pre-release builds to trusted testers, for both iOS and Android. You upload a build, pick who gets it, and App Distribution emails them.

It is not a store. There is no listing, no public page and no review of your app by Google Play or the App Store. Testers install the build outside the store, through App Distribution. That is the whole point: it's quick. It's also why it behaves differently from Play testing, as you'll see below.

Android: uploading a build

The overview says you can upload your APK, AAB or IPA "using the Firebase console, fastlane, Gradle, or the CLI tools". The Gradle route is listed for Android only. The Firebase console, the Firebase CLI and fastlane work for both platforms.

The Android console guide walks through the simplest way. It describes an APK upload; the same page has a separate AAB tab, so read that one if you build app bundles. The steps:

  1. Add Firebase to your Android project and register the app.
  2. Open the App Distribution page in the Firebase console and select your app on the Releases page.
  3. Drag the build file in.
  4. Pick tester groups and individual testers, and add release notes.
  5. Click Distribute.

How testers are invited

You can add testers one by one and organize them into groups. Per Google's tester page, a Firebase project can have up to 500 testers and a group up to 200. Going past that needs a free increase request.

There are also invite links. Google's invite links page describes one as "a unique URL that lets testers enter their email addresses to sign up to test an app". A link can point at an app or at a group. Without a group, testers are only added to the latest distributed release.

New testers get an email invitation. Existing testers get an email when a new build is ready. You can see in the console whether each tester accepted and whether they downloaded the app.

What testers do

The tester setup page says App Distribution emails the tester "an invitation with instructions on how to install and test the build". The tester signs in with Google and accepts. Google says they can use any Google account, not only the one that received the email, and that each invitation can be accepted once. Testers have 30 days to accept before the invitation expires, and you can resend it from the tester's row.

The page I fetched didn't describe the Android install steps in detail, such as any extra app or phone setting. So I won't claim any. Send your testers the invite email and ask them to follow its instructions.

iOS: devices and UDIDs

The iOS upload works the same way, with an IPA file instead of an APK. The difference is who can install it. Google's page on registering additional iOS devices says an ad hoc build installs only if the device's "unique device identifier (UDID) is included in the build's provisioning profile".

The flow looks like this:

  1. The tester opens the invitation in Safari, signs in with Google and registers their device.
  2. App Distribution collects the UDID and emails it to you.
  3. You add the device in your Apple developer portal and to your provisioning profile, then download the updated profile.
  4. You rebuild the app with that profile and distribute it again.
  5. The tester gets an email and installs the build.

Google adds one warning: your Apple developer account "may only allow you to import a limited number of devices per year". I didn't find a number in the pages I read, so check Apple's current limit in your developer account before you count on a big group.

That extra round trip per new tester is why many iOS makers use TestFlight for outside testers instead. I wrote about it in TestFlight external testers and the public link.

Expiry, release notes and feedback

  • Builds expire. A distributed build stays in the dashboard for 150 days, and an expiration notice appears 30 days before that.
  • Release notes. You add them in the console after the upload and before you click Distribute.
  • Release links. You can copy a link to a specific release, and it works for testers who already have access to that release.
  • In-app feedback. Testers can send feedback with screenshots from inside the app. Google's feedback guide covers Android only, and says the SDK is in beta and "may receive limited or no support". It needs the App Distribution SDK in your app.

What it costs

Google's Firebase pricing page lists App Distribution as "No-cost". I found no other fees or usage limits on that page. Apple and Google developer accounts are separate and have their own terms.

Does it count for Google's 12 testers rule?

If you have a new personal Google Play developer account, you've probably heard about the 12 testers for 14 days rule. I read Google's testing requirements page on 10 November 2026. It says: "At least 12 testers must be opted in to your closed test when you apply for production access", and "they must have been opted in continuously for the preceding 14 days".

The page doesn't mention Firebase. So I won't tell you what Google would or wouldn't accept. Google's requirement is about testers opted in to your closed test on Play. Testers in Firebase App Distribution are outside Play. If the rule applies to you, the opt-in has to happen on Play. The 12 testers for 14 days post explains the rule in full.

Which one to use when

  • Firebase App Distribution. Quick builds to a few known people, on Android or iOS, with no store involved. Good for early, rough versions and CI builds.
  • Play internal testing. Google describes it as optional, for a small group of trusted testers. It is a Play track, so the build lives in Play.
  • Play closed testing. The track that matters for the 12-tester rule on a new personal account. Use it when you're heading to production access.
  • TestFlight. A common route on iOS. See my TestFlight post above for how outside testers join.

The Play tracks are explained in internal, closed and open testing. You can use more than one. A common pattern is Firebase for early builds and Play closed testing later.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. Sign-in is with X, and new accounts start with 3 credits.

When you post an app, you link to wherever testers can open or install it. That can be your site, a TestFlight link or a Google Play testing link. A Firebase App Distribution invite link is another place a tester could install from, if you put it in your test task and ask for it plainly. Keep in mind the iOS device step above: a tester on iPhone can't just tap and install an ad hoc build. And a TestSwap review is a text form on TestSwap. It does not opt anyone in to a Play closed test. Here's how to write a test task.

Checklist

  1. Decide the goal: quick feedback now, or Play production access later.
  2. Add Firebase to your app and open App Distribution in the console.
  3. Upload the build and write short release notes.
  4. Add testers or a group, or create an invite link.
  5. On iOS, expect to collect UDIDs, update the profile and rebuild for new devices.
  6. Tell testers to accept within 30 days and what to try first.
  7. Note the 150 day build lifetime and redistribute before it runs out.
  8. If you need the Play 12-tester rule, run a closed test on Play as well.

Try it

If you want fresh eyes on a build, post your app on TestSwap with a test task that says exactly how to install it and what to do. You get 3 credits to start, and reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).