How to Choose a Google Play Closed Testing Service: 10-Point Checklist
Comparing closed testing services for the 12 testers / 14 days rule? Check these 10 things before you pay: track record, tester count, duration, real devices, logs, updates, refunds.
How to Choose a Google Play Closed Testing Service: 10-Point Checklist
Personal Google Play developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for at least 14 days before they can publish to production. Many solo developers can't find 12 people with Android phones who will stay enrolled for two weeks, so they look for a paid closed testing service. Those services differ a lot in tester count, duration, and refund terms.
This checklist covers the 10 things to check before you pay. Use the same criteria whichever service you pick. Each item ends with a short note on how Doply handles it, so you have one reference point to compare against.
First, one rule: Google decides whether you get production access. Be careful with any service that promises approval.
1. Is there a public track record?
A failed closed test costs you two weeks. If you've never heard of a service, check how many apps it has run and whether there are reviews from real customers on a platform the service doesn't control. If a service won't share any numbers, ask why.
- Check: number of apps tested, production approvals, reviews on third-party platforms
- Doply: 5,700+ apps have completed closed testing and 5,000+ have been approved for production. 2,556 reviews with a 4.9 rating on Kmong, a Korean freelance marketplace (as of November 2026).
2. How many testers, and is there a buffer above 12?
Google requires 12, and if a tester drops out mid-test the count can fall below 12. Google also looks at how active testers were, so extra testers help. Look for a buffer, not exactly 12.
- Check: number of testers provided, what happens if the app fails to install on some devices
- Doply: 14 to 16 testers. If fewer than 12 devices have the app, the status changes to "Insufficient Devices" and the Doply team fixes it right away.
3. Does the test run longer than 14 days?
14 days is Google's minimum. If the start date or install timing slips a little, you can come up short. Check for buffer days.
- Check: total duration, when the clock starts
- Doply: 18 days (14 required + 4 buffer). The test starts as soon as you pay, and Doply runs 24/7, 365 days a year.
4. Are the devices real?
The point of the test is real use on real devices. Ask whether the service uses emulators or real phones, and which models and Android versions. Also check that your app's minSdk can install on those devices.
- Check: real devices or emulators, models and Android versions
- Doply: 54 real Samsung Galaxy devices (Android 13 and 14). Your minSdk must be 33 or lower to install.
5. Can you check compatibility before paying?
If your app can't install on the service's devices, paying is pointless. See whether the service checks compatibility first.
- Check: pre-payment compatibility check, how long it takes
- Doply: The compatibility check finishes almost instantly, and payment only opens when 14 or more devices can install your app.
6. Can you see progress and launch records?
Waiting two weeks and hoping it's working is stressful. Check whether you can see how many devices have your app, whether it launched each day, and which version is installed. These records also help when you write the production application.
- Check: dashboard, per-device status, launch screenshots, public tester list
- Doply: The dashboard shows live, per-device test status. A screenshot is uploaded 2 seconds after each launch (large apps and games may show a black screen). The tester list is public on the testers page.
7. How are new versions picked up?
Google recommends updating your app during the closed test. Check when and how your new versions reach the service's devices.
- Check: how often updates are checked, how you can confirm the installed version
- Doply: New versions are checked and updated every day starting at midnight KST. Once a new version is live on your closed track, it reaches the devices the next day. We recommend updating every 2 to 3 days.
8. Does it help with the production application?
After 14 days you fill in the production access application: what you tested, the feedback you got, and what you changed. Support for this varies a lot between services.
- Check: whether the service helps with the questionnaire, and how much
- Doply: Doply writes the answers for the production application questionnaire and gives them to you. For tips on the questions themselves, see Production Access Rejected: Causes and Fixes.
9. Are the extension and refund terms clear?
If approval is slow or you're asked to keep testing, you may need more days. Check in writing, before paying, whether free extensions or reruns are offered, what the conditions are, and when refunds apply.
- Check: free extension conditions and length, cost of a rerun, refund conditions
- Doply: If you release two or more updates within the 14-day closed test, the test is extended by 18 days for free. If you don't meet that condition, you can pay to run it again. You get a full refund if the app is not installed on 12 or more test devices, or if a service outage causes you harm. After the app is installed on 12+ devices and testing has started, it is not refundable. Details are in the pricing and refund policy.
10. Is the business behind it clear?
You need someone to contact if something goes wrong. Check that the operator's business details are public and where the official place to buy is. Buying from an unofficial reseller can leave you without support.
- Check: business details, official sales channel, support contact
- Doply: The official site is doply.io. Doply is run by KyuLabs in Korea, and business details are in the site footer.
What to check on your side first
Whichever service you choose, a few things are up to you.
- Confirm your account is personal. Organization accounts are not covered by the 12 testers / 14 days rule, so you don't need a service.
- Check your closed track's countries. The service's tester accounts must be in a country included on your closed testing track. Doply's tester accounts are Korean, so South Korea must be included. Your production release can exclude it.
- Check how your app is built. Doply doesn't accept TWA (Trusted Web Activity) apps because their production approval rate is low. A native WebView or Capacitor wrapper is a better option.
- For paid apps, apply a 100% discount promotion for the test period. Don't switch the app to free: Google does not let a free app go back to paid.
- Plan your updates. A service can handle the testers, but shipping updates is still your job.
Checklist summary
| Item | What to look for |
| Track record | Apps tested, approvals, reviews |
| Tester count | A buffer above 12 |
| Duration | Buffer days beyond 14 |
| Devices | Real devices, Android versions |
| Pre-check | Compatibility check before payment |
| Progress records | Dashboard, per-device status, screenshots |
| Updates | How often, how to confirm |
| Application help | Support for the production questionnaire |
| Extension and refunds | Clear written conditions |
| Business | Business details, official sales channel |
To compare paid services with finding testers yourself, see How to Get 12 Testers: Free vs Paid. If you haven't set up the track yet, start with How to Set Up a Closed Testing Track.
Doply costs $6.99 per app plus applicable tax, paid by card or PayPal. See what's included on the Doply service page.
FAQ
Does a closed testing service guarantee production approval?
No. Google decides. A service keeps the tester count and duration stable; shipping updates and checking your application is still up to you.
Isn't 12 testers enough?
Google requires 12, but one dropout can take you below 12, and Google also looks at how active testers were. A buffer is safer.
How much do closed testing services cost?
It depends on the service and plan. Compare tester count, duration, and extension and refund terms, not just the price. Doply is $6.99 per app plus tax.
Do organization accounts need a closed testing service?
No. Organization accounts are not covered by the 12 testers / 14 days requirement.
Experience It Yourself
Simplify your Android app closed testing with Doply. Let us handle the complex tester management while you focus on core development.
Learn More →