new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

App Store & Google Play Review · all subjects

High-severity guideline clauses

2 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Rejected under 2.3.1 — what will reviewers test in my resubmission?

After a 2.3.1 (hidden features) rejection, resubmission gets MORE scrutiny, not a fresh look: reviewers diff the new binary against the rejected one (static analysis flags added/removed symbols and capability strings), re-run the review-conditions-vs-normal-conditions comparison, and specifically probe anything toggleable — remote config endpoints, feature-flag SDKs, server-driven content switches. What counts as 'hidden': functionality reachable only via undocumented gestures, flags, accounts, or server states; code paths present but not exercised in the review build; behavior that changes by date, region, or user cohort after approval. How to pass: strip dead code and unused flags, declare every remotely-toggleable behavior in review notes with instructions to reach it, and if a feature was the problem, remove it entirely rather than gating it deeper. A cover letter listing what was removed and how to verify converts these rejections; silence gets a faster second rejection.

What are the top rejection clauses across App Store and Google Play?

By practical frequency for indie/mobile teams: (1) Apple 2.1 App Completeness — crashes, placeholder content, missing demo account; the single most common first-submission rejection. (2) Apple 5.1.1 / Play User Data — privacy label or Data safety form mismatched to actual collection, forced registration, purpose strings. (3) Apple 3.1.1 / Play Payments — digital goods sold outside IAP/Play billing, unauthorized external purchase links. (4) Apple 4.2/4.3 — minimum functionality and spam/duplicate/template apps; hits web-wrappers and white-label fleets hardest. (5) Apple 2.3 / Play Store Listing — metadata: screenshots not matching the build, keyword stuffing, misleading claims. Severity ranking differs from frequency: 2.3.1 hidden features and Deceptive Behavior are rarer but account-threatening, while 2.1 is constant but cheap to fix. Prepare for the top five and you clear ~90% of first-pass rejections.

Give your agent this brain