TestFlight for Android: it doesn't exist, here's what to use

TestFlight is Apple-only. The Android equivalents are Google Play internal, closed and open testing, internal app sharing, and Firebase App Distribution.

Storewatch blog cover: TestFlight for Android: it doesn't exist, here's what to use

There is no TestFlight for Android. TestFlight is Apple's beta tool and runs on Apple platforms: Apple's overview lists iOS, macOS, visionOS, tvOS and watchOS. To beta test an Android app, use Google Play's testing tracks, internal app sharing, or Firebase App Distribution.

Here is how each Android option works and how they compare with TestFlight, plus what to do if you ship on both. Facts are from Google's Play Console help and Firebase docs, as of November 2026.

The Android options

Google Play internal testing

Per Google's help, an internal test can have up to 100 testers per app, who you add by email. It's the fastest to distribute: Google says internal test bundles reach testers within minutes. Testers can also install paid apps for free. Google notes internal tests might not be subject to standard Play policy or security reviews.

Closed testing

Testers join through email lists or Google Groups. Email lists hold up to 2,000 testers each (200 lists per account, 50 per track). Google Groups have no size limit. Testers opt in using a link, and the link only shows when the app's status is "Published".

Open testing

Anyone who finds your test on Google Play, or uses a shared link, can join. It's unlimited by default, or you can set a limit of at least 1,000.

Internal app sharing

You upload a bundle or APK and get a link. Google's internal app sharing page says version codes don't need to be unique, and debuggable builds are allowed. Links expire after 60 days and only 100 users can download through each link. Testers must turn the feature on in the Play Store first.

Firebase App Distribution

Firebase App Distribution is Google's service for sending pre-release builds outside the Play Store. It supports Android and iOS from one place, with tester groups, email invitations and optional in-app feedback. A Firebase project allows up to 500 testers, and a group up to 200, with higher limits available on request, per the tester docs.

TestFlight vs Play testing

TestFlightPlay internalPlay closedPlay open
Testers100 internal, 10,000 external1002,000 per email list; no limit for Google GroupsUnlimited, or a limit of 1,000+
ReviewBeta App Review for the first external buildMay skip standard reviewNot statedNot stated
How they joinEmail invite or public link, via the TestFlight appEmail listOpt-in link, lists or GroupsPlay Store listing or link

Google's help page doesn't say whether closed or open tests get a Play review before going out, or how long it takes, so I've marked those "not stated". Check Play Console for your own app.

One Google rule to know first

If your Play developer account is a personal account created after November 13, 2023, Google requires a closed test before you can apply for production access. Per Google's testing requirements, you need at least 12 testers opted in, continuously for 14 days. Google says review of the production application usually takes seven days or less. TestFlight has no equivalent rule.

If you ship on both

  • Keep the structure the same. An internal group for your team and an external group for outside testers maps well onto Play's internal and closed tracks.
  • Use one build label. A shared version number and a build number from your CI keeps feedback easy to match across platforms.
  • Expect different rules. TestFlight builds last 90 days from upload. Check Play and Firebase limits separately, since they work differently (Play internal app sharing links last 60 days).
  • Collect feedback in one place. TestFlight feedback lives in App Store Connect (see TestFlight feedback). Play testers can't leave public reviews on test versions, so Google suggests giving them a direct feedback channel.
  • Firebase for both. If you want one tool for both platforms, App Distribution handles iOS and Android, though the iOS side doesn't replace the TestFlight app and its review flow for App Store builds.

For the Apple side, see inviting TestFlight testers and TestFlight previous builds. Storewatch covers the Apple side of your release (Build uploaded, TestFlight, In review, Approved, Live) and shows AdMob earnings for iOS and Android together, but it doesn't track Android beta testing.

Frequently asked questions

Is there a TestFlight app for Android?

No. TestFlight is Apple's and runs on Apple devices. On Android, testers join Google Play tests or install through Firebase App Distribution.

What is the Android equivalent of TestFlight?

Google Play internal, closed and open testing are the closest, since testers install through Google Play. Firebase App Distribution is the main option outside the Play Store.

How many testers can an Android beta have?

Internal tests allow 100. Closed tests allow 2,000 per email list, with no size limit for Google Groups. Open tests are unlimited unless you set a limit of 1,000 or more.

Can I run iOS betas through Firebase instead of TestFlight?

Firebase App Distribution supports iOS builds, but TestFlight is Apple's own route for App Store builds, with its tester and review features.

Is internal app sharing the same as internal testing?

No. Internal app sharing is link-based: shared files can't be used in testing or production releases and links expire after 60 days. Internal testing is a Play track.