I opened the Anything app page expecting a demo and instead saw emptiness. You can still click the link, but the storefront is gone. I felt the room tilt—an app removed, a category under the microscope.
On Thursday the Anything App Store page went blank — Apple pulled Anything and raised questions
You may have clicked the same listing I did: Anything on the App Store. The app that boasted “the fastest way to build apps” now returns nothing, removed by Apple last week for what sources call a rule violation. I spoke to reports and read the threads: The Information says this is enforcement of the App Store’s rules, not a personal vendetta against one startup.
Dhruv Amin, co-founder of Anything, told The Information that people used the app to generate real tools—apps for emergency teams, gig-worker finance trackers—made on phones with help from Anthropic’s Claude and OpenAI’s Codex. Replit and Vibecode saw updates blocked earlier this month, per MacRumors; the pattern reads like a tightening of oversight.
At the heart of the issue sat Guideline 2.5.2 — a rule that limits apps from changing themselves
Apple’s Guideline 2.5.2 reads like a firewall: “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.”
Put plainly: Apple doesn’t want an app to construct other apps on-device in ways it can’t monitor. Anything’s approach—generate an app on a phone and let users debug and ship it without a computer—appears to bump against that rule. Amin said his team tried a workaround that debugged inside a browser window, but Apple rejected the update and removed the app.
Why did Apple remove vibe coding apps from the App Store?
Apple frames these removals as governance: apps that can change what they do outside their signed bundle are harder to moderate and could introduce behavior Apple can’t vet. Developers of vibe coding tools argue the apps are simply assistants—agents powered by Claude and Codex that scaffold code—but the review team sees a product that effectively produces executable changes after installation.
On developer forums the mood is tense — startups and big tools are adjusting to a new boundary
I watched comments from Replit, Vibecode, and smaller teams; the conversation is blunt: rebuild your flow or get removed. Xcode, meanwhile, has embraced AI agents—Apple added autonomous coding tools that use Anthropic and OpenAI models to edit and review code. That adds irony: Apple ships AI helpers in Xcode while policing third-party apps that let phones create apps.
The result is a moat around the App Store’s control: Apple can allow AI inside its own developer tools while limiting how third parties package similar capabilities for consumers. Vibe coding startups argue consumers want app creation without a Mac. Apple argues it needs to be able to moderate every possible executable change.
What is Guideline 2.5.2 and what does it mean for app makers?
Guideline 2.5.2 prohibits downloading or executing code that alters app behavior after installation. For developers that means any feature which assembles or installs new executable pieces on a device is risky. For companies like Anything, Replit and Vibecode, the safe path is to move code generation behind a web interface or keep any execution strictly within approved containers—if Apple accepts those changes.
At demo floors and Slack channels the consequences are already real — smaller teams scramble while big players watch
If your startup’s pitch is “build apps on your phone,” you now face two options: re-engineer to fit Apple’s container model or negotiate exceptions the platform might not grant. The Information and Gizmodo reached out to Apple; Apple has said these enforcement actions target apps that change behavior in ways Apple can’t moderate, not a category per se.
Replit and Vibecode reported blocked updates; Anything was removed. The playbook for survival may be to shift core activity to the web or to fold into Apple’s own toolchain. The App Store’s controls work like a moat around its garden, and the smaller bridges are under repair.
Vibe coding proponents argue the tech is practical: ship quickly, iterate on-device, reduce cost. Critics warn of opaque behavior and potential misuse if arbitrary code can be introduced post-install. I keep returning to a single image from the week: a new generation of app assembly that felt stable until one rule check made it a house of cards.
“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.”
Anything’s own marketing suggested the app could even generate marketing assets while you sleep; the company tweeted that vibe coding had gone “superhuman.” Whether Apple will allow that promise back into the store depends on how developers reframe where code runs and how it’s delivered.
Apple, Anthropic, OpenAI, Xcode, Replit, Vibecode, Dhruv Amin, The Information, Gizmodo and MacRumors are now names on a short list of actors rewriting the rules of mobile app creation. The question for founders and product teams: will you rebuild to appease a platform gatekeeper, or will you push the work beyond its walls—and at what cost?
BREAKING: vibe coding just went superhuman!
Anything now generates assets and handles complex tasks in the background while you do nothing
ship apps in your sleep pic.twitter.com/KQjoOjyCUt
— Anything (@anything) March 27, 2026
One side sees an overbroad rule blocking modern workflows; the other sees a policy protecting platform integrity. Which side will shape the next chapter of app creation—and who will write the new rules as tools like Claude and Codex keep getting smarter?