Question 1

What is the Google Play 12 testers requirement?

Accepted Answer

For new personal developer accounts created after November 2023, Google requires you to run a closed test with at least 12 testers who must remain actively opted-in for 14 continuous days before you can apply for production access.

Question 2

Why did Google introduce the 14-day closed testing rule?

Accepted Answer

Google implemented this rule to ensure that apps meet a minimum quality standard, have real users interact with them, and to reduce the number of low-effort, spam, or malicious apps entering the Play Store.

Question 3

Do I need real people for closed testing?

Accepted Answer

Yes, absolutely. Google's automated systems detect emulator usage, bot behavior, and fake accounts. AppBanana uses only real human testers on physical Android devices.

Question 4

Can I use bots or emulators for Android app testing?

Accepted Answer

No. Using bots, click farms, or emulators violates Google Play policies. If detected, it will lead to rejection, account strikes, or permanent account termination. AppBanana strictly avoids bots.

Question 5

How does AppBanana recruit real human testers?

Accepted Answer

We have built a proprietary, opt-in community of real Android users and developers globally who securely test applications on their personal devices.

Question 6

How long does the closed testing phase take?

Accepted Answer

Google requires a minimum of 14 continuous days. However, AppBanana provides testing for up to 21 days to ensure your metrics remain strong while your app sits in the manual review queue.

Question 7

Will my app get approved automatically after 14 days?

Accepted Answer

No. After 14 days, you unlock the ability to answer a comprehensive questionnaire and manually apply for production access. A Google reviewer then decides if your app meets their standards.

Question 8

What happens if Google rejects my app after closed testing?

Accepted Answer

If rejected, we will guide you on what to fix, and then re-test your app completely free of charge. If it still fails due to testing requirements, we offer a 100% refund.

Question 9

Does AppBanana guarantee production access?

Accepted Answer

While nobody can guarantee Google's final subjective decision, we guarantee that you will meet the closed testing requirements flawlessly. We take on the risk—if you don't get approved, you don't pay.

Question 10

How fast can I start closed testing with AppBanana?

Accepted Answer

Once you complete your order and provide your Google Play Console invite link, we typically start onboarding testers within 1 to 2 hours.

Question 11

How much does it cost to get 12 testers?

Accepted Answer

Our standard package is a one-time fee with no hidden costs. It covers 12+ testers, 14-21 days of engagement, crash reporting, and a full refund guarantee. Check our pricing section for current rates.

Question 12

Is the AppBanana service compliant with Google Play policies?

Accepted Answer

Yes. Our testers are real users downloading your app voluntarily. We do not use fake engagement, paid ratings, or bots, ensuring full compliance with Google's terms of service.

Question 13

What if I already have some testers, can AppBanana provide the rest?

Accepted Answer

Yes! Even if you have 5 or 10 friends helping out, we will provide the full 12+ testers to ensure you have a safe buffer in case any of your personal testers drop off.

Question 14

Do I need to provide the APK or source code to AppBanana?

Accepted Answer

No. You never send us your source code or APK. You simply invite our tester email group to your Google Play Console closed track, and they download the app directly from the Play Store.

Question 15

How do testers opt-in to my closed testing track?

Accepted Answer

We provide an email list that you paste into the Play Console. Once you publish the track, we distribute the opt-in web link to our testers so they can join and install.

Question 16

How many times can I apply for production access?

Accepted Answer

There is no strict limit, but repeated rejections without meaningful changes can flag your account. That’s why we help you get it right on the first or second try.

Question 17

What information do I need to submit to Google after testing?

Accepted Answer

Google will ask you to detail how you recruited testers, how they interacted with the app, what feedback you received, and what changes you made. AppBanana provides templates to help you answer these.

Question 18

Does AppBanana provide app feedback or reviews?

Accepted Answer

Yes, our testers provide genuine usability feedback, crash reports, and bug reports. However, we do not provide fake public store reviews, as this violates Google Policy.

Question 19

How active do the testers need to be?

Accepted Answer

Testers must remain opted-in, keep the app installed, and periodically open and engage with the app over the 14-day period to generate valid usage telemetry for Google.

Question 20

What happens if a tester drops out before 14 days?

Accepted Answer

We over-allocate testers (providing more than 12) so that even if a few drop out, you will never fall below Google's strict minimum threshold.

Question 21

Do I need to update my app during the 14-day testing period?

Accepted Answer

It is highly recommended! Pushing at least one or two updates based on tester feedback proves to Google that you are actively iterating and improving your app.

Question 22

Can I test games as well as standard applications?

Accepted Answer

Yes! AppBanana tests all types of Android applications, including high-performance games built on Unity, Unreal Engine, and standard utility apps.

Question 23

Is the service available globally?

Accepted Answer

Yes, our service and our testers are global, meaning we can test apps restricted to specific regions or apps available worldwide.

Question 24

How do I track tester activity?

Accepted Answer

You can track the number of opted-in testers directly inside your Google Play Console under the Closed Testing track statistics.

Question 25

What happens if my app crashes during testing?

Accepted Answer

Our testers will report the crash. We recommend you fix the bug and push an update to the closed track. Crashes during closed testing are normal and fixing them helps your approval case.

Question 26

Do I need a published store listing before starting closed testing?

Accepted Answer

Yes, you must have your main store listing (title, description, screenshots) approved and the app reviewed by Google before the closed testing track becomes accessible to our testers.

Google Play Closed Testing FAQ