Frequently asked questions

If your developer account is a personal account created on or after 13 November 2023, Google requires a completed closed test before you can apply for production access. The test needs at least 12 testers opted in for 14 consecutive days. Organisational accounts, and personal accounts created before that date, are exempt. Play Console always states the exact requirement for your account — that is the number Google checks when you apply.

Google's floor is 12 testers opted in for the full 14 days, but 12 is a floor, not a target. If a single tester opts out on day 12, the counter restarts from day one, so a group of exactly 12 has no margin at all. We run 15 testers per campaign: the three extra seats absorb opt-outs and quiet testers without putting your 14 days at risk.

Yes. The requirement is per app, not per account. Every new app needs its own 14-day closed test, including apps from developers who already have production access on other titles. Once an app has production access, you can ship updates with no further testing.

No. Only the closed testing track counts toward the production access requirement. Internal and open tracks are genuinely useful for other purposes, but Google specifically requires a closed track with real testers opted in for the full 14 days.

It starts when your testers have opted in through your opt-in link or Google Group and installed the app — not when you paste email addresses into Play Console. That gap is why so many developers add 12 testers and then watch the counter sit at zero. Our testers opt in within hours, so day one starts almost immediately.

Yes. Google requires 14 consecutive days with at least the minimum number of testers opted in. If your opted-in count drops below that minimum on any single day, the window restarts — which is why buffer testers matter more than a perfect plan.

1) You publish your task with the Google Play link and the Google Group link — about a minute. 2) Testers join the group and install your app; the moment the 15th tester has installed it, the 14-day cycle starts automatically. 3) Testers keep the app installed and stay active on a staggered schedule, and you can watch progress in your dashboard. 4) Before day 10 you receive a written test report with the issues we found and our suggestions. 5) On the final day the last activity check-in completes the task and each tester's commission settles automatically. 6) Every tester keeps the app installed for two extra days as a buffer — 16 days in total.

Recruiting normally completes within 8 hours. Publishing takes about a minute, and you do not need to chase anyone: as soon as 15 testers have installed your app the 14-day cycle starts on its own.

Two links: your app's Google Play listing and the Google Group that testers join. The group is required by Google Play's own closed testing flow. There is no SDK to integrate, no code change and no need to give us access to your Play Console.

Yes. We check every day whether a new build is on your track. When you publish an update, testers install it and keep testing on the latest version, so the report you receive at the end reflects the newest build rather than an early one.

Yes. Each app is a separate task with its own 15 testers and its own 14-day window, and tasks run in parallel. Agencies and studios running several apps side by side are routine for us.

The final activity check-in closes the task, and the escrowed commission is settled to each tester automatically. At that point the tester cohort has satisfied Google's requirement and you can open Play Console and apply for production access.

Real people on real physical Android devices. There are no emulators, no cloned accounts and no simulated traffic. We also run device ID, IP and device-model checks so one person cannot quietly occupy several seats.

A global pool spanning many countries and time zones. Google counts opted-in testers wherever they live, and your app's distribution countries are a separate setting in Play Console, so tester location does not affect the requirement either way.

Mainstream Android phones across brands and Android versions. Coverage on older and lower-end hardware is part of the point — that is where crashes, ANRs and layout problems usually hide, and it is the compatibility evidence Google's reviewers look for.

Yes. Testing focuses on functionality, flows and stability rather than language, and we brief testers on which screens and flows to exercise inside your app.

They use it. The requirement is genuine usage, not an installed icon: testers open the app across the cycle and go through real flows. On the first day they must install it and spend at least 30 seconds in it; after that they keep coming back on scheduled days rather than all at once, which is exactly the activity pattern Google is looking for.

One flat price per app: $10. It covers the entire campaign — tester rewards, escrow, verification, daily monitoring, the test report and settlement. There is no subscription, no per-tester fee and no setup fee.

No. You pay once when you publish the task. Everything that follows — recruiting, monitoring, replacing testers who go quiet, the written report and the final settlement — is included in that single payment.

Payment happens at checkout on the publisher dashboard, and commissions are paid out to testers through PayPal once a task completes. You keep a record of every task payment on your side.

Each app is its own task at the same flat price. Nothing changes in the process — publish the second task and it runs in parallel with the first, with its own 15 testers and its own 14-day window.

No, never. We do not ask for your password, your console access or your signing keys. All we need is the public opt-in link or Google Group that Play generates for your test, so you stay in full control of your account the entire time.

Yes. Google's requirement is that real people genuinely test your app for 14 days, which is precisely what this service delivers: real installs, real usage and real feedback. Nothing in Google's policies restricts where you find your testers, and you provide the opt-in link from your own console.

Every install comes from a distinct real device with its own Google account, and we actively block emulators, duplicated devices and shared IPs. In other words, the behaviour we produce is the behaviour Google's reviewers are looking for — not traffic that has to be explained away.

Your app details are shared only with the testers assigned to your task, and we never ask for your source code, store credentials or customer data. The only thing exchanged is the public opt-in link.

Activity is checked every day, and a tester who misses the required check-ins is not paid for them. Because a campaign runs 15 testers against a 12-tester minimum, a quiet tester does not push your opted-in count under the line — you find out during the cycle, not on the last day.

Yes. The publisher dashboard walks you through publishing, and our written guides cover the Play Console side step by step: creating the closed testing track, creating the Google Group testers join, and applying for production access once the 14 days are done.

A Google Play developer account with your app uploaded to a closed testing track, and the Google Group you want testers to join. If your console looks different from the guide, message us from the site and we will walk you through it.

Usually within a few hours, often much sooner. Messages sent from the site go straight into our support queue and the answer comes back as a reply in your message box.

Day 1: publish the task and let recruiting run — testers are in place within 8 hours, and you do not need to do anything else. During the cycle: check the dashboard, and read the test report when it arrives before day 10. Last day: the final check-in closes the task, settlement runs automatically, and you can apply for production access in Play Console right away.

Yes — most of our volume is repeat publishers. Every new app needs its own 14-day closed test, and each task goes through exactly the same process, reporting and settlement.