Apple Removes Anything App from App Store: What Developers Need to Know

Apple pulled the vibe coding platform Anything from the App Store on March 26, citing Guideline 2.5.2, the rule barring apps from executing code that modifies their features or behavior after review. The move goes further than the update blocks Apple had already imposed on Replit and Vibecode earlier this month, making Anything the first such removal reported so far in this category, according to Techzine and MacRumors.

Apple is not objecting to AI-assisted app creation as a practice. The distinction is simpler than that: Apple blocks apps that generate code and then execute or render that output inside the native iOS environment, producing behavior that was never part of what Apple reviewed. That's the line Anything crossed. But here's what makes the Anything case more than a clean enforcement story: the app tried the compliance fix Apple had reportedly suggested to other blocked developers, submitted the update, and got removed anyway. Apple has not explained why.

For anyone building AI coding tools for iOS, the category is still open. The question is how much of your current architecture survives the constraints Apple is now enforcing.

Why Apple removes Anything app from App Store: the rule it's enforcing

Guideline 2.5.2 predates AI-assisted development by years. It requires apps to be self-contained within their bundles and prohibits them from downloading, installing, or executing code that introduces or changes features after the point of review, as confirmed by 9to5Mac and GIGAZINE. The app Apple approves at submission must be the app users get. Full stop.

Apple also cited section 3.3.1(B) of the Developer Program License, which allows interpreted code to be downloaded into an app only if it does not alter the application's primary purpose by providing features inconsistent with what Apple evaluated at review, per 9to5Mac.

There is one narrow carve-out. Educational apps built specifically to teach coding may download and execute code, but only under strict conditions: users must be able to view and edit the full source code within the app, and that code cannot be used for any other purpose, according to MacRumors and 9to5Mac. General-purpose vibe coding platforms don't qualify.

Think of it this way: Apple will allow an app to function as a drafting desk, helping users write and export code to be built and run elsewhere. What it won't allow is an app that acts as a mini runtime, executing generated code on-device and effectively becoming a different, unreviewed piece of software after approval. That is the specific behavior Guideline 2.5.2 is designed to prevent.

What Apple has not explained is why Anything got removed while comparable App Store vibe coding apps remain live. The rules Apple cited are consistent. The application of those rules is not, at least not publicly.

What Anything did, what it tried to fix, and why Apple pulled it anyway

Anything launched on iOS in November without incident. Co-founder Dhruv Amin says the platform was used to publish thousands of apps through the App Store, and the company had raised $11 million at a $100 million valuation in September, per MacRumors. Apple began blocking the app's updates in December, four months before the outright removal.

When The Information's coverage of broader App Store code execution enforcement surfaced earlier this month, Amin moved toward compliance. He submitted an update that would redirect app previews to an external web browser rather than rendering them inside Anything on-device, aimed at addressing the behavior Apple and reviewers had flagged, according to 9to5Mac.

Apple rejected the update. Then removed the existing version from the store.

That sequence is the live reporting angle here. According to secondary reporting, Apple had told Replit and Vibecode that reinstatement was possible if they redirected previews to an external browser or removed the ability to generate Apple-platform-specific software, per a Yahoo Finance-syndicated report. Anything tried the first of those remedies precisely. It was removed regardless, and Apple has not responded to requests for comment on why, per GIGAZINE.

Vercel's v0, which offers related capabilities, was not subject to the same enforcement action, per developer commentator Michael Tsai citing The Information. Both Techzine and 9to5Mac note that other comparable tools remain on the store. Apple hasn't drawn a public line between what it accepted in those cases and what it rejected in Anything.

What this means for App Store vibe coding apps: a practical read

Developer observers have identified a useful distinction: vibe-coding apps, tools that help users generate software, versus vibe-coded apps, software that was built using AI. Apple's enforcement targets the former, specifically when they execute generated code within the native iOS environment. It is not, based on current evidence, a crackdown on the flood of AI-generated apps themselves, as Michael Tsai noted. Apple blocks apps that generate code and run it on-device; it continues to approve apps that AI helped build.

Based on available reporting, here is what the compliance picture looks like:

• Likely viable: Apps that help users write, generate, or export code where execution and preview happen outside the iOS app, in a browser, on a server, or through another platform.
• High risk: Apps that generate working software and render or run the output inside the native iOS app without routing it through external environments first. This is the behavior Apple's App Store code execution rules are squarely targeting.
• Conditional path: Redirecting previews to a web browser and removing Apple-platform-specific app generation appear to be the changes Apple indicated could unblock Replit and Vibecode, per Yahoo Finance. That path didn't save Anything, but it hasn't been explicitly ruled out for others.
• Genuinely uncertain: Why apps with comparable technical architectures remain live. Vercel's v0 is the clearest example. No public explanation covers the gap between what Apple accepted there and what it rejected in Anything.

The backdrop makes this harder to navigate, not easier. US iOS app submissions grew 54.8% year-over-year in January 2026, the fastest rate in four years, per Sensor Tower data cited by Business Insider. Apple says it processed more than 200,000 submissions per week over the last 12 weeks, with 90% reviewed within 48 hours. Some developers report waits of weeks regardless. Forrester analyst Dipanjan Chatterjee put the structural problem plainly: "This is not a problem Apple can reject its way out of; as AI accelerates app creation, the company will have to evolve from artisanal gatekeeping to curation at scale," per Business Insider. Removing Anything enforces a real rule. It does nothing to answer that larger question.

What developers should take away

Developers should read this episode in three parts.

First, Apple's enforcement has escalated from blocking updates to removing apps entirely. Anything was a funded, established product with active users and a nine-figure valuation. None of that protected it, per MacRumors.

Second, this is not a ban on vibe coding as a practice or on the apps it produces. Based on available evidence, Apple blocks apps that execute or render AI-generated code inside the native iOS environment. That is a workflow distinction with real product design implications, and it's narrower than the headlines suggest.

Third, and most practically: precedent is being set through enforcement actions, not published guidance. Apple hasn't issued a policy memo or a compliance checklist, and hasn't explained why some apps with similar architectures remain untouched while others get pulled. Developers building in this space are navigating based on what Apple has done, not what it has said. The Anything removal shows those two things can diverge in ways that even a good-faith compliance attempt won't necessarily fix.