Google Play testing service FAQ. Straight answers, before you order.

Because finding 12 to 25 real people with Android devices who reliably open your app every day for 14 days is much harder than it sounds, and one quiet dropout can leave your count short. We keep a verified tester network across 120+ countries, replace dropouts immediately, and support you until production access is granted. See everything included in our android app testing service.

We are mobile developers ourselves, with hundreds of shipped apps behind us, so we know exactly what Google's review looks for. You also get what freelancers do not offer: a live progress dashboard, guaranteed tester replacement, a written report, proven questionnaire answers, and a money-back guarantee. Meet the team.

Two things: a Google Play developer account with the one-time $25 fee paid, and your app uploaded to a closed testing track in Play Console. Internal testing does not count toward the requirement, so the build must sit on a closed track; our testing tracks comparison explains the difference. Just paid the $25 fee? Start here. And if you get stuck, order first and we walk you through the upload on WhatsApp.

Every new app on a personal account needs its own closed test with 12 opted-in testers for 14 days; the requirement is per app, not per account. The same people can test more than one of your apps, but each app needs them to opt in again and hold its own unbroken streak. Our per-app testing guide shows how to plan a portfolio.

100% real humans on physical Android devices with personal Google accounts. Each tester has a unique device, IP address, and location. We never use emulators, bots, or scripts: Google's Play Integrity checks are built to catch exactly that, and fake activity typically does not count toward the requirement anyway. Here is why emulators fail closed testing.

Real devices from Samsung Galaxy, Google Pixel, Xiaomi, Huawei, OnePlus, Oppo, Vivo, and more, running Android versions 7 through 16. That spread gives your app genuine compatibility coverage across screen sizes, chipsets, and Android versions before the public ever sees it.

14 consecutive days, exactly as Google requires. Your dashboard shows the day counter from day 1, and we do not stop at the finish line: our testers stay opted in until you confirm Google has approved your production access, so your test never falls short while the review is still running.

Yes. Every plan includes a written bug report; Professional and Enterprise include more detailed reporting with reproduction steps. Testers flag crashes, performance problems, and UX friction they hit during real daily use, so you reach Google's review with a stronger build than you started with.

Our testers are spread across 120+ countries, including the USA, UK, Germany, India, Brazil, Indonesia, and the Philippines. Google counts opted-in testers wherever they live, and your app's launch countries are a separate store-listing setting. Our guide on testers in different countries explains both gates.

Yes. Our tester network has capacity for hundreds of apps at the same time, and your testing still starts within 4-6 hours no matter how busy the queue is. Agencies running several apps in parallel are a normal day for us, not a special request.

The clock starts when testers accept your opt-in link, not when you paste their emails into Play Console. That difference is why so many developers add 12 testers and watch the counter stay at zero. Our testers opt in within hours of receiving your link, so day 1 starts almost immediately. If your count ever looked stuck, this is why added testers do not get counted.

Yes. Google requires 14 consecutive days with at least 12 testers opted in for the whole window; if the count dips on day 9, the streak restarts from zero. That is the single most common way DIY attempts fail, and it is why we monitor daily and replace dropouts immediately. More detail in our 14 consecutive days guide.

Yes. Uploading new versions to your closed track during the test is allowed and does not reset the clock, as long as testers stay opted in. Many developers ship fixes as our bug reports come in and reach Google's review with a better build. Our guide on updating your app during closed testing covers the safe way to do it.

Yes. Your app, its data, and your business information are never shared with anyone outside the assigned testers, and we sign NDAs on request. We never ask for your source code, your Play Console password, or your developer account access. The only thing you send us is the public opt-in link Google generates.

No, never. You paste our tester list into your own console, which takes about 3 minutes with our step-by-step guide, and send us the public opt-in link. We never ask for your password, console access, or developer account details, and every opt-in is visible in your own dashboard, so you verify everything yourself while staying in full control.

You can opt in with a second Google account, and a single self opt-in will not sink you. The trap is trying to fill the list with several of your own accounts: Google links accounts by device, network, and payment fingerprints, and a ban on a linked account can cascade to your developer account. Not worth it when the other 11 testers are the hard part anyway. We wrote up whether you can be your own tester in detail.

Yes, completely. Your dashboard includes step-by-step instructions with screenshots for every stage, and a human on WhatsApp answers within minutes if your console looks different from the guide. We also hand you proven answers for the production questionnaire. Start with how the process works; most first-timers finish their part in about 7 minutes.

All categories: games, utilities, productivity, social, e-commerce, health and fitness, education, and everything in between. New app or an existing one that needs its closed test, it makes no difference. If your app needs anything special to test, like a demo login, tell us and we brief the testers.

24/7, on WhatsApp and email. Most messages get a reply within minutes, any day of the week, and overnight questions are usually answered within a few hours. Support does not end at checkout either: we stay with you through setup, the 14 days, the production application, and Google's review.

Of course. Most of our volume is repeat customers: solo developers back with app number two, and agencies that run 5 to 10 apps through us regularly. Every order gets the same process, the same dashboard, and the same guarantee. Each new app needs its own 12-tester, 14-day test, and we handle that every time.

You apply for production access in Play Console. Google asks a short questionnaire about your testing, and we hand you proven answers based on your actual test, so you are never guessing. Google's review usually takes 7 days or less, and we stay available until the approval email lands. Our guide to the production access questionnaire shows what Google asks.

Two, and you pick: a full refund of what you paid, or a free retest where we rerun the entire 14-day cycle with our testers at no cost. Most developers take the retest, because rejections are usually fixable and the second pass goes through. Either way, the refund policy spells it out.