Testers do not need to live in your app for hours. Google cares that opted-in testers actually use the product across 14 continuous days — meaningful short sessions beat idle marathon time.
Session Duration Guidelines
There is no published “X minutes per day” quota. Aim for sessions long enough to exercise core features, repeated across the window.
Minimum expectations
- At least one intentional open on most days for most testers
- Long enough to tap through a real flow (often a few minutes)
- Avoid open-and-instant-close as the only behavior
Quality over quantity
- Five focused minutes > thirty idle seconds
- Feature interaction > clock time
- Consistency across 14 days > one long day-1 session
Personal accounts after Nov 13, 2023 still need ≥12 continuous opt-ins for 14 days. Organization / D-U-N-S accounts are exempt from that gate. Google previously required 20 testers; the minimum is now 12.
What Google Likely Looks For
Meaningful sessions
- Opens with interaction
- Navigation beyond the first screen
- Usage that matches what you claim in the production-access form
Consistency
- Activity through the full closed window
- Not only a spike when you begged everyone on day 1
Console: Test and release → Testing → Closed testing.
Factors Affecting Session Length
App type
- Games: longer sessions are natural
- Utilities: short, frequent opens are normal
- Content apps: varies with content depth
Human reality
- Some days will be shorter
- Natural variance is fine; total silence is not
Recommendations for Developers
Set realistic expectations
Tell testers: “Open daily, try these 3 flows, stay opted in 14 days.” Do not demand hour-long chores.
Track what matters
Verify opens and return visits — not just opt-in count.
Keep testers engaged
Automated reminders (Closed Test Pro or your own push/email) keep short daily sessions happening without spammy manual nagging.