Topics: Custom software & SaaS, Mobile apps
Want this done for your business? Get a fixed quote or book a free 30-minute call.
Quick answer: Use TestFlight to beta test on iPhone and Google Play's internal, closed or open tracks on Android. If your Play developer account is a personal one created after 13 November 2023, Google requires a closed test with at least 12 opted-in testers for 14 continuous days before you can apply for production; organisation accounts are exempt. Use the beta to check crashes, onboarding and the tasks that make you money.
Plenty of launch plans assume the app is finished when development ends and Apple approves it. Then the Android side stalls, because Google Play will not grant production access to a new personal account until a closed test has run for a fortnight with enough real testers. A beta is worth running anyway. Plan it as a stage with its own dates, owner and exit criteria rather than discovering it in launch week.
Why run a beta before you launch an app?
Because real people on real phones find problems your team cannot. Internal QA testing checks that features work as specified. A beta checks that strangers understand them, on devices, networks and settings nobody in the office uses.
A good beta tells you:
- Where people get stuck during sign-up and onboarding
- Which crashes happen on older or budget phones
- Whether payments, notifications and permissions behave outside test conditions
- What the store reviewers are likely to hit, before they do
- Which features people ignore, which is useful before you spend more on them
It also gives you your first advocates. Testers who saw their feedback acted on often become the first reviewers once you go live.
How does TestFlight work for internal and external testers?
TestFlight, Apple's beta service, has two kinds of testers with different limits and rules.
| Internal testers | External testers | |
|---|---|---|
| Who | Members of your App Store Connect team | Anyone you invite by email or public link |
| Limit | Up to 100 | Up to 10,000 |
| Review | No beta review | The first build of a version goes through Beta App Review |
| Speed | Available once the build has processed | Available after approval, usually quick |
A public link is the easiest way to reach a wider group, and you can cap how many people may join through it, so a link shared beyond your intended group cannot flood the beta. Every TestFlight build expires 90 days after upload, so long betas need fresh builds. Testers install the free TestFlight app, and can send feedback with screenshots and crash reports from inside it. Add short "what to test" notes with each build; testers follow instructions far better than they explore.
What are Google Play's internal, closed and open testing tracks?
Google Play gives you three testing tracks, each suited to a different stage.
| Track | Who can join | Discoverable on Play? | Use it for |
|---|---|---|---|
| Internal testing | Up to 100 testers you list | No | Quick builds for your own team |
| Closed testing | Testers you invite by email list or Google Group | No | The main beta, and the required test for new personal accounts |
| Open testing | Anyone, from your store listing | Yes | Larger public betas before full launch |
Testers on these tracks send private feedback rather than public reviews, so a rough early build will not damage your rating.
What is the 12-tester, 14-day rule, and who does it apply to?
Per Google's Play Console Help, developers with personal accounts created after 13 November 2023 must run a closed test with at least 12 testers who have been opted in for the last 14 days continuously before applying for production access. The threshold was 20 testers when the rule began; Google later lowered it to 12.
When you apply, Google asks about the test: how you recruited testers, what feedback you received and what changed. It can refuse production access if engagement looks thin, and you would then run the test again.
Organisation accounts are not subject to this requirement, which is one of several reasons a business should publish under its own company account. Our guide to setting up Apple and Google developer accounts explains the D-U-N-S number and enrolment steps.
If the rule does apply to you, a sensible timeline:
- Days 1–3: publish a stable build to closed testing and recruit 15–20 testers, so a few dropouts do not take you under 12.
- Days 1–14: send tasks, collect feedback and ship fixes to the same track. Testers stay opted in across updates.
- Day 15 onwards: apply for production access, then allow time for Google to review the application before your launch date.
How do you recruit testers and collect useful feedback?
Recruit people who match your customers, give them specific jobs and keep feedback in one place.
- Who: existing customers, staff at client sites, members of a loyal customer WhatsApp group, or people from your target audience. Friends and family are polite, not useful.
- A spread of devices. Ask each tester which phone and OS version they use, and make sure the group includes older iPhones and budget Android phones, not just the latest models.
- A spread of settings. Include someone who uses large text, dark mode or a regional language on their phone; these settings expose layout problems quickly.
- Avoid paid tester services. Google looks at real engagement, and a list of strangers opening the app once will not satisfy the review or tell you anything.
- Give tasks, not a vague invitation. "Book an appointment for next Tuesday, then reschedule it" produces better feedback than "have a look around".
- Use one channel. TestFlight feedback and Play's private feedback, plus a short form for both platforms. Feedback scattered across chats and emails gets lost.
- Close the loop. Release notes that say "fixed the crash you reported" keep testers engaged through the 14 days.
Testers who feel heard often become early reviewers and referrers, which feeds straight into your first 1,000 app downloads.
What should you measure before moving to production?
Agree the exit criteria before the beta starts, so launch is a decision rather than a mood.
| Measure | Why it matters | How to read it |
|---|---|---|
| Crash-free users and sessions | Crashes drive uninstalls and one-star reviews | Check TestFlight, Play Console's Android vitals and your crash tool |
| Onboarding completion | Shows whether people reach the point of value | Track each step; fix the biggest drop first |
| Key task success | Bookings, orders or payments completed | Run them end to end with real accounts |
| Performance on budget phones | Many users do not own flagships | Startup time and smoothness on your oldest supported device |
| Open feedback themes | Recurring confusion signals design problems | Resolve or consciously defer each theme |
Set your own targets for each line. If crash rates or task success miss them, run another round rather than launching on the original date. Build two to four weeks of beta into realistic app timelines from the start, so it never feels like a delay. When the numbers pass, move on to the App Store and Google Play submission checklist.
Frequently asked questions
How many testers do I need for Google Play?
If your personal developer account was created after 13 November 2023, you need at least 12 testers opted in to a closed test for 14 continuous days before applying for production. Recruit a few extra in case some drop out. Organisation accounts have no minimum, though a meaningful beta still needs real users.
Does the 12-tester rule apply to company accounts?
No. Google applies it to new personal accounts only. Organisation accounts require a D-U-N-S number and business verification instead, which takes time to set up but avoids the closed-testing requirement.
How long does a TestFlight build last?
Each build is available for 90 days from upload. After that it expires and testers can no longer open it, so upload a new build if your beta runs longer.
Can beta testers find my app on the store?
Not for TestFlight or Google Play's internal and closed tracks; testers need an invitation or link. An open test on Google Play is visible from your store listing, and anyone can join it.
How long should an app beta run?
Two to four weeks suits most small business apps, enough for two or three rounds of fixes. On Google Play the closed test must run at least 14 days if the personal-account rule applies to you. Complex apps, or apps with payments and bookings, deserve longer.
Plan a launch without the surprise
We build and launch apps for businesses in India, Australia, the UK and the USA, with the beta planned into the schedule from day one. See our approach to app development and launch, or book a free call to map out your timeline.