TestFlight External Testing Before Launch
External TestFlight is how people who are not on your App Store Connect team install a recipe app before it is public. The first build still goes through Beta App Review.
Quick answer
How does TestFlight external testing work before launch?
External TestFlight lets you invite up to 10,000 people who are not on your App Store Connect team. You need a beta app description, beta review information, and an email for feedback. The first build is sent to Beta App Review when you add it to an external group. Internal testing is a separate cap of 100 team members. Cooks join by email or a public link.
On this page
Sunday Sauce is a recipe app you do not want strangers meeting for the first time on the App Store. The shopping list drops an ingredient. The timer does not survive a phone call. External TestFlight is the way cooks who are not on your developer team install a build, follow one recipe, and send you the screen where it broke. It is still a beta. It is not the public product page, and it is not a quiet launch in one country.
Apple’s TestFlight overview is the source for the numbers below. The rest of getting the listing ready is the launch checklist. If you meant “live, but only in two storefronts,” that is a soft launch, which uses Availability after review, not a beta group.
External means not your App Store Connect team
Internal testers are members of the team who hold Account Holder, Admin, App Manager, Developer, or Marketing. Apple’s cap there is 100 people. You can auto-distribute new builds to them. They do not need the same Beta App Review step. External testers are everyone else: the cooks on your mailing list, a cooking club, a public link in a newsletter. The cap is 10,000 external testers. You can share up to 100 builds, and you can test more than one build at a time.
Before an external group can install, you provide test information: what you want people to try, plus an email address so you can read feedback. The beta app description and beta app review information are required to share the beta with external testers. Testers install through the TestFlight app. They can use the builds you shared on up to 30 devices. You do not collect UDIDs.
The first external build goes to review
Create a group, add the build, and App Store Connect sends that build for TestFlight review. Apple says your builds are automatically sent for review once they are added to a group, and that the first build has to be approved for external testing. Do not promise Sunday Sauce’s newsletter a link the same hour you upload if review has not finished. Internal testers can be on a newer build while you wait. Do not treat that as proof the external group is unblocked.
What you ask them to test should be one dinner, not “try everything.” The beta description is the note in the invite. If an approved App Store version already exists, the invite can also include screenshots and the app category. For a first launch, you will not have that approved version yet. Write the beta description as if the cook has never seen the app: which recipe, what “done” means, and where to send a broken step.
Email invites and public links
| Invite | When it fits | Watch-out |
|---|---|---|
| You know the cooks and their addresses. | A list of strangers you scraped is not a test plan. You still need the feedback email on the beta. | |
| Public link | A newsletter, a club, or a post, without collecting addresses first. | You can require device type and OS version. Disable the link when you hit the tester cap. |
| Internal group | You and the people with App Store Connect roles. | Capped at 100. It does not replace the external review or the 10,000-person group. |
External testers join by email or by a public link, after the build is approved for TestFlight. Internal testers are a separate cap of 100 team members.
What to ask a cook to do
Pick one recipe that uses the shopping list, the steps, and the timer. Ask the tester to start from a fresh install, add the ingredients they actually have, and stop when the dish is done or when they are stuck. TestFlight lets them mark up a screenshot. If the app crashes, you get a crash report, and they can add context. Filter that feedback by OS version before you decide the timer is “fine on your phone.”
Groups exist so you can point one cohort at a build. A small group that owns a specific oven timer bug is more useful than 10,000 installs of a build you already know drops the last step. Grow the public link after the first cooks finish a recipe. Apple shows how many people viewed a public link, how many installed, and how many failed the criteria you set. If you are full, turn the link off so the next person sees that the beta is closed.
What external testing does not do
It does not publish the product page. People with the invite see the beta, not your subtitle in search. It does not set Availability, so it is not a soft launch. It does not phase the App Store release. When you are done, builds you already uploaded can be selected for the App Store submission. You still submit that build for App Review. Beta approval is not App Store approval.
Play’s version of a private tester list is closed testing, including the 12-tester rule on new personal accounts. That is a different console. Read the closed testing guide before you assume a TestFlight group satisfies Play. Screenshots for the store should be captured from the build you will submit, after the recipe flow survives testers. AppGrowthKit can frame those screens. It does not invite testers.
Leave the beta with a build you would ship
Stop when a cook who is not you can finish the chosen recipe without a message from you. Read the crash list. Fix the shopping-list drop. Then select that build for App Store review. The public page, the support URL, and the privacy details are still required. TestFlight did not file them. The launch checklist is the pass you do after the beta, not instead of it.
If you want the App Store release itself to roll out gradually after approval, that is a phased release, not another TestFlight group. Keep the beta link disabled once you are on the store, unless you are deliberately testing the next version. A public link that still installs last month’s broken timer will confuse the same cooks you just asked to trust the launch.
Run an external test of Sunday Sauce
One recipe, one external group, Beta App Review before the link goes wide. Internal testers can chew on the build while you wait.
Write the beta description around one recipe
Name the dish, the steps you care about, and the email where feedback should land. That description and the beta review information are required before external testers can be invited. Do not write “test the whole app.” A cook with a weeknight will follow one path. Put the contact email in the test information so you actually see what they send.
Upload the build and add an external group
Upload to App Store Connect. You can keep up to 100 builds. Create the external group and add this build. Adding it sends the build to TestFlight review. The first external build has to be approved before that group can install. Use an internal group of team members, up to 100 people in the roles Apple lists, if you need a faster loop on the same upload.
Invite a small set before the public link
Email a handful of cooks you can talk to. They install with the TestFlight app and can keep the builds you shared on up to 30 devices. Ask them to complete the one recipe and mark up the screen where the list or the timer fails. Read crashes by OS version. Do not open a public link until that first dinner works.
Open a public link with criteria
When the recipe survives the small group, create a public link and, if you need it, limit who can join by device type and OS version. Put the link in the newsletter. Watch views, installs, and people who did not meet the criteria. If you reach the 10,000 external tester cap, disable the link so new visitors are not staring at a dead invite.
Ship the build that finished the recipe
Fix the blockers, upload the next build if you must, and get external approval again if that is what the group requires. Then select the build for App Store review. Turn the wide link off when the public app is the one you want people to install. TestFlight feedback is not an App Store review. Ask for stars later, from people who cooked in the released app, and only within the rules for requesting reviews.
Key takeaways
- External TestFlight is up to 10,000 testers outside your App Store Connect roles. Internal is up to 100.
- Beta description, beta review information, and a feedback email are required for external testing.
- The first build added to an external group goes to TestFlight review before those testers can install.
- Invite by email or a public link. A public link can filter on device type and OS version.
- Testers install with the TestFlight app and can use shared builds on up to 30 devices. This is not a soft launch.
Frequently asked questions
Do external testers need to be on my developer team?
No. That is the point of an external group. Internal testers are the people who already have Account Holder, Admin, App Manager, Developer, or Marketing, and that list stops at 100. External testers are invited by email or a public link, up to 10,000. They use the TestFlight app. You still give Apple a beta description, beta review information, and an email for feedback before you can share the build with them. They do not need a seat in App Store Connect.
Why is my public link not installing yet?
The first build you add to an external group is sent for TestFlight review, and it has to be approved before external testers can install. Uploading the build is not that approval. Internal testers in the allowed roles can often try a build sooner. Check that the group actually contains the build, that review has finished, and that the tester meets any device or OS criteria on the public link. If you disabled the link because you hit the cap, the install will not start until you turn it back on or free a seat.
Can I use TestFlight instead of a soft launch?
No. Soft launch means the app is on the App Store with Availability limited to a few storefronts, so you can watch crashes and the real acquisition funnel, then add countries. TestFlight never puts Sunday Sauce in search. It also does not count as App Store conversion. Use the beta to finish one recipe. Use Availability later if you want a small public footprint. Phased release is a third switch, after the app is approved, and it is not a tester group either.
How many builds and devices are involved?
Apple’s TestFlight page says you can share up to 100 builds and test more than one at a time. Testers can access the builds you shared with them on up to 30 devices. Those are the figures on the overview. Do not plan around a device-registration spreadsheet. TestFlight does not ask you for UDIDs. When a build is bad, stop testing it and point the group at the fixed one instead of leaving both dinners in the invite without a note.
Should I ask beta cooks for App Store reviews?
No. They are not on the public listing yet, and a beta invite is the wrong place to beg for stars. Ask which step failed and read the screenshot they mark up. After the app is live, a review request is its own decision, with Apple’s limits on how often the system sheet can appear. The launch checklist covers the listing. TestFlight covers the recipe. Mixing them produces ratings from people who never cooked the version on the store.
Keep reading
How to Soft Launch an iOS App
A soft launch limits App Store Availability to a few storefronts so you can watch crashes and the real install funnel, then add countries. It does not game search.
App Store Phased Release, Day by Day
Seven days, fixed percents, pause up to 30 days total. Not for a first release. The automatic-update binary is staged. Treat the listing copy as live, and watch crashes before day 5.
App Store Launch Checklist: From Screenshots to First Users
A practical launch plan for indie app developers: get your listing compliant, make screenshots convert, recruit useful early feedback, then improve with evidence instead of post-launch guesswork.
Google Play Closed Testing Before Production
A new personal Play account cannot ship a habit app to production until a closed test has at least 12 testers opted in for 14 days straight. An opt-out resets that tester.
How to Ask for an App Store Review
Call the system prompt after a finished job, not on launch. A receipt scanner’s third successful scan is the moment. The pre-question gate is the risk.
Free tools that help here
App Icon Generator
Drop in one 1024px icon and download every iOS and Android size, ready for Xcode and Android Studio. Runs entirely in your browser - nothing gets uploaded.
ASO Character Counter
Count characters for every App Store and Google Play metadata field against exact store limits. Live counts and over-limit warnings - nothing gets truncated at submission.
Screenshot Beautifier
Add polished backgrounds, padding, shadows, and rounded corners to any screenshot in seconds. Perfect for social posts, docs, and portfolios.
Test the recipes, then show the real ones
AppGrowthKit builds the store screenshots from the recipe screens testers actually used, so launch day is not a different app.
Try AppGrowthKit for Free