What happens across the 16 days
Choose a plan and send one WhatsApp message. We confirm the details, share the secure payment link and coordinate everything after that.
A typical run
day 9Day 0, minute 1
Choose your tester cover
Select 14 testers for ₹349, 16 for ₹449 or 25 for ₹949, then message us on WhatsApp. We confirm the plan and send the secure payment link in the same chat.
Day 0, minute 2
Send the handoff message
The success page prepares a support message with your payment reference and app details already written. Send it to complete 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.
In Play Console open Testing, then Closed testing, create or open a track, and manage testers with an email list or Google Group. Add the Gmail addresses we provide, publish the closed-test release, then share the track's opt-in link. Applime support can walk you through the setup and never needs your Play Console password.
Keep the closed track live, do not remove testers or unpublish the release, and review the feedback and testing signals you receive. Google asks what testers did, what feedback they gave and what you changed, so keep brief notes and release fixes to the closed track when needed. We check in around day 7 and day 14.
You apply for production access from the Play Console dashboard and answer questions about tester recruitment, engagement, feedback, changes and release readiness. Google says reviews usually take seven days or less, although they can take longer. Applime support stays available during the review.
Two minutes of your time, then it is handled.
Choose your tester plan, send one handoff message, and we coordinate the run through to your production-access application.
- Testers within 6 hours
- 100% money-back if rejected
- No account needed
Closed test complete
14 of 14 days complete, 12 testers held