Yes. Your testers should open the app every day.
Across more than 50,000 apps tested, that one habit is the clearest difference we see between a closed test that gets approved and one that does not.
Google’s written rule is narrower. It asks only that 12 testers stay opted in for 14 continuous days [1]. That is the floor you have to clear to apply. It is not the standard that gets you approved.
Most rejections happen in the gap between those two things. Our own numbers put it bluntly: 92.5% of the rejected apps that come to us failed because their testers were inactive.
What does Google actually require?
One sentence, and it pays to read it closely. At least 12 testers must be opted in when you apply, and they must have been opted in continuously for the previous 14 days [1].
Look at what that measures. It measures opt-in status. It does not measure sessions.
Google publishes no minimum number of opens. No session length. No activity threshold. Its guidance simply asks you to encourage testers to use as many features as possible [1].
So developers read the rule, decide that activity does not matter, and run a test where twelve people install the app and never touch it again. That test meets the letter of the rule. It still fails.
Why do inactive testers get apps rejected?
Because clearing the rule is not the same as passing the review.
Fourteen days lets you apply. What you submit next is an application, and Google asks you three things [1]:
- Summarise the feedback you received from testers, and say how you collected it.
- Describe the changes you made based on what the closed test taught you.
- Explain how you decided the app was ready for production.
Every one of those answers depends on somebody actually using your app.
Twelve silent installs give you nothing to summarise. No changes to point at. No evidence of readiness beyond the fact that two weeks went by. Reviewers see an application built on nothing, because that is what it is.
This is why daily opens matter even though Google never asks for them. They are not there to satisfy a counter. They produce the material your application is made of.
What 50,000 apps taught us about this
We see this from an unusual angle.
Many of the developers who come to us arrive after a rejection. They ran the test themselves first, usually with friends and family. We ask every one of them what went wrong, and we have been collecting those answers since the policy began.
Across more than 50,000 apps tested, 92.5% of those rejections traced back to inactive testers. Not the wrong number of testers. Not paperwork. People who installed the app, opted in, then forgot about it for two weeks.
The story is nearly always the same.
A developer asks twelve friends and relatives. Everyone agrees. Everyone installs. Play Console shows twelve names, so the developer assumes the job is done.
The testers were doing a favour, not testing a product. They never open it again. Fourteen days later the count still reads twelve, the application goes in, and it comes back refused.
That is a finding from our own case records, not a Google statistic. Google does not publish rejection reasons. What we can tell you is what developers tell us when they arrive, and inactive testers dominate it.
| Statement | Status | Source |
|---|---|---|
| 12 testers opted in for 14 continuous days | Required to apply | Published by Google |
| You must describe feedback, changes and readiness | Required to be approved | Published by Google |
| Testers should use as many features as possible | Encouraged | Published by Google |
| Testers should open the app every day | Strongly recommended | Testers Community data |
| A daily usage number Google checks | Does not exist | No published source |
How often should testers open the app?
Every day, for all 14 days. That is what we hold our own testers to, and what we tell developers running the test themselves.
Aim at daily rather than occasional, because you need the margin.
Ask for daily and you get most days. Ask for every two or three days and you get a handful of opens in week one, then silence in week two. That is the pattern that produces an empty application.
Aim high, so ordinary forgetfulness still lands you somewhere useful.
Depth matters as much as frequency. A tester who moves through real screens and hits a real problem gives you a sentence you can put on the form. A tester who opens the app for four seconds gives you a number and nothing else.
So ask for both. Open it daily, and use it properly a few times across the fortnight.
This is why the free Pack of 16 works the way it does. Sixteen developers open every app in their pack daily for 16 days and leave feedback. That is stricter than Google’s rule on purpose, because the rule was never the thing that got anyone approved.
Why does friends and family testing fail so often?
Not because the people are unwilling. Because the ask is wrong.
You asked for a favour, so they did you a favour. They installed it.
What you needed was two weeks of daily use and honest feedback about a product they have no reason to care about. Those are very different requests. The second one is a real commitment from someone helping out of goodwill.
If you go this route, say what it involves before they agree. Fourteen days. Open it daily. Tell you when something breaks.
Most people will still say yes. The ones who say no have saved you a rejection.
Does a missed day reset my 14 days?
No. The timer runs on opt-in status, so it keeps going through weekends, holidays and quiet stretches. A tester who misses a Tuesday has broken nothing.
Two things do interrupt it. A tester clicking Opt out ends their continuous period. Dropping below 12 opted-in testers means you no longer meet the requirement when you apply.
Uninstalling does neither. An uninstall leaves the tester opted in and the clock running.
So a missed day costs you nothing on the timer. It costs you a day of the feedback your application is built from, which is the part that decides the outcome.
Frequently asked questions
Do Google Play testers need to open the app every day?
They should. Google’s rule only requires 12 testers opted in for 14 continuous days, with no daily usage threshold. In practice, 92.5% of the rejected apps that come to us failed because testers were inactive.
Will my app be rejected if testers do not open it?
It is the most common reason we see. Inactive testers leave you unable to answer the questions about feedback, changes and readiness. An application built on nothing is what gets refused.
Does a single missed day break the 14 day streak?
No. Only opting out breaks it. A missed day costs you feedback, not time on the clock.
How many times a day should a tester open the app?
Once a day is the target, used properly rather than opened and closed. Depth matters as much as frequency, because a tester who hits a real problem gives you something to write on the form.
Why does testing with friends and family get rejected so often?
Because installing is a favour and testing daily for two weeks is a commitment. Most friends do the first and not the second. That leaves you with twelve opted-in testers and no feedback.
Is it better to have 12 active testers or 20 quiet ones?
Twelve active testers. Extra testers protect you if someone opts out, but they do not improve the answers you give on the form.
Does Google publish a required number of daily opens?
No. Google publishes no engagement threshold at all. The daily recommendation comes from our own case data, not from Google documentation.
If you want testers who actually open the app
Option 1: verified testers assigned to you
- Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
- Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers assigned within 6 hours, so your 14 days start today rather than after a week of asking.
- They open your app daily and stay active for the full period.
- Anyone who goes inactive is replaced.
- A feedback report at the end, plus pre-filled answers for the 10 production access questions.
- 100% production access or your money back.
More than 10,000 apps have reached production this way. Submit your app to start.
Option 2: join a free Pack of 16
If you would rather trade time than money, the Testers Community app puts you in a pack of 16 developers. Everyone tests each other’s apps for 16 days, opening every app daily and leaving feedback. Inactive members get replaced.
Either way, read the full requirements before you start. If your testers have already gone quiet, our guide to fixing inactive testers covers the recovery. It is also worth knowing that an uninstall does not stop the clock, and neither does shipping an update.
Sources
- Google Play Console Help: App testing requirements for new personal developer accounts
- Google Play Console Help: Set up an open, closed, or internal test
- Testers Community internal case data. Drawn from developers who applied for production access on their own, were refused, and then ran their closed test with us. Google does not publish rejection reasons.
