TestFlight on Android?
It doesn’t exist.
If you searched for testflight on android, here is the honest answer first: it is not real. TestFlight is Apple’s own beta-testing app, built only for Apple’s own platforms, and Apple has never shipped a version for Android. What you actually want is Google Play’s testing system, which does the same job for an Android app.
If your Play developer account is new, you will also run into a specific rule there: Google Play closed testing requires at least 12 opted-in testers for 14 consecutive days before you can apply for production access. That process, and the two other tracks that make up Android’s answer to TestFlight, is what this guide walks through.
The short answer
There is no TestFlight for Android, and there never has been. TestFlight only runs on iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. For Android, the real equivalent is built into Google Play Console: an internal testing track for your team, a closed testing track with email lists or an opt-in link, and an open testing track that behaves like a public beta. New personal developer accounts also face a mandatory rule on the closed track: 12 testers, opted in for 14 consecutive days, before production access unlocks.
TestFlight on Android, at a glance.
Android apps that are actually TestFlight, official or otherwise
Where TestFlight runs: iOS, iPadOS, macOS, tvOS, visionOS, watchOS
Android closed-testing minimum, for personal accounts made after Nov 13, 2023
How long those 12 testers must stay opted in, continuously
Side by side
TestFlight vs. Android’s testing tracks.
The two systems solve the same problem in different ways. Here is where they line up and where they genuinely diverge.
| TestFlight (iOS) | Google Play testing (Android) | |
|---|---|---|
| Platforms it runs on | iOS, iPadOS, macOS, tvOS, visionOS, watchOS only | Android only |
| Internal / small-team testers | Up to 100 App Store Connect team members | Up to 100 testers on the internal testing track |
| Wider tester group | Up to 10,000 external testers per app | Up to 2,000 testers per closed testing list, 50 lists per track |
| Review before testers get a build | First build needs Apple's TestFlight review | No review required to start any testing track |
| Shareable link without collecting emails | Public link, capped anywhere from 1 to 10,000 testers | Closed testing opt-in link, or open testing's public Play listing |
| Mandatory minimum to reach production | None. TestFlight testing is optional before release | 12 testers for 14 days, for personal accounts made after Nov 13, 2023 |
Figures from Apple’s TestFlight overview and App Store Connect Help for TestFlight, and Google Play Console Help for Android’s testing tracks.
Why not
Can I run TestFlight on an Android phone?
No, and it is not a settings toggle or a workaround away. TestFlight is not a generic beta-testing tool that happens to favor Apple; it is wired directly into App Store Connect, the system Apple uses to sign and distribute iOS, iPadOS, macOS, tvOS, visionOS, and watchOS builds. An Android build is not signed that way and has nowhere in App Store Connect to live, so there is no version of TestFlight, official or otherwise, that would know what to do with one.
Google built its own equivalent instead, inside Google Play Console, wired into Android’s own signing and distribution system the same way TestFlight is wired into Apple’s. That is Play Console’s internal, closed, and open testing tracks, covered next. If a search result or an app claims to be testflight for android, treat it as unofficial at best, since neither Apple nor Google has ever built one.
TestFlight and Google Play’s testing tracks are not competitors, they are each platform’s own answer to the same need. If you are building for both iOS and Android, you will end up using both systems, never one for the other.
The real equivalent
Google Play’s three testing tracks.
Where TestFlight has one system with internal and external testing groups inside it, Android splits the same idea into three separate tracks. Here is what each one is for.
Internal testing
Add your team as testers by email and a new build is available to them almost as soon as you upload it. There is no tester minimum and no waiting period, so this is the fastest way to get a build onto real devices. It is also the closest match to how you would quietly hand a build to a small group before touching TestFlight-style external testing at all.
Closed testing
Add testers with an email list or an opt-in link and run the test as long as you like. If your Google Play developer account is a personal account created after November 13, 2023, this track is not optional: you need at least 12 testers opted in continuously for 14 days before Google will let you apply for production access. Organization accounts and older personal accounts can skip straight past this requirement, though the track itself is still useful for targeted feedback.
Open testing
Open testing puts a test version of your app on the Play Store itself, so anyone can find it and join, similar in spirit to sharing a wide-open link. Anyone who joins can leave private feedback. If you want to limit how many people can join, Google requires that cap to be at least 1,000 testers, so open testing is built for genuinely public betas, not a small circle.
Requirement details from Google Play Console Help on closed testing and its overview of all three tracks.
The timeline
From build to your first tester.
Same five stops, two very different paths through them.
| TestFlight (iOS) | Google Play testing (Android) | |
|---|---|---|
| 1. Get a build ready | Build signed for App Store Connect | Signed Android App Bundle (.aab) |
| 2. Upload it | Via Xcode, Transporter, or EAS Submit | Upload to a track in Play Console |
| 3. Review before testers see it | First build needs Beta App Review; up to 6 submissions per 24 hours | No review required to start any track |
| 4. Get it to testers | Email invite, or a public link | Email list, or an opt-in link |
| 5. Minimum before going fully public | None required | 12 testers for 14 days, for new personal accounts |
Review and submission limits from App Store Connect Help.
Try it
Which track do you actually need?
Pick what you are trying to do, and this points at the track that matches, the same way choosing internal vs. external testing would on TestFlight.
Choose one of the three options above to see the track that fits.
Try it
How many testers should you actually invite?
The 14-day window counts testers who stay opted in, not everyone who ever joined. Real people drop out, so plan a cushion above the number you need.
Invite about
17 testers
To keep 12 opted in for the full 14 days with a mixed group group, invite a buffer above the number you actually need. This is a planning estimate, not a Google Play guarantee.
Inviting testers
How to invite testers without TestFlight.
On iOS, you invite to TestFlight one of two ways: an email invite, which a tester accepts inside the TestFlight app, or a public link, which skips collecting emails and can be capped anywhere from 1 to 10,000 testers. Android’s closed testing track mirrors both options almost exactly, just without a separate tester app in the middle.
In Play Console, add testers as an email list you paste addresses into, the equivalent of a TestFlight email invite, or generate an opt-in link and share it anywhere, the equivalent of a testflight public link. Either way, a tester just taps through and installs from the Play Store, the same download flow as any other Android app. If you want the widest possible reach, open testing goes a step further than anything TestFlight offers, by listing your beta on the Play Store itself for anyone to discover.
Where the two systems really differ
TestFlight (iOS)
- One iOS build, submitted once for Beta App Review
- Testers install the TestFlight app first, then accept your invite
- A public link with an optional 1 to 10,000 tester cap
- No mandatory tester count before you can submit to the App Store
Google Play testing (Android)
- No separate tester app; testers install straight from Google Play
- Email lists or opt-in links, no review needed to start
- Open testing puts a beta on the Play Store itself, for anyone
- New personal accounts must clear 12 testers for 14 days first
Myth vs. reality
What people get wrong.
Four claims about testflight for android that come up constantly, and what is actually true.
Myth
There is a TestFlight app you can sideload on Android
Reality
No such app exists. Play Console's internal, closed, and open testing tracks are the real system, built into Android from the start.
Myth
You need a Mac to test an Android app before release
Reality
No. Testing an Android app only needs Google Play Console in a browser. TestFlight is the one that needs Apple hardware, not the Android side.
Myth
Beta testing on Android always requires 12 testers
Reality
Only closed testing does, and only for personal accounts created after November 13, 2023. Internal testing has no minimum at all.
Myth
A TestFlight public link and open testing are the same thing
Reality
Open testing goes further: it lists your beta on the Play Store itself for anyone to find. A TestFlight public link is only ever a URL you share.
Step by step
Setting up Android testing, start to finish.
No TestFlight app to install, no separate review to wait on. Here is the whole path, from a signed build to production access.
- 1
Build a signed Android App Bundle
Every Play Console testing track wants the same artifact: a signed .aab file. Without it there is nothing to upload, so this is step zero before any track, email list, or link matters.
- 2
Open Testing in Play Console and pick a track
Internal testing for a quick check with your own team, closed testing for a controlled group and, for new personal accounts, the mandatory pre-production step, or open testing for a genuinely public beta.
- 3
Add testers by email list or opt-in link
Closed testing accepts a pasted email list or a shareable opt-in link, the closest thing Android has to inviting testers to TestFlight without an app-specific tester client.
- 4
Hold the track's requirement, if it has one
Internal and open testing have no fixed window. Closed testing does, for accounts that need it: at least 12 testers have to stay opted in and testing for 14 consecutive days, not just sign up once.
- 5
Apply for production access when it is met
Once your closed test clears the requirement, or if your account was never subject to it, the option to apply for production access, the real public Play Store listing, becomes available in the console.
Where Newly fits
Newly builds the app, you run the testing.
Newly is a paid AI mobile-app builder, from $25 a month. You describe an app in plain language and Newly generates a real React Native and Expo codebase you own, including the signed Android App Bundle that Play Console’s testing tracks are waiting for. Neither TestFlight nor Google Play’s tracks are things Newly replaces, since both are platform review systems, not app-building steps; Newly’s job ends at handing you a build that is ready to go into either one.
Once a build clears testing and reaches production, the next question is usually how to get more app downloads, which is a separate problem from testing but the natural next one once your app is actually live.
Everything above is the Android half. If the same app also has an iOS build waiting — TestFlight itself, the App Store Connect review, the metadata screens — that whole flow lives in publishing to the App Store rather than here.
FAQ
TestFlight on Android, answered.
No. TestFlight is Apple's own beta-testing app, and it only runs on Apple platforms: iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. There is no TestFlight app in the Google Play Store, and Apple has never released one, because TestFlight is built to distribute builds signed for Apple's App Store Connect, which has no Android counterpart. If you are looking for testflight on android, what you actually want is Google Play's own testing system, which does the same job for Android apps.
Skip TestFlight on Android. Build the real app instead.
From $25 a month, Newly turns a description into a real React Native app and the signed Android bundle your testing track is waiting for. You bring the testers, Newly brings the build.