10 yes/no questions covering the actual Play Console gates that block first-time Android publishes in 2026. The 12-tester / 14-day rule, Data Safety form, content rating, target API level — the boring stuff that costs you a week if you miss it.
Built by 9jatesters because we kept fielding the same emails. We don't collect your answers; everything runs in your browser. Email yourself the results at the end if you want to share with your team.
Progress
0 of 10 answered
Gaps so far
0
Google Play now requires personal-developer-account apps to keep 12+ testers active in a closed-test track for 14 straight days before you can publish to production. The clock resets if testers drop off.
Google's official docThe 14-day rule only applies to the Closed Testing track. Internal testing doesn't count. If you have testers on the Internal track, you'll need to move them.
Google's official docRequired for every app, regardless of permissions. The URL must be reachable, must mention your app by name, and must explain how personal data is collected and used.
Google's official docA standalone form from the Privacy Policy. You declare each data type, whether it's collected/shared, why, and whether it's encrypted in transit. Mismatch between this form and your actual code = rejected app.
Google's official docAbout 15 yes/no questions about violence, sexual content, drugs, gambling, controlled substances. Returns IARC ratings across regions. Required before first publish.
Google's official docPlay's rolling API-level requirement bars new apps and updates that target older API levels. Behind by a year? Won't accept your submission. Behind by two years? Existing app stops getting new installs.
Google's official docA standalone declaration. If you have ads (mediated or direct), you must say so. If you don't, you must say so. False declarations = takedown + dev-account warning.
Google's official docReviewers can't review what they can't open. If your app gates first-screen behind a login, you must provide a test username + password in Play Console → App content → App access, or your review will fail before the policy team sees the actual app.
Google's official docRequired asset set: 512×512 hi-res icon, 1024×500 feature graphic, at least 2 phone screenshots, short description (80 chars), full description, app category, contact email. Missing any of these = listing won't submit.
Google's official docThe package name (com.yourcompany.yourapp) is the immutable primary key for your app on Google Play. Change it after submission and it becomes a different app — no upgrade path for existing testers. Common rookie mistake.
Google's official docGoogle announced the change in November 2023, and rolled it out to all new personal-developer accounts in 2024. The official reason: too many low-quality apps shipped straight to production without real-world validation, hurting search relevance and increasing post-launch removal rates. The unofficial reason: it shifted developer accountability earlier in the funnel.
The hard part for solo founders and small teams is the 14-day consecutive requirement. Testers have to install the app, keep it installed, and open it at least once every day. If you can't field 12 reliable testers from your personal network, you're stuck — which is why a marketplace of bank-account-verified Nigerian Gmail accounts exists.
None of this matters for organisation accounts — only personal developer accounts hit the 14-day gate. If you registered as an LLC / Ltd / Limited from day one, you can skip the closed-test requirement entirely (but you'll still need every other check above).