Apple Removes Anything as Vibe Coding Scrutiny Grows

Apple has removed Anything, a vibe coding app, from the App Store after rejecting an update that tried to move app previews into a browser. The move matters because Apple is drawing a line around how code gets created, previewed, and executed on iPhone and iPad.

The timing is telling. In early March, Apple already pushed back on apps like Replit and Vibecode, and now a separate app has been pulled entirely. This is less about vibe coding as a buzzword and more about Apple deciding what kinds of code-generating workflows are acceptable inside its store.

What Apple says the rules mean

Apple pointed to section 2.5.2 of its App Review Guidelines, which says apps must be self-contained and may not download, install, or execute code that changes app behavior. Apple also cited section 3.3.1(B) of the Apple Developer Program License Agreement, which limits downloaded interpreted code if it changes the app’s primary purpose.

That language sounds dry, but it has real consequences for AI coding tools. If an app can generate code and then run that code in ways Apple cannot inspect during review, Apple sees a risk. If the app keeps the code generation inside a tighter box, Apple is more likely to allow it.

• Apple says apps must stay inside their own bundles.
• Apple says code cannot be downloaded and used to change app features outside review.
• Educational code apps get narrow exceptions, but only when source code is fully visible and editable.
• The rule Apple cited, 2.5.2, is about code changing app behavior, not about AI branding.

That distinction matters. A lot of people hear “vibe coding” and think Apple is reacting to the style of product, but the company is reacting to execution paths. In Apple’s view, an app that helps you write code is one thing; an app that downloads and runs fresh code to alter itself is another.

Why Anything got pulled

According to The Information, The Information reported that Anything tried to ship an update that would show previews of vibe-coded apps in a web browser instead of inside the Anything app. That sounds like an attempt to reduce the self-modifying behavior Apple objected to.

Apple rejected that submission and then removed the app from the store entirely, developer Dhruv Amin said. That sequence suggests Apple was not satisfied with a partial workaround. It wanted a cleaner separation between code generation, code execution, and the app itself.

"Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps."

That quote is the heart of the issue. Apple is not trying to ban software development tools. It is trying to keep generated code from becoming an uncontrolled extension of an iOS app.

There is also a practical side here. If an app can mutate itself after review, Apple loses part of the control it uses to keep the App Store predictable for users and developers. That control has always been one of Apple’s biggest selling points, even when it frustrates builders.

How this compares with other coding tools

Apple has not removed every vibe coding app. The report says similar apps remain available, which makes this look selective rather than blanket enforcement. That is important, because it means developers still have room to build around Apple’s policy if they design the workflow carefully enough.

Compare that with the broader market. Web-first coding tools such as Replit and browser-based editors like Visual Studio Code often keep execution in environments that are easier to inspect or isolate. Apple’s discomfort rises when code moves from a browser or sandbox into an app that can alter its own behavior on the device.

• Replit is cloud-first, so much of the execution happens off-device.
• VS Code runs on desktop and has a different review model than iOS apps.
• Anything appears to have crossed into code-preview behavior Apple viewed as too dynamic for App Store rules.
• Apple’s policy focus is on downloaded code that changes app functionality, not on AI code generation alone.

That is why the same product category can get different treatment depending on where it runs. On the web, a tool can often ship faster with fewer gatekeepers. On iOS, the review process is part of the product’s legal and technical shape.

It is also worth noting that Apple’s position creates a design challenge for builders. If your app promises fast, natural-language app creation, you need to decide whether the output lives in a browser, a sandboxed preview, or a fully native runtime. Apple is making it clear which of those paths it likes least.

What this means for app builders

The immediate takeaway is simple: if you are building an AI coding tool for iPhone or iPad, assume Apple will inspect where code runs, how it changes behavior, and whether the app can mutate itself after review. That is where the line seems to be today.

For developers, this is a product design issue as much as a policy issue. A browser preview, remote execution, or fully editable source view may help an app survive review, but only if the workflow stays within Apple’s rules. Anything that looks like a hidden runtime or post-review feature swap is going to draw attention.

For users, the practical effect is that some vibe coding apps may feel less magical on iOS than they do on desktop or in the browser. That is not because the tech is weak. It is because Apple is forcing the experience into a narrower box.

My read: Apple will keep tightening enforcement around apps that generate and run code locally on device, while leaving room for tools that keep execution outside the app itself. If you build in this category, the key question is no longer “Can AI write the app?” It is “Where does the code actually run?”

If Apple keeps applying the same reading of section 2.5.2, more vibe coding apps may need browser-only previews or remote runtimes to stay listed. The next App Store rejection in this category will tell us whether Anything was a one-off or the start of a broader cleanup.