Google doesn't officially state that closed testers must keep your app installed for the whole 14 days. The written rule is about testers being opted in continuously. But Google can ask you to keep testing because of "insufficient tester engagement during the testing period", so keeping the app installed and using it regularly is strongly advised.
This article separates what Google says from what developers report, and gives you practical instructions to send your testers.
What Google's rule actually says
The requirement for personal developer accounts created after November 13, 2023 is to "run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days" (App testing requirements).
Notice the wording: opted in, not installed. A tester opts in by opening your opt-in link and accepting. Google's testing setup page says "Each tester needs to opt in using the link" (Set up a test). Whether installing the app is part of being "opted in" isn't documented anywhere official.
So, strictly by the published text, the 14-day count is about staying in the testing program. Our article on what counts as an opted-in tester covers that definition with examples.
Why installs still matter
The same official page lists the reasons Google may ask you to continue testing: "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period."
Engagement is hard to show if the app isn't on anyone's phone. The production access form also asks about it directly: whether testers used all of your features, and whether their usage matched what you expect in production.
Developers who received a "more testing required" result have also reported what the email said. According to a Product Expert community guide, it mentions testers who "did not have your app installed on their device, did not actively test the app daily or were left out of the testing program during these 14 days." That is a community report of a real email, not a published Google rule, but it points in one direction: installs and actual use are likely part of how engagement is judged.
Opting out and uninstalling are different things
These two actions are easy to confuse:
- Opting out means leaving the testing program. Google is clear that testers who opt out before 14 days "do not count toward the requirement", and if they rejoin, "the 14 days must be consecutive to count".
- Uninstalling removes the app from the phone. The tester may still be opted in.
Only opting out is clearly defined as breaking the count. Uninstalling isn't defined either way, which is exactly why it's risky. You can't prove engagement from someone who removed the app on day 3.
What testers should do, day by day
Send your testers short, specific instructions before day 1. Something like this:
- Open the opt-in link with the Google account I added to the test, and accept.
- Install the app from the Google Play page the link opens.
- Keep it installed until I confirm I've applied for production access.
- Open it regularly and try the features I list each week.
- Accept updates when they arrive.
- Don't leave the testing program, even if you stop using the app for a few days.
- Tell me if you change or reset your phone, so you can reinstall.
Google doesn't publish a minimum number of sessions, so don't promise testers that "once a day" is a rule. It's a sensible habit, not an official threshold.
Situations that come up during 14 days
A tester needs storage space and uninstalls. Ask them to reinstall from the same Google Play page as soon as they can. As long as they didn't opt out, their opt-in streak isn't described as broken by the uninstall. The gap in usage is the weak point.
A tester gets a new phone. They should sign in with the same Google account and install the app again. Testers opt in with their Google account, so they likely won't need to opt in a second time, but ask them to check that the Google Play page still shows them as a tester.
A tester's phone resets. Same as above. Make sure they use the Google account that is on your tester list, not a new one.
You ship an update. Testers receive it through Google Play like any other update. Tell them what changed so they have a reason to open the app again.
How to check from your side
You can't see each tester's phone, but you can see signals:
- Your closed track's tester information shows how many testers are opted in.
- Crash and usage data in your own analytics shows whether people are actually opening the app.
- Private feedback appears under Monitor and improve > Ratings and reviews > Testing feedback.
If usage drops to almost nothing in week two, assume engagement is at risk and act before you apply. Our closed testing timeline shows where the second week fits and when to apply.
Key takeaways
- Officially, the rule counts testers who are opted in continuously for 14 days.
- Google doesn't say installation is required, but it may require more testing for "insufficient tester engagement".
- Keeping the app installed and using it regularly is strongly advised for every tester.
- Opting out breaks the streak. Uninstalling isn't defined, but it weakens your engagement story.
- Keep testers installed and opted in until after you've applied.
When the 14 days are done, our production access guide shows how to describe tester engagement honestly in the form. GoPlayTester's testers keep your app installed and opted in for the full 14 days on real devices; you can order here. Google makes the final decision on every application.
