AppReviewX Log in

Google Play closed test for an app built with AI

Why the 12-tester rule does not depend on how the app was built, and how to use the 14 days to get feedback you can act on.

In this guide

Short answer: Google Play's closed-test requirement is about your developer account, not about how you built the app. Written by hand or built mostly by prompting, the same step applies.

What the requirement says

Play Console Help states that a closed test with "a minimum of 12 testers who have been opted in continuously for at least 14 days" is needed, and that you apply for production access once the criteria are met. Source: Play Console Help, retrieved 2026-10-20.

The page ties this to certain new personal developer accounts. Whether it applies to you depends on your account type and creation date, so read the current page before you plan. Details: Google Play closed test requirements and what counts as 14 days. Policies change.

Why it is worth taking seriously as a builder

The 14 days are an unusually good window. You have a build in real hands and time to fix things before the public sees it. If you built mostly by prompting, outside testers are the quickest way to see what you did not think to try.

How to use the 14 days

  1. Ship a build you would be fine with others using. Run the pre-launch checks first: test a vibe-coded app before launch.
  2. Recruit more than 12. People drop out. Count only testers who stay opted in, and see what counts as 14 days.
  3. Tell testers what to try. Three or four concrete tasks beat "have a look".
  4. Ask for structured reports (device, steps, expected, actual): bugs testers find in AI-built apps.
  5. Fix in small updates and say so, so testers can retest.
  6. Write down what changed. You may need it for the production-access application: production access application.

More on the process: Google Play closed testing: 12 testers.

About reviews

A closed test is testing, not rating. Do not ask testers for store reviews in return for anything, and do not swap reviews with other developers. Ratings should come later from a good product and an honest ask. See buy app reviews: risks and what to do instead.

How AppReviewX helps

AppReviewX has test groups for the Google Play requirement: 12 testers, 14 days in a row, for Android apps. Feedback is private and structured; one feedback you write earns 1 credit, and new accounts start at 0. No promise about rankings or installs. Start free.

Related: Vibe coding hub, standing out among many new apps, first honest reviews.