What happens across the 16 days
Two things are asked of you: pay, and send one WhatsApp message. Everything after that is ours.
A typical run
day 9Day 0, minute 1
You pay ₹349
Razorpay handles it: UPI, card, net banking or wallet. You are not asked to create an account, pick a plan or add anything at checkout.
Day 0, minute 2
You land on WhatsApp
The success page opens a WhatsApp message with your payment reference and app details already written. Send it. That message is your entire onboarding.
Day 0
We check your track is set up correctly
Most failed runs are misconfigured on day zero: an internal track instead of a closed one, or a release saved as a draft and never rolled out. We check both before anyone joins.
Within 6 hours
Testers begin opting in
Real people open your opt-in link with their own Google accounts and install from the Play Store on their own Android devices. The group of 14 is usually complete inside a day.
Day 1
The clock starts
Your 14 days are counted from the moment the twelfth tester opts in, not from when you created the track. Play Console shows the count on the closed testing page.
Day 7
First check-in
We confirm the count is still at or above 12 and top up if anyone has dropped. This is the check most self-run tests never do, and it is why they fail.
Day 14
The requirement is met
Play Console unlocks the production access application on your dashboard. We message you the same day.
Days 15–16
Buffer, then apply
We hold testers two extra days so you are never applying on a technicality. We help you answer the questionnaire. Google asks what feedback you got and what you changed, and vague answers get refused.
What we need from you
- Your app name, as it appears in Play Console
- Your package name, for example
com.yourstudio.app - The closed testing opt-in link from Play Console
- A WhatsApp number we can reach you on
That is the complete list. We never ask for your Play Console password, and you should never give it to anyone who does.
What you must not do
- Remove testers from the track
- Halt the rollout or unpublish the release
- Delete or recreate the closed track
- Apply for production access before day 14 is complete
Shipping updates to the closed track during the run is fine and does not reset anything. Taking the track down is what breaks continuity.
About the process
Still unsure whether the rule even applies to you? Read the requirement in full.
Testers usually begin opting in within 6 hours of us receiving your closed testing link, and the group is complete within 24 hours. Your 14 days are counted from the moment the 12th tester opts in, not from when you created the track.
Three things: your app name, the closed testing opt-in link from Play Console, and a WhatsApp number to reach you on. That is the entire onboarding. We do not need your Play Console password and will never ask for it.
You do not add them one by one. In Play Console open Testing, then Closed testing, create or open a track, and set the tester list to allow anyone with the opt-in URL, or send us the list link and we will return the 14 Gmail addresses for you to paste in. We walk you through it on WhatsApp either way.
No. Keep the closed track live and do not remove testers or unpublish the release. We check in around day 7 and again on day 14. Everything else is on us.
You apply for production access from the Play Console dashboard. Google reviews the application and usually responds within a few days. We stay reachable on WhatsApp through that review in case Google asks for anything else.
Two minutes of your time, then it is handled.
Pay ₹349, send one message, and the next thing you do is apply for production access.
- Testers within 6 hours
- 100% money-back if rejected
- No account needed
Closed test complete
14 of 14 days complete, 12 testers held