Updates to Vibe Coding Apps Rejected From the App Store
Apple has quietly blocked AI “vibe coding” apps, such as Replit and Vibecode, from releasing App Store updates unless they make changes, The Information reports.
[…]
Apple told The Information that certain vibe coding features breach long-standing App Store rules prohibiting apps from executing code that alters their own functionality or that of other apps.
[…]
An Apple spokesperson said the policy is not targeted specifically at vibe coding apps.
If the apps are in breach of longstanding rules, why is it the updates that are blocked? It seems like either Apple should have rejected the apps long ago or else they’re trying to retcon the new policy, which remains unclear to me.
Report sources say that the apps in question are close to being approved for the App Store again, but after agreeing to make changes to the way they function. These changes include updating previews of the vibe-coded apps, or removing functions like making apps specifically for Apple devices.
That sounds like removing the core functionality.
The report adds that there are other apps that exist in the App Store that didn’t get the same limitation, such as Vercel’s v0. Other apps that offer similar capabilities that aren’t coding-specific, such as design app Canva, could potentially be hit by the same issues, since they can be used to create filters, quizzes, and other items using AI.
For the most part, the report focuses on the issue being one of competition and revenue protection. Apple could lose revenue due to these vibe coding apps creating software that doesn't pass through the App Store itself.
Previously:
- Mac App Store Review Times Increasing
- Bitrig for iOS Early Access
- Study on AI Coding Tools
- Tim, Don’t Kill My Vibe
- Vibe Coding
- iDOS Emulator to Be Removed From the App Store
- Executable Code in Educational Apps
- Pythonista in App Store Peril
- Editorial 1.1.1 Rejected From the App Store
- Briefs Rejected From the App Store, Again
- App Store Changes
Update (2026-04-01): Juli Clover (Hacker News):
Apple has removed a “vibe coding” app from its App Store, reports The Information. AI app building app “Anything” was pulled from the App Store , and Anything co-founder Dhruv Amin was told that his app violated Guideline 2.5.2.
[…]
“Anything” launched on iOS back in November with no issue, and Amin says the tool has been used to publish thousands of apps in the App Store . The app let users create and preview vibe code apps on the iPhone, and it raised $11 million at a valuation of $100 million back in September.
While Anything was removed from the App Store on March 26, Apple has been blocking updates to the app since December. Amin submitted an update that would allow vibe coded apps to be previewed in a web browser instead of in the app to attempt to comply with the 2.5.2 rule, but Apple blocked the update and pulled the app.
6 Comments RSS · Twitter · Mastodon
This absolutely sucks for iPhone users because making small personal programs you can run on your own device to solve your own problems is the best use case for vibecoding and is immensely powerful.
Apple is hamstringing its own users to protect its App Store revenue, because it's better off if you buy some shitty subscription app rather than make a dedicated app for yourself.
Perhaps this explains the 25% increase in app submissions resulting in reviews now taking 3-5 days, compared to the previous 24-48 hours. I say good riddance.
"Perhaps this explains the 25% increase in app submissions resulting in reviews now taking 3-5 days, compared to the previous 24-48 hours"
This is about rejecting a small number of vibecod*ing* apps, not a large number of vibecod*ed* apps.
@Plume I thought the implication was that the vibe coding apps were being used to make the vibecoded apps that get submitted.
The apps are still being made, though. Just not inside an app on iOS. You can even still use things like Lovable on iOS, just inside the web app instead of the native app.
"Amin submitted an update that would allow vibe coded apps to be previewed in a web browser instead"
So what exactly was Apple's complaint after that?
