Skip to content
FAQ

Questions, answered properly

Short answers where a short answer is honest, long ones where it is not.

The requirement

What Google actually asks for, and who is exempt.

If you created a personal Google Play developer account on or after 13 November 2023, you cannot publish to production until you have run a closed test with at least 12 testers opted in continuously for 14 days. Google introduced the rule with 20 testers in November 2023 and reduced it to 12 in December 2024. The 14-day window never changed.

It applies to personal Play Console accounts created on or after 13 November 2023. Organisation (business) accounts are exempt, and so are personal accounts created before that date. Once an app has production access, its future updates never need testers again.

How the service runs

From payment to production access.

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.

Testers and legitimacy

Who the testers are, and whether this is allowed.

Yes. Every tester is a real person opting in with their own Google account and installing your app on a real Android device: Samsung, Xiaomi, Pixel, Realme, OnePlus, Vivo, Oppo and Motorola among them. Emulators and fake accounts do not satisfy Google and we do not use them.

Google's public requirement focuses on completing a closed test with enough opted-in testers and demonstrating meaningful testing. Google does not endorse Applime or certify third-party testing providers. A paid service is not a substitute for real use and honest feedback, so describe how you recruited testers truthfully in your production-access application.

Google's closed-test rule does not state that all testers must live in one specific country, but every tester must be eligible for the track and able to install the app. If your app or track has country restrictions, tell us before the test so availability can be checked.

Yes, and it is common. A rejection usually means testers dropped out, the count fell below 12, or engagement was too thin. You do not need a new app or account. You restart the 14 days on the same closed track. We take it from there.

Yes, 100%. If Google rejects your production access application after our 14-day closed test, we refund the full price of your selected plan. If you would rather try again, we re-run the entire test free instead. Ask within 30 days of the refusal and the refund reaches your original payment method within 3 business days of approval.

You get your money back, or a free re-run, your choice. The only runs the guarantee does not cover are ones ended by you: removing testers, halting the rollout, unpublishing the release, deleting the closed track, or applying before day 14 is complete. Our refund policy sets out the detail.

Price, payment and refunds

Why ₹349, and what happens if it goes wrong.

There is no customer dashboard, account system, sales team or ASO upsell to fund. You choose 14, 16 or 25 testers and pay only for the managed testing run. Keeping the service focused is why the entry plan starts at ₹349.

Choose 14 testers for ₹349, 16 testers for ₹449 or 25 testers for ₹949. Google needs at least 12 testers opted in continuously for 14 days on affected accounts, so every plan provides a buffer above that minimum.

Yes, 100%. If Google rejects your production access application after our 14-day closed test, we refund the full price of your selected plan. If you would rather try again, we re-run the entire test free instead. Ask within 30 days of the refusal and the refund reaches your original payment method within 3 business days of approval.

You get your money back, or a free re-run, your choice. The only runs the guarantee does not cover are ones ended by you: removing testers, halting the rollout, unpublishing the release, deleting the closed track, or applying before day 14 is complete. Our refund policy sets out the detail.

Choose a plan and message us on WhatsApp; we send a secure Razorpay payment link in the same chat. It supports UPI, credit and debit cards, net banking and popular wallets. International cards work too. We never see or store your card details.

Yes. Each app needs its own closed test, so place one order per app. Message us on WhatsApp if you are running several at once and we will keep them coordinated.

Answered? Then let's start the clock.

One WhatsApp chat and one secure payment to begin. No Applime account to create.

  • Testers within 6 hours
  • 100% money-back if rejected
  • No account needed

Closed test complete

14 of 14 days complete, 12 testers held