Short answer: start the Google Play closed test as early as possible, because new personal accounts need at least 12 testers opted in for 14 continuous days and then a production access review. Run a TestFlight beta in parallel for iOS. Use week one for setup and stability, week two for real-world use and fixes, and week three for applications, reviews and launch preparation.

Before week 1: setup

Complete Play Console app setup so the closed track is available, and add TestFlight test information, a beta app description and beta app review information in App Store Connect. Recruit testers for both platforms at once, with a buffer for Android.

Week 1: stability

Android

Roll out to the closed track, share the opt-in link, log opt-in dates and run Play's pre-launch report.

iOS

Test with internal testers, then add a stable build to an external group for beta review and invite testers.

Both

Send the tester brief with daily tasks. Fix crashes first.

Week 2: real-world use

Ask testers to use the app normally: on mobile data, with low battery, in their own language. Collect feedback through Play's testing feedback, TestFlight screenshots and your own form. Ship at least one update on each platform and tell testers what changed.

Week 3: apply and prepare

Android

Once 12 or more testers have been opted in for 14 continuous days, apply for production access with specific answers. Google says review usually takes seven days or less. Keep the closed test running.

iOS

Select your tested build and submit it for App Store review.

Both

Prepare store listings, screenshots and support pages.

Launch-day checks

Install the production build from each store on a clean device. Confirm sign-up, payments if any, and your support contact. Keep a closed track and a TestFlight group for future updates; Google recommends continuing closed tests to reduce low ratings when you release changes.

Getting help

If you're short of testers, TestLancer can run a 14-day Google Play closed test and an iOS round with your TestFlight build. It doesn't sell reviews and can't guarantee approval on either store.

The official rules, in one place

According to Google's Play Console Help article on app testing requirements for new personal developer accounts:

  • The rule applies to personal developer accounts created after November 13, 2023.
  • You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
  • Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
  • The application has three parts: About your closed test, About your app/game and About your production readiness.
  • Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
  • Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.

Quick checklist before you apply for production access

  • [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
  • [ ] A buffer of extra testers in case someone drops out at the last minute.
  • [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
  • [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
  • [ ] A list of changes you made because of the test, with version numbers.
  • [ ] Working test credentials in Play Console if your app needs a login.
  • [ ] Content rating, target audience and data safety answers that match the real app.
  • [ ] No crashes or empty screens on the build you're about to ship.

If any box is empty, a few more days of testing usually costs less than another review cycle.

Mistakes that cost developers extra weeks

  1. Recruiting exactly 12. One opt-out and you're back to waiting.
  2. Running the test on the internal track. Internal days don't count toward the requirement.
  3. Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
  4. Tidying the tester list mid-test. Removing someone ends their streak.
  5. Shipping no updates. The production readiness section asks what you changed because of testing.
  6. Using friends who never open the app. Google can ask for more testing when engagement is low.
  7. Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.

FAQ

Can I launch iOS before Android?

Yes. Apple doesn't require a minimum test period, so iOS can go live while the Play closed test continues.

What if Google asks for more testing?

Keep testing with engaged testers and reapply. That's why the closed test should keep running while you wait.

Is three weeks always enough?

It's a realistic minimum for a small app. Google's review can occasionally take longer.

Next step

If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.