Real people, on their own phones
Verified Android users install and use your app on physical devices, opting in with their own Google accounts. No emulators, no automated accounts.
Google Play closed testing
Without friend hunting.
₹349 once — lowest price in our sourced comparison.
This is the real email Google sends when production access is granted. Your own approval arrives from Google Play Support.

Recently published public Play Store listings, supplied on 11 September 2026.








If a completed run does not get you through, you choose: another run at no charge, or a full refund. Both are written into our terms.
Verified Android users install and use your app on physical devices, opting in with their own Google accounts. No emulators, no automated accounts.
If production access is refused after a completed run, take a free re-run or a full refund. Claim within 30 days; refunds are issued within 3 business days.
Every plan adds more than the 12 testers Google requires, and holds them for 16 days rather than 14, giving the run a buffer against drop-offs.
Check-ins on day 7 and day 14, help with the production access questionnaire, and someone on WhatsApp for anything else. Mon–Sat, 10:00–19:00 IST.
Getting twelve names onto a tester list is easy. Keeping twelve people opted in for fourteen unbroken days is the part that fails.
Days of recruiting and chasing
Testers begin joining within 6 hours
Friends who install once
Verified Android users on real devices
People drift off and never say
14–25 held for the full 16 days
Nobody tells you until day 14
Spare testers absorb it, we check on day 7
Work them out alone
Guided answers based on your actual run
Start again, on your own
Free re-run, or 100% of your money back
Comparing paid services instead? See the established providers, with sources.
The support and sixteen-day run stay the same; only the tester buffer changes.
Real people opt in to your own closed track, install your build and keep it there. You watch the count in Play Console the whole time.

Apex Habits: Habit Tracker
com.mangalgupta.apexhabits
Closed testing · Android 8+
You’re a tester
Opted in continuously for 14 days
The application asks how you recruited testers, what feedback you got and what you changed. Specific answers pass. We help you write yours.
Through an opted-in Android testing community whose members installed the app and used it through the period.
No outreach spreadsheets, no group-chat reminders. Send the opt-in link after paying and testers begin opting in within the stated start window.
Google counts fourteen unbroken days. We hold your testers for 16, so the count never dips at the edges of the window.
No chasing testers. No silent drop-offs. One path through the requirement.
Choose 14, 16 or 25 testers and message us on WhatsApp. We confirm the plan and send a secure Razorpay payment link in the same chat; there is no account to create.
After payment, use the support handoff with your order reference already filled in. Send your app name and the closed testing opt-in URL from Play Console.
Real people on real Android devices join your closed track and install the app. Every plan adds more than Google's 12-tester minimum to protect the run against drop-offs.
Testers keep the app installed and open it through the period. We check in at day 7 and day 14. You do nothing except leave the track live.
Play Console unlocks the production access application. You submit it, Google reviews it, and Applime support remains available while you wait.
Experiences shared after completing a managed Google Play closed test.
“Testers were in the track by the same afternoon. The count stayed above the requirement for the full fortnight, and I could apply for production access on schedule.”
“I sent the link in the evening and testers started joining the next morning. The day-seven check-in arrived without me needing to chase anyone.”
“The spare testers made the difference. One person left halfway through, but the required count did not fall and the test stayed on schedule.”
“This was my second attempt after a refusal. The guidance helped me make my questionnaire answers specific, and Google approved the next application.”
“Two testers left during my earlier self-run test and the count dropped. The extra tester buffer here kept the new run on schedule.”
“No new dashboard to learn and no Play Console password to share. I sent the opt-in link and followed progress from my own account.”
“I had recruited friends and then lost several before the first week ended. With Applime, the tester count simply stayed where it needed to be.”
“I could follow the count in my own console throughout the run. On day fourteen, I received clear instructions for the production-access application.”
“I liked that I could see the testers in my own Play Console. There was no separate dashboard and I never had to share my account password.”
“My first application was too vague. The second one explained the testing and feedback properly, and the production-access request went through.”
Every plan covers the same sixteen-day managed run. The only difference is the number of testers protecting your schedule above Google’s minimum.
The complete run with two testers above Google's minimum.
A wider buffer for extra protection against tester drop-offs.
The largest tester buffer for launches where schedule certainty matters most.
Choose a plan in WhatsApp, then use the secure Razorpay link we send. Card details are handled by Razorpay.
Quick answers about testing, timelines and the guarantee.
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.
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.
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.
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.
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.
One WhatsApp chat, one secure payment, and the clock is running. No account to create.
100% money back if Google rejects your app.