Beta testing your app with TestFlight and Google Play tracks

Short answer: On iPhone, use TestFlight: up to 100 internal testers from your team get builds right away, and up to 10,000 external testers can join once your first build passes a beta review; each build can be tested for 90 days. On Android, use Google Play's testing tracks: internal testing for up to 100 people within minutes, closed testing for invited groups, and open testing that anyone can join from Google Play. Start small and internal on both, fix the obvious problems, then widen.

Beta testing is where you find out that the sign-up email lands in spam, the booking button hides behind the keyboard on small phones, or that customers don't understand step two. It's far cheaper than finding out from one-star reviews.

The two platforms side by side

All figures above are from Apple's TestFlight pages and Google's Play Console Help, as of November 2026.

Apple: TestFlight, step by step

1. Prepare test information. In App Store Connect, add a beta app description and the email address that receives tester feedback. Apple says the beta description and beta app review information are required before sharing with external testers.
2. Upload a build from Xcode or your build pipeline. Apple notes you can share up to 100 builds and test several at once.
3. Add internal testers. Apple allows up to 100 members of your team with the Account Holder, Admin, App Manager, Developer or Marketing role. You can have new builds delivered to internal testers automatically.
4. Create external groups. Make a group (for example "Customers – pilot"), add the build. The first build must be approved for TestFlight by App Review; builds are sent for review automatically when added to a group.
5. Invite people by email, or with a public link you can share in an email or social post, which helps when you don't have testers' addresses.
6. Collect feedback. On recent iOS versions, testers send screenshots and comments from inside the beta; you see them in the TestFlight Feedback section in App Store Connect.
7. Stop or move on. You can expire a build when testing is done. Apple notes that if you don't, invited testers can still test that build after it goes live, and that builds become unavailable to testers after 90 days.

Google Play: testing tracks, step by step

1. Start with internal testing. Google recommends it as the first step. Create an email list of up to 100 testers. Google says a new app bundle on the internal track reaches testers within minutes, and that internal tests might not go through standard policy or security reviews.
2. Share the opt-in link. Testers accept the invitation via the link from Play Console, then install from Google Play like a normal app.
3. Move to closed testing. Create a closed testing release for a wider, invited group. Google's help allows up to 200 email lists of up to 2,000 users each, and up to 50 lists per track; you can also create extra named closed tracks, for example one for staff and one for customers.
4. Open testing (optional). Your test version becomes visible on Google Play and anyone can join and send private feedback. Make sure the store listing is ready before you choose it.
5. Promote to production when the test version is stable.

One rule to know: Google's help states that developers with personal Play accounts created after November 13, 2023 must meet specific testing requirements before publishing. Check Google's app testing requirements page for the current details if that applies to you.

Running a useful beta

The tooling is the easy part. What makes a beta worth doing:

Pick the right testers

• 5–10 staff or friends for the first internal round
• then 20–50 real customers who match your audience, including someone on an older phone and someone who isn't tech-savvy

Give them tasks, not just an invite

"Book a haircut for next Tuesday and cancel it." "Order two items and use the promo code." Testers who are told what to try find more real problems than those told to "have a look".

Make feedback easy

TestFlight's built-in feedback is good on iPhone. For Android, add a short form link in the welcome message or inside the app's settings for beta builds.

Watch the numbers too

Crash reports and basic analytics from beta builds show problems testers don't mention. Make sure your analytics and crash reporting are switched on before inviting anyone.

Version your builds clearly

Put the version and build number on a settings screen so testers can tell you exactly which build they're reporting on.

FAQ

Do testers need to pay or have a developer account?

No. iPhone testers install the free TestFlight app; Android testers accept the invite and install from Google Play.

How long does TestFlight beta review take?

It varies. Only the first build for external testers needs approval; later builds may also be reviewed when added to groups. Plan a day or two of buffer before an external test.

Can I test in-app purchases in a beta?

Yes on both platforms, without real charges in normal test setups. Apple's App Store Connect help has a section on testing subscriptions and in-app purchases in TestFlight.

Should I use open testing at all?

Only if you want public feedback and your listing is ready for strangers to see. Many small businesses get what they need from internal and closed tests.

If you'd like a test plan that turns your beta testers into useful bug reports, tell us where your app is in development.

Sources

• https://developer.apple.com/testflight/
• https://developer.apple.com/help/app-store-connect/test-a-beta-version/testflight-overview
• https://support.google.com/googleplay/android-developer/answer/9845334?hl=en