---
title: "Do Closed Testers Need to Open the App Every Day?"
description: "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."
image: "https://www.12testers14day.com/images/blog/blog-tester-daily-activity.webp"
---

1. [Home](/)
2. /[Blog](/blog)
3. /Do Closed Testers Need to Open the App Every Day?

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.

Sundar•Published November 17, 2026•Updated November 17, 2026

**4 min**estimated read

**5**guide sections

**1**references

![Illustration of Android testers completing useful app sessions, reporting issues, and confirming fixes across a continuous testing window](/images/blog/blog-tester-daily-activity.webp)

On this page

1. [01Two different things: counting and engagement](#section-2-two-different-things-counting-and-engagement)
2. [02A realistic engagement plan](#section-3-a-realistic-engagement-plan)
3. [03What counts as useful activity](#section-4-what-counts-as-useful-activity)
4. [04Avoid shortcuts](#section-5-avoid-shortcuts)
5. [05What to put in your tester brief](#section-6-what-to-put-in-your-tester-brief)
6. [06Frequently asked questions](#frequently-asked-questions)
7. [07Official sources](#official-sources)
0% read

On this page · 7 sections
1. [01Two different things: counting and engagement](#section-2-two-different-things-counting-and-engagement)
2. [02A realistic engagement plan](#section-3-a-realistic-engagement-plan)
3. [03What counts as useful activity](#section-4-what-counts-as-useful-activity)
4. [04Avoid shortcuts](#section-5-avoid-shortcuts)
5. [05What to put in your tester brief](#section-6-what-to-put-in-your-tester-brief)
6. [06Frequently asked questions](#frequently-asked-questions)
7. [07Official sources](#official-sources)

[Open the free toolsCheck your closed test setup with the free tools before you change anything.](/tools)

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](https://support.google.com/googleplay/android-developer/answer/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

1. Write a short tester brief. Explain what the app does and the two or three things you want people to try.
2. 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.
3. Ask for feedback in one place, such as a form or a single email address, so you can keep a dated record.
4. Ship an update during the test if feedback points to a real problem, and tell testers what changed.
5. Send a short reminder in the middle of the test so people keep the app installed and stay in.
6. 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](https://support.google.com/googleplay/android-developer/answer/14151465) (Google Play Console Help)

Continue

## Choose the next step

[How a closed test worksThe rule, the steps, and what to check along the way.](/how-it-works)[Free closed testing toolsPlan your 14-day window and prepare your production access notes.](/tools)[All closed testing guidesMore fixes for stuck or confusing closed tests.](/blog)

Related

## Next pages to read

[The 12 testers, 14 days requirementThe full rule, who it covers and how to apply.](/blog/12-testers-14-days-requirement)[How to write the production access questionnaire answersTurn tester activity into clear answers.](/blog/answering-production-access-questions)[Testers dropped out of my closed testKeep testers in for the full window.](/blog/closed-test-testers-left-what-now)

## 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.

[See plans and prices](/pricing)[Open the free tools](/tools)

```json
{"@context":"https://schema.org","@type":"Article","headline":"Do Closed Testers Need to Open the App Every Day?","description":"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.","image":["https://www.12testers14day.com/images/blog/blog-tester-daily-activity.webp","https://www.12testers14day.com/opengraph-image"],"url":"https://www.12testers14day.com/blog/how-often-closed-testers-should-open-app","mainEntityOfPage":"https://www.12testers14day.com/blog/how-often-closed-testers-should-open-app","datePublished":"2026-11-17T00:00:00.000Z","dateModified":"2026-11-17T00:00:00.000Z","articleSection":"Requirements","keywords":["do testers need to use app daily","closed testing daily usage","google play tester engagement"],"citation":[{"@type":"WebPage","name":"App testing requirements for new personal developer accounts","url":"https://support.google.com/googleplay/android-developer/answer/14151465","publisher":{"@type":"Organization","name":"Google Play Console Help"}}],"inLanguage":"en","author":{"@type":"Person","name":"Sundar","url":"https://www.12testers14day.com/about"},"publisher":{"@type":"Organization","name":"12 Testers 14 Days","url":"https://www.12testers14day.com/","logo":{"@type":"ImageObject","url":"https://www.12testers14day.com/brand-mark.svg"}},"isPartOf":{"@type":"WebSite","name":"12 Testers 14 Days","url":"https://www.12testers14day.com/","description":"Managed Google Play closed testing with 14 testers for 16 days, plus free guides and tools for fixing a stuck or confusing closed test."}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.12testers14day.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.12testers14day.com/blog"},{"@type":"ListItem","position":3,"name":"Do Closed Testers Need to Open the App Every Day?","item":"https://www.12testers14day.com/blog/how-often-closed-testers-should-open-app"}],"name":"12 Testers 14 Days breadcrumbs"}
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Will Google deny access if testers did not open the app daily?","acceptedAnswer":{"@type":"Answer","text":"Google does not state a daily-open rule. Focus on real use and a clear record of feedback instead."}},{"@type":"Question","name":"Do testers have to keep the app installed?","acceptedAnswer":{"@type":"Answer","text":"The rule is about staying opted in. Keeping the app installed makes it much more likely they will actually use it and send feedback."}},{"@type":"Question","name":"How much feedback is enough?","acceptedAnswer":{"@type":"Answer","text":"Google does not set a number. Aim for specific feedback you can describe, and at least one change you made because of it."}}]}
```
