Recruit 15 to 20 beta testers who match your customer, from interviews, your waitlist and one or two communities. On Google Play, new personal developer accounts must run a closed test with at least 12 testers opted in for 14 days before going live, so start recruiting before the build is ready.

This is for founders preparing a first release on Android, iPhone or the web. The running example is ShiftSwap, an imagined app that lets café staff swap shifts. Store rules are as of October 2026.

In short:

  • Testers who fit the customer give useful feedback. Friends give praise.
  • Recruit a few more than 12, because some testers drop out.
  • TestFlight allows up to 10,000 external testers on iPhone.
  • Ask testers to do one task, then ask what almost stopped them.

Google Play's rule sets the minimum

Google's page on testing requirements for new personal developer accounts is clear. Personal accounts created after November 13, 2023 must run a closed test with at least 12 testers. Those testers must stay opted in continuously for the 14 days before you apply for production access.

So recruit 15 to 20. If three people opt out in week one, you're still at or above 12. Google's guide to setting up open, closed or internal tests explains the three testing tracks. Our guide to publishing an app to Google Play covers the steps after the test.

TestFlight covers iPhone testers

On iPhone, Apple's TestFlight handles beta builds. You can add up to 100 internal testers from your team and invite up to 10,000 external testers. External testing needs a beta app description and beta review information first.

On the web, testing is simpler: share a link. That makes a web version a good first test, even if the store versions follow later.

Recruit from people who fit the customer

The best testers have the problem today. For ShiftSwap, that's staff and managers at cafés who swap shifts by group chat, not developers who like new apps.

Recruit from these sources, in this order:

  1. Invite everyone you interviewed. They know the problem and want to see what you built.
  2. Email your waitlist, starting with people who answered a question when they signed up.
  3. Ask each early tester to bring one colleague, which works well for team apps like ShiftSwap.
  4. Post in one or two communities where your customer gathers, following their rules.

Write a short screening question into the sign-up form, such as "How do you swap shifts today?" Anyone who says "we don't" isn't your tester yet.

Give testers one task, not a tour

Testers who are told "have a look around" tap three screens and leave. A single, real task gets real feedback.

For ShiftSwap, the task is: "Offer next Saturday's shift and see who takes it." Send it with the install link, and say how long it should take, such as ten minutes.

Then ask three questions after the task:

  • What were you trying to do, and did it work?
  • What almost stopped you?
  • What would make you use this next week?

The second question gets the most useful answers. Ask it in a short form or a two-minute call.

Keep testers engaged for 14 days

A two-week closed test needs testers to stay. Three habits help:

  • Send one short update each week, with what you fixed from their feedback.
  • Name the change and thank the person who spotted it, with their permission.
  • Ask for one new task in week two, such as swapping a shift back.

People stay when they see their feedback matter. A tester who reported a bug on Monday and sees it fixed on Thursday becomes your best supporter.

Sort feedback by how often it blocks the task

Feedback piles up fast. Sort it into three groups:

Group Example from ShiftSwap Action
Blocks the task Can't find "offer shift" Fix this week
Slows the task Too many taps to confirm Fix before launch
Nice to have Dark mode Add to the list

Fix anything that blocks two or more testers first. One person's wish list can wait.

AI assistants help with the sorting. Paste all answers and ask for groups with counts and quotes, without adding new ones. Check the counts against the answers.

Test GrowApps builds on your own phone first

GrowApps lets you see your app on your phone while you build it: scan the code, open it in your phone's browser, and install a test version on Android (test on your phone). For Google Play, it helps you build the signed app file that you upload to your closed test in your own Play Console. Run your own task on your phone before you invite the first tester.

Write your tester invite now

Write a three-line invite: who it's for, the one task, and how long it takes. Send it to the first three people you interviewed. Then follow the launch checklist for your first 100 users once the test ends.

Frequently asked questions

Should I pay beta testers?

Usually not for a first test. People with the problem want a better tool. For hard-to-reach professionals, a small gift, such as a free year of the paid plan, is a fair thank-you.

Do the 12 testers have to use the app every day?

Google's rule is about testers being opted in to the closed test continuously for 14 days. Real use matters for your feedback anyway, so give testers a reason to open the app more than once.

Sources and further reading