The Google Play rule
What is the 12 testers for 14 days rule?
Before an app from a new personal developer account can go to production, Google Play requires a closed test with "a minimum of 12 testers who have been opted in continuously for at least 14 days" (Google's page). Testers who opt out before 14 days do not count. Details in the 12 testers guide.
Does it apply to my account?
Google states it for personal developer accounts created after November 13, 2023. If you have an organization account, you probably do not need it, though you can still join a wave for real testers and written feedback before a launch.
Is opting in enough, or do testers have to use the app?
The rule counts opted-in testers. But when you apply for production access, Google asks how testers used the app and what feedback you received, and it can ask you to keep testing when tester engagement was insufficient. That is why TestBuddy measures use rather than installs.
What happens after the 14 days?
You apply for production access from your Play Console dashboard. The form covers your closed test, your app and its production readiness. Google says review usually takes seven days or less. The questionnaire guide goes through each question, and the refusal guide covers a "no".
Is TestBuddy allowed by Google?
Your testers are real Android developers who opt in to your closed test, install your app from Google Play and use it every day. That is what a closed test is for. There are no bots, no fake installs, and no exchange of reviews or ratings. TestBuddy is independent: it is not affiliated with Google and does not claim its endorsement. Google decides on your production access.
Joining a wave
What do I need before joining?
A Google account to sign in, a closed test in Play Console with its opt-in link, TestBuddy's tester group added to that test, and a build carrying the SDK, opened once on any phone. The closed testing setup guide and the SDK docs cover each step.
When does my wave start?
As soon as 16 developers are ready. If the wave is not full by the next Monday at 09:00 Paris time, it starts then with 13 or more developers; with fewer, it waits another week. Everyone in a wave starts the same day. See how it works.
How many testers will I get?
In a full wave, 15: every other developer in the wave tests your app. That is 15 places against a rule of 12, so one or two drops do not touch your Play counter. A wave that starts with 13 developers gives each app 12 testers.
Can I put several apps in TestBuddy?
One at a time: an account has one open campaign. When your campaign ends, you can create the next one.
Testing every day
How much time does it take?
About 30 minutes a day for 14 days: 15 apps, at least 2 minutes each, plus whatever real poking around you feel like. Several short sessions on the same app add up.
When does a day end?
At 06:00 the next morning in your time zone. Opening an app at 00:30 still counts for the evening before. If apps are left, you get a reminder email from 18:00.
What if I miss a day?
Your own recruiting pauses until you complete a full day, every app on your list. Your current testers keep testing; you stop gaining new ones. Miss three days on the same app and that place is given to another tester.
What if an app crashes or does not run on my phone?
Report it from your Today screen. The place ends without blame, its credits go back to its developer, and you get another app. You can report 2 apps per 14 days. Three reports on the same app within 24 hours pause its recruiting until its developer confirms a fixed build.
What if one of my testers drops?
Their place ends, the credits reserved for it come back to you, and a replacement is recruited among the developers still receiving places.
How do testers give feedback?
Twice per app: first impressions from day 3, a fuller review from day 10. Each is a rating from 1 to 5 and a few lines, which you read under a tester number in your production access report.
The SDK
Do I need to integrate an SDK?
Yes. Without it nobody can tell real use from a tap on Install. It is
a small Kotlin library: one dependency (the Play Install Referrer
client), no AndroidX, minSdk 24, one line in
Application.onCreate. See the
SDK docs.
Will my users see anything?
No. The SDK has no user interface. Only a tester who taps "Link it" in TestBuddy sees a short confirmation toast.
Can I remove it before production?
Yes. Keep it in your closed test build for the length of your wave,
then remove the dependency and the init line before your
production release. The SDK docs list the steps.
What if a tester is offline?
Sessions wait in a queue on the phone and are sent when the network answers. A session still counts if it reaches TestBuddy within 48 hours.
Credits and pricing
What are credits?
They count the testing you give and receive. Each validated tester day earns one credit; a tester place for your app costs 14. Your first wave is lent to you as a start advance, which your own tester days repay. Credits have no money value and cannot be bought, sold or transferred.
Is it free?
Yes, in money: no card needed. You pay in testing.
Privacy
What data do you collect?
From you: the email and account identifier of your Google account, your time zone, and your app's details and closed test link. From testers' phones, through the SDK: the link code, the time your app spends in the foreground and the objectives you choose to record. Nothing about your real users: on a phone that is not linked to a tester, the SDK only announces your app key and package name. Full list in the privacy policy.
Will other developers see my name or email?
No. Developers see their testers under a number, never their name or email.
How long do you keep test data?
Session events are deleted 120 days after they are received. Your account, campaigns, feedback and credits ledger are kept while your account exists. Ask hello@jointestbuddy.com to delete your account at any time.