Negative App Store reviews involving iOS and OS X betas aren't fair to developers; Apple should filter or prevent them, and users should send feedback privately
Federico Viticci / MacStories :
Context & Ripple Effects
In mid-July 2015 Federico Viticci argued at MacStories that app reviews written while users run iOS and OS X betas unfairly punish developers whose apps break under unfinished system software — and asked Apple to filter such reviews out. The argument landed fast: within about two weeks, Apple blocked beta testers from posting App Store reviews altogether.
That quick fix sits early in a longer arc of Apple being pushed to make the storefront a managed feedback channel rather than a raw forum — a thread that runs through the later decision to let developers reply to reviews and through ongoing critiques of what the App Store's job actually is.
First-order effects
- Developers whose ratings cratered during each iOS and OS X beta cycle get immediate relief once Apple filters prerelease-OS reviews out of their averages.
- Apple has to build review-gating into the App Store pipeline itself, deciding at the OS level who may post public feedback.
Second-order effects
- Gating public reviews redirects bug reports toward private channels like Apple's own beta feedback tools, giving Apple more visibility into pre-release quality than developers have.
- Once Apple accepts responsibility for review fairness, pressure builds for richer review tooling — the mechanism that eventually produced developer responses to reviews in iOS 10.3.
Third-order effects
- If the pattern holds, the App Store consolidates into a curated quality layer where Apple controls not just distribution but the terms of public judgment — a stance critics later extended to arguments about whether the store's stated security role serves developers or Apple's gatekeeping.
The trend: The App Store is shifting from a passive review forum into an actively curated feedback channel, with Apple deciding what counts as legitimate public criticism.