Back to News
Market Impact: 0.6

Vibe coding drove an 84% jump in App Store submissions. Apple is cracking down.

AAPLTSLA
Artificial IntelligenceTechnology & InnovationRegulation & LegislationAntitrust & CompetitionPrivate Markets & VentureCompany Fundamentals
Vibe coding drove an 84% jump in App Store submissions. Apple is cracking down.

New app submissions to Apple’s App Store surged 84% in a single quarter as 'vibe coding' went mainstream, driving Apple approval times from ~24 hours to as long as 7–30+ days and totaling 557,000 new submissions in 2025. Apple has begun removing and blocking vibe-coding apps under Guideline 2.5.2 (no dynamic code execution), creating regulatory and business-model risk for the App Store while venture-backed platforms (Cursor: $2B annualised, $29.3B valuation after $2.3B round; Lovable: $200M annualised, $330M Series B at $6.6B; Replit: $240M 2025 revenue, targeting $1B in 2026) scale rapidly.

Analysis

The arrival of natural‑language→code tooling is not merely a developer productivity story; it rewrites the economics of distribution and inference. Faster, ad hoc software generation shifts demand away from large, infrequent releases toward continuous micro‑deployments, which in turn raises recurrent inference and runtime costs — I estimate this could add a mid‑single‑digit percentage to datacenter GPU inference demand over 12–24 months if adoption continues. That flow benefits hyperscalers and GPU vendors disproportionately while creating a new choke point at the platform gatekeeper layer. Apple faces three clear strategic paths with different cost and timing profiles: (1) scale human review (labor cost in the low‑hundreds of millions annually, slow by design), (2) invest in automated LLM‑assisted review and sanctioned runtime sandboxes (one‑time platform engineering spend likely in the low‑to‑mid hundreds of millions, deployable in 12–24 months), or (3) double down on enforcement and accept friction that redirects developer activity to alternative distribution routes. Each path has asymmetric business outcomes — automation/sandboxing preserves recurring commissions and creates a new product line Apple can monetize, while enforcement cedes developer mindshare and long‑term fee capture. Regulatory and competitive catalysts will determine near‑term direction: regulatory pressure that favors multi‑store access or mandates interoperability could accelerate diversion of developer flows to competitors, while reciprocal commercial deals between vibe‑tool vendors and platform owners could lock Apple into a monetizable compliance layer. The market is currently underpricing the optionality of a regulated, paid certification model that Apple could introduce within 6–18 months to reclaim value.