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

Reviewer testing behaviour

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

What can Apple reviewers actually see and test — and what's invisible to them?

They test on real current devices with a 5–15 minute session: fresh install, every visible button, account creation with their own test emails, IAP purchase flows in the sandbox environment, permission prompts, and airplane-mode behavior. They see the client completely — UI, network calls from the device (including your analytics beacons), crash logs on their device. They do NOT see: your backend, your logs, your database, other users' data, or anything behind your server — which is why a backend that's down during review becomes a 2.1 rejection they cannot distinguish from a broken app. Practical consequences: your review-notes demo account must work from THEIR network (no IP allowlists); server-side flags they can't see must be declared; analytics must match the privacy label because the traffic is visible; and if a feature needs specific hardware, location, or a second user, put a video or demo mode in review notes — they cannot and will not arrange it.

Give your agent this brain