Vibe coding, the practice of describing an app in plain English and letting Claude or ChatGPT generate working code, has hit the App Store like a flood. New app releases reached roughly 560,000 in the first half of 2026, double prior levels in some metrics. The Next Web reported an 84% jump in submissions in one quarter alone. At WWDC, Apple acknowledged over 1,000 apps submitted every single hour.
That volume is breaking the review process. And Apple is not backing down from the rules that govern it.
The rule Apple keeps enforcing
App Store Guideline 2.5.2 prohibits apps from downloading, installing, or executing code that alters core features. The stated reason is security: Apple wants to stop untested software from reaching user devices. That position has not shifted despite the pressure.
The practical effect is that AI coding companions often trigger rejections. Preview features that let users test generated apps look like unauthorized code execution to reviewers. Replit and an app called “Anything” both faced removals. The Information described an escalating crackdown. Developers told reporters they feel like they’re operating in the dark, with apps approved one day and blocked the next.

What the volume problem actually looks like
Human reviewers cannot keep pace. Automation helps, but only so much. The signal-to-noise ratio inside the store is degrading as low-effort copies multiply and discovery suffers. Apple requires every title to add distinct value, but enforcing that standard at this scale is a different problem than writing the rule.
A 9to5Mac piece from June outlined possible structural fixes beyond stricter enforcement: expand TestFlight beyond its current 10,000-tester cap, add a discovery tab inside the beta tool, and create a sandboxed tier for experimental apps that can reach an audience without full App Store scrutiny.
The operator angle
If you’re an indie builder using vibe coding tools to ship iOS apps, you’re operating in genuinely uncertain territory right now. The same app can clear review one week and get pulled the next. Builders who’ve hit walls are pivoting: wrapping web apps in native shells, targeting macOS or visionOS where the rules differ slightly, or focusing on categories less likely to trigger the code execution flag.
The longer-term question for the ecosystem is whether Apple adapts its review infrastructure fast enough to capture the creativity surge, or whether frustrated builders migrate toward Android or the web. That decision is still unresolved.
