Requirements
Do Closed Testers Need to Open the App Every Day?
Google's closed testing rule counts opted-in testers, not daily opens. Real use still helps your production access application. Here is what to aim for.

On this page · 7 sections
No, Google's written rule does not say closed testers must open your app every day. The requirement is at least 12 testers opted in to a closed test for the last 14 days continuously. This applies to personal Play developer accounts created after 13 November 2023; organization accounts are exempt (Play Console Help 14151465). But when you apply for production access, you describe your closed test in Play Console. So regular, real use across the test makes your application much easier to support, even if daily opens are not a stated rule.
Two different things: counting and engagement
The count is mechanical. Play Console checks whether enough testers stayed opted in for long enough. That is what the dashboard progress shows.
Engagement is what you describe in your application. If testers opted in and never opened the app, you have little to say about how the test went, what testers told you, or what you changed.
A realistic engagement plan
- Write a short tester brief. Explain what the app does and the two or three things you want people to try.
- Spread tasks across the test. Day 1: install and sign up. Later in the first week: use the main feature. Second week: try settings, edge cases, and anything you changed.
- Ask for feedback in one place, such as a form or a single email address, so you can keep a dated record.
- Ship an update during the test if feedback points to a real problem, and tell testers what changed.
- Send a short reminder in the middle of the test so people keep the app installed and stay in.
- Keep a log of what testers did and said. You will use it for your questionnaire answers.
What counts as useful activity
Useful activity is anything that tells you something about your app: completing a sign-up, using the main feature, finding a crash, saying a screen is confusing, or asking for a missing option. A tester who opens the app once a day for a few seconds tells you very little.
Quality beats a daily habit. A tester who uses the app properly a few times and writes two clear notes is worth more to your application than one who opens it daily and says nothing.
Avoid shortcuts
Scripts or bots that open the app automatically do not produce feedback and do not help you answer Google's questions honestly. They also risk breaking Google Play policies. Real people using the app is the point of the test.
What to put in your tester brief
Keep the brief short enough to read on a phone. Include what the app is for, the account or login to use, the main task to try first, and how to report a problem. Add a line asking testers to keep the app installed and stay in the test until the end date.
If you update the app during the test, send a two-line note saying what changed and what to try again. That gives testers a reason to come back, and gives you feedback on the fix.
FAQ
Questions about this topic
Will Google deny access if testers did not open the app daily?
Google does not state a daily-open rule. Focus on real use and a clear record of feedback instead.
Do testers have to keep the app installed?
The rule is about staying opted in. Keeping the app installed makes it much more likely they will actually use it and send feedback.
How much feedback is enough?
Google does not set a number. Aim for specific feedback you can describe, and at least one change you made because of it.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Rather not recruit testers yourself?
Our managed closed test runs 14 testers for 16 days. Google requires 12 testers for 14 days (for personal Play developer accounts created after 13 November 2023; organization accounts are exempt); the extra 2 testers and 2 days are our buffer.