The vibe coding wave is, in some ways, truly exciting – and in others, a bit of a mess.
AI-powered tools like Replit and Vibecode now let people with little or no coding background generate a working app from a prompt in a matter of hours, with minimal hand-written code involved. The barrier to entry has collapsed, and for non-technical founders who’ve spent years being told they need a technical co-founder to build anything, that’s game-changing.
Apple is currently processing more than 200,000 submissions a week – more than at any point in the App Store’s history. The review team hasn’t scaled at the same rate, and review times that used to run under 48 hours are now stretching to several days for a growing number of developers. The likely cause isn’t a broken process. It’s the flood of AI-generated apps that vibe coding has made trivially easy to produce.
Apple has started blocking updates for some of the most popular vibe coding platforms, citing guidelines against apps that execute code to change their own functionality. The platform has a quality problem, which seemingly traces back to how low the barrier to entry has become.
The App Store Queue Is The Symptom, Not The Problem
The spread of vibe coding has been fast because the tools are good enough to produce things that look and function like apps, and because the cost of trying is now close to zero.
You don’t need to hire engineers or spend months learning Swift. You need a weekend and a willingness to iterate on prompts until something usable comes out. The problem is that everyone else has exactly the same tools, the same prompts and the same weekend.
Apple’s official position is that about 90% of submissions are still reviewed within 48 hours. What’s changed is the tail: Apple’s own data puts average review time at around one to one and a half days, but the outliers – submissions stuck for a week or more – are getting significantly more frequent in developer communities. The gap between Apple’s headline number and what developers are actually experiencing is, arguably, the most telling part of this story.
Apple is yet to confirm that vibe coding is the direct cause, but the timing lines up closely with the growth of these platforms, and blocking updates for the most prominent ones suggests the company is treating this as a policy issue rather than a throughput one.
According to Business Insider reporting, developers and analysts aren’t just worried about volume. They’re worried about the proportion of submissions that are near-identical prompt-generated variations on existing apps, which forces reviewers into judgement calls rather than quick passes and this compounds the slowdown.
For founders who’ve spent meaningful time building something differentiated, the slower queue is an irritant, but the deeper problem is discoverability. When the store is processing tens of thousands of submissions a week, many of them prompt-generated variations on the same basic utility app, standing out becomes considerably harder.
More from Tech
- Amazon Just Bought Its Second Robot Startup In A Week. Should Robotics Founders Be Excited Or Nervous?
- Global Tech Investments Went Up 10% – What Does This Mean For Startups?
- OpenAI Built The Future Of Video, Then Pulled The Plug. What Were They Thinking?
- Project Prometheus Is Jeff Bezos’s Most Ambitious Bet Yet – And It Has Nothing To Do With Amazon
- How Can Antivirus Software Guard Against Identity Theft?
- How SportsTech Startups Are Transforming Fitness
- Apple’s Loss Is Oura’s Gain: What Brian Lynch’s Move Tells Us About The Future Of Wearables
- Two-Thirds Of UK Tech Firms Are Outside London – Cost Crisis Or Regional Tech Boom?
Is A Lower Barrier To Entry Actually Good For Founders?
The catch with tools that make shipping trivially easy is that they make shipping trivially easy for everyone.
When the barrier drops to near zero, submission volume spikes, and the result isn’t just a slower review queue. It’s a more crowded market, lower average quality and a signal-to-noise problem that affects every founder trying to build something worth using.
The honest answer to whether that’s a good thing depends entirely on what you’re building and how much of your advantage was ever about the ability to ship code. If your edge was always the idea, the distribution or the understanding of a specific customer problem, vibe coding is a catalyst. Prototype faster, test assumptions more cheaply, get to a meaningful product without burning months of runway on engineering.
If your edge was execution speed and technical quality, the situation is more complicated. A recent study found that fewer than a third of UK firms report meaningful returns from AI tools, and a sizeable part of that gap is products built quickly but not built well. Vibe coding accelerates shipping, it doesn’t automatically accelerate the quality of thinking that goes into what gets shipped.
The founders who’ll do well in a world where anyone can generate an app over a weekend are the ones who understand that shipping was never really the hard part. Building something people want to keep using is, and no amount of AI-generated code changes that.
The Weekend App Is Easy, The Defence Around It Is Not
Vibe coding has democratised shipping in the same way Canva democratised design: it’s made the basic version of the thing accessible to everyone, which means the basic version is now worth considerably less.
The skills that still matter are the ones that can’t be prompted away: product judgement, user insight, distribution thinking and the ability to build something with enough depth that a weekend project can’t replicate it.
Apple’s review queue will sort itself out, either through scaled processes or tighter guidelines. The more durable question for founders is what it means to compete when the cost of a minimum viable product is now a few hours of prompting.
The answer is to be clear about where your actual advantage lies, and make sure vibe coding is accelerating that rather than substituting for it.