iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If your personal Google Play developer account was created after November 13, 2023, Google requires you to complete a closed test before applying to publish your app in production. The minimum is 12 testers continuously opted in for at least 14 days. You then answer questions about the test, your app, and its production readiness; meeting the numerical minimum alone does not guarantee approval. This guide covers that requirement for the specified newer personal accounts, not every developer account or every app.
Who needs to complete the production-access test?
Google applies this prerequisite to personal developer accounts created after November 13, 2023. Developers using other account types, or personal accounts created on or before that date, should check the applicable requirements in Google Play Console Help rather than assume this specific rule applies to them.
For accounts in scope, production access is gated by a qualifying closed test and an application in Play Console. Google also says production and some other Play Console features remain unavailable until the requirements are met.
Recommended Free Tools
What does “12 testers for 14 days” mean?
At least 12 testers must remain opted in to the closed test continuously for a minimum of 14 days. The requirement measures continuous opt-in status, not simply the number of people who ever joined or the total number of tester-days.
#1 Best Overall
- ⚠️ ONLY COMPATIBLE with Android USB-C Phones and iPhone 15, 16, 17 Models (15, 15 Pro, 15 Pro Max, 16, 16 Pro, 16 Pro Max, 17, 17 Pro, 17 Pro Max) ⚠️ Android OS: 9, 10, 11, 12, 13, 14. iOS Operating System: iOS 17-26. Application version – 5.13.0.
- ⚠️ Compatible Android Devices Include: ⚠️Samsung Galaxy S8, S8+, S9, S9+, S10, S10 Plus, S10e, S10 5G, S20, S20+, S20Ultra, S20 FE 5G, S21, S21+, S21 Ultra, S22+, S22 Ultra, S23, S23+, S23Ultra, S24, S24 Ultra, S24+. Samsung Galaxy A31, A32, A41, A50, A51, A51 5G, A51 5G UW, A52, A52 5G, A70, A71, A71 5G, A71 5G UW, A72. Samsung Galaxy Note 8, 9, 10, 10+, 20, 20 Ultra. LG G6, G7, G8, G8s. Google Pixel 3, 3 XL, 3a XL, 4, 4 XL, 5, 6, 6 Pro, 7, 7 Pro, 8, 8 Pro, 9, 9 Pro XL. OS: Android 9, 10, 11, 12, 13, 14. Application version – 5.13.0.
- PORTABLE ON THE GO: Manage your diabetes at or away from home with the Dario device (for iPhone) being small and light enough to fit in your pocket.
- SMART GLUCOSE METER: Track & monitor on your phone with free Dario Health App (US Only). Please make sure to pull the lancet loader back before hitting the release button.
- QUICK & EASY: No coding with results in 6 seconds and only a 0.3µ sample needed.
- A tester who opts out before completing 14 consecutive days does not meet the continuous-period requirement.
- If that tester opts back in later, their qualifying period starts again; they must complete another 14 consecutive days.
- Keep enough eligible testers opted in throughout the period so that at least 12 meet the requirement.
The count is only the entry threshold. Google’s application also asks whether testers engaged with the app and whether their behavior resembled expected production use. A test with the required headcount but little meaningful use may not establish production readiness.
How do I apply for production access?
- Set up and run a closed test in Play Console. Google provides instructions for configuring tester access and sharing a test in Set up an open, closed, or internal test.
- Confirm that at least 12 testers have stayed opted in continuously for at least 14 days.
- Open the Play Console Dashboard and select Apply for production.
- Complete the three application sections described below. Select Next to save and move between sections, then select Apply in the final section to submit.
If you discard a section or leave it without selecting Next, that section is not saved. The final section must be submitted with Apply.
What questions does the production-access application ask?
The application has three parts. Prepare evidence from the test before filling them out; Google asks about actual tester activity and real readiness decisions, not hypothetical plans.
About your closed test
Expect questions about how easy it was to recruit testers, whether they used the app’s available features, whether their behavior matched expected production use, and what feedback you received and how you collected it. Be ready to describe any differences between test behavior and the use you expect after release.
About your app or game
Google asks who the app or game is for, what value it provides (or what makes a game distinctive), and your estimated first-year install range. Describe a specific intended audience and a concrete user outcome. Choose an install range you can reasonably explain; Google asks for an estimate but does not prescribe a forecasting method. The estimate is not a commitment or guaranteed forecast.
Google says these answers are not shown publicly on Google Play and do not affect app visibility, Play Console feature access, or developer-program eligibility.
Rank #3
- Compatible test strips: this meter uses KetoBM ketone test strips (50 count) and KetoBM glucose test strips (100 count), sold separately. Check listing images for compatible strip packaging.
- 2-in-1 Ketone & Glucose Testing: One smart meter for both blood ketone and blood glucose testing. Perfect for anyone following a ketogenic diet who also wants to track blood glucose. No need for two devices, one complete kit.
- Free Bluetooth App: Syncs wirelessly to our free iPhone and Android app. Log readings, view trends and export your data — no subscriptions, no hidden fees, ever.
- Complete Starter Kit & Glucometer: Includes 10 ketone test strips, 10 glucose test strips, 20 lancets, lancing device, and carrying case. A complete system ready to use out of the box.
- FDA-Cleared: Delivers consistent blood glucose and ketone readings for at-home testing.
About your production readiness
Explain what you changed in response to closed-test learning and how you decided the app was ready for production. If you made no changes, describe what you tested and why the results supported that decision. Do not invent fixes or claim checks you did not perform.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHow to prepare accurate sample answers
Use the following frameworks to organize your own evidence, not as answers to submit unchanged. Replace each prompt with facts from your test. If you do not know an answer, gather the information or state the limitation honestly.
Closed-test questions
- Recruitment: “Recruiting was [easy / required effort] because [specific reason]. We invited [the real audience and channels]. Our testers included [relevant audience or device range, if true].”
- Engagement and feature use: “Testers tried [features they actually used]. We expected users to [expected behavior]. During the test, usage [matched / differed] in these ways: [observed examples]. We followed up by [action taken, if any].”
- Feedback: “We collected feedback through [actual channel or channels]. Testers reported [themes or representative issues]. We reviewed the reports by [real method] and prioritized [items actually addressed].”
App or game questions
- Audience: “This app is for [specific users] who need to [task or need].” Avoid describing the audience as everyone if the product is intended for a narrower group.
- Value or distinction: “It helps users [specific outcome] by [actual feature or approach].” For a game, describe its real gameplay or experience rather than relying on broad marketing claims.
- First-year installs: Select the range in Play Console that reflects your defensible estimate. Do not present it as a guaranteed result.
Production-readiness questions
- Changes made: “Based on [specific feedback or observed issue], we changed [actual change]. We checked the change by [verification actually performed].” If the test did not prompt a change, explain the evidence behind that decision instead.
- Readiness decision: “We consider the app ready because [real test results, stability checks, core-flow coverage, policy review, and resolution of release-blocking issues]. Remaining limitations are [honest description].” Include only checks and results you can support with test notes or the app itself.
What evidence should you collect during the test?
Keep a straightforward record so your application reflects what happened rather than what you intended to happen. Google recommends keeping a record of feedback, and its questions map to the following evidence:
Rank #4
- Wide Compatibility & Protocol Detection: Supports standards from USB 2.0 to USB4 v2 and handles up to 48V/5A; X-Ray functionality distinguishes between sub-15W and PD3.1 EPR profiles while detecting retimers, SBU types, and PHY connections.
- Complete Protection Kit: Includes a dedicated screen protector to prevent scratches during professional field use; the compact, portable design is engineered for technicians and hardware enthusiasts who need deep diagnostic power on the go.
- Bluetooth Connectivity & App Integration: Syncs with the iOS and Android app to unlock X-Ray diagnostics; enables free firmware updates to access six new read categories including PD 3.1, Thunderbolt 5, and DP Alt Mode signal support.
- Advanced Pin Testing & eMarker Mapping: Utilizes a 25-pin continuity check to map internal pinouts and measure Vbus resistance; reads eMarker chips to verify manufacturer IDs, EPR status, and authenticity directly from the cable’s hardware.
- Digital Interface & Real-Time Metrics: Features a bright screen with three diagnostic views displaying maximum wattage and data rates; provides a clear visual guide for proper cable insertion and immediate feedback on cable capabilities.
- Who the intended audience is and how testers were recruited.
- Which features and scenarios testers tried, including features they missed.
- Whether their observed behavior matched expected real-world use, and any differences.
- What feedback arrived, the channel it came through, and how you reviewed it.
- Which issues you found, what you changed, and how you verified each change.
- What checks support your decision that the app is ready, along with any remaining limitations.
Recruit testers who resemble the intended audience, not only people who can install the app. Give them clear instructions about the features and scenarios to try, and provide an obvious channel for reports. Google identifies personal and professional networks and relevant communities as possible recruitment routes. Feedback can be collected directly or through private Play testing feedback; testing feedback does not become a public review.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should you check before submitting?
Review the test feedback and address release-blocking issues before applying. Google advises developers to check the following:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Policy compliance.
- Accurate audience and content-rating settings.
- Functional reliability.
- Valid login credentials for reviewers when authentication is required.
Google states: “Google evaluates production apps for policy adherence, but review is not a troubleshooting step.” Do not submit expecting reviewers to diagnose compliance or explain how to fix the app.
Best Value
- CONNECTS TO ALL DEVICES - Inito’s latest model works with all iOS and Android devices, syncing wirelessly. It seamlessly fits it into your morning routine without the hassle of attaching a gadget to your phone.
- TRACKS ALL 4 KEY HORMONES IN 1 TEST - Inito measures actual values of estrogen, LH, PdG (urine metabolite of progesterone), and FSH on a single strip so you get a complete picture of your cycle from the comfort of your home. Our advanced Spectral Mapping Technology reads even the weakest signals for lab-grade precision.
- KNOW WHEN YOU’VE OVULATED, DON’T JUST PREDICT IT - Inito confirms ovulation by tracking the rise in your PdG levels, while other tests only track LH and give you a ‘yes’ or ‘no’ result. Get your 6 most fertile days to maximize your chances of conception.
- DESIGNED FOR EVERY CYCLE - Whether you have PCOS, irregular cycles, anovulatory cycles or are trying after age 35, Inito gives you 100% personalized results with actual hormone values. These insights help you confidently find the lifestyle changes, such as diet, exercise, or supplements, that work best for your unique body.
- PRECISE INSIGHTS DRIVEN BY ACTUAL DATA - Every Inito kit comes with access to our free, easy-to-use app for iOS and Android. Receive AI-powered analysis built on the world’s largest fertility hormone dataset, with no monthly subscriptions – just real data, ready to share with your doctor.
How long does production-access review take?
Google says review usually takes seven days or less, but it can take longer. The account owner receives an email when the review is complete; the guidance does not promise a particular approval date.
Google may ask you to continue testing, including when fewer than 12 testers are opted in or tester engagement was insufficient. Approval opens the Production page and access to open testing. The stated tester minimum by itself does not guarantee approval.
How do internal, closed, open, and production tracks differ?
These tracks serve different purposes in the release process; for accounts subject to the prerequisite, the required step is closed testing.
| Track | Purpose and access |
|---|---|
| Internal testing | An optional, fast early test. |
| Closed testing | A controlled test; required for eligible newer personal accounts before applying for production access. |
| Open testing | Becomes available after production access. |
| Production | Makes the app available to users. |
For operational details on setting up a track, inviting testers, and sharing access, see Google’s testing-track instructions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
