Vibe Coding Removed from App Store: What’s Next?

In March 2023, Apple completely removed the Vibe Coding app, Anything, from the App Store, marking a significant setback for its survival in a closed ecosystem. This article delves into the core of this conflict—Apple’s Guideline 2.5.2 and its fundamental incompatibility with AI-generated code logic. As the platform insists on a static review framework, entrepreneurs are forced to make tough choices between web-based survival and migrating to Android. This situation represents not only a technical battle but also a real challenge to the monopolistic review power of app stores.

Anything’s co-founder and CEO, Dhruv Amin, stated that the app had previously helped users publish thousands of applications on the App Store, including management systems for emergency responders and reimbursement tracking tools designed for gig economy workers.

According to reports, prior to Anything’s removal, Apple had already imposed update freezes on similar applications like Replit and Bitrig, indicating a systematic tightening of the Vibe Coding category. Apple maintains that this action is merely enforcing existing rules to prevent apps from introducing new features without review. However, critics argue that this review framework, designed for static apps, is fundamentally incompatible with the underlying logic of AI-generated content.

Amin remarked, “This is the problem with Apple and closed platforms—either they are making a mistake, or they decide that your category is not allowed to exist.” He is currently evaluating a shift to Android, while other teams have already turned to pure web development. The future of Vibe Coding is becoming increasingly clear.

After Launching Thousands of Apps, Apple Suddenly Changes Course

Last August, Anything entered the market as a browser-based Vibe Coding tool. Vibe Coding allows individuals without programming experience to generate applications directly through AI—users describe their ideas, and the code is automatically produced. In November, Anything launched its iPhone client, and the App Store review team raised no objections, allowing it to be released smoothly.

In the following months, Anything continued to update, and users had published thousands of applications on the App Store through this tool. These included valuable products such as a management system for emergency responders and a reimbursement tracking tool for gig economy workers, demonstrating that Vibe Coding is not merely a toy-level technical experiment.

The turning point occurred in mid-December 2022 when Apple’s review team began rejecting every update submitted by Anything, citing violations of Guideline 2.5.2. This was less than two months after the iPhone version was launched. Amin attempted to compromise by moving the Vibe Coding preview feature from the app to the web browser to avoid controversy. Apple not only rejected this submission but also removed the entire app from the App Store in March 2023.

From initial approval and operation to update freezes and final removal, the entire process took less than six months. Before Anything’s app was officially removed, reports indicated that Apple had blocked updates for multiple Vibe Coding applications. Shortly thereafter, Anything faced a more thorough removal.

Meanwhile, Replit and Bitrig, also part of the Vibe Coding category, remain on the App Store but are similarly unable to update—Replit’s last update was in January, and Bitrig’s was in November 2022. Apple’s attitude towards this category reflects a systematic tightening.

Guideline 2.5.2: A Rule That Closes Off a Category

Apple’s sole reason for the removal was Guideline 2.5.2, which states that applications must be “self-contained within their installation package” and must not read or write data outside designated container areas, nor “download, install, or execute code that introduces or alters application features and functions.”

The original intention of 2.5.2 was to prevent developers from bypassing App Store reviews and silently pushing unreviewed feature changes on user devices. This logic is reasonable—within the context of mobile security, applications expanding permissions without review indeed need to be constrained. The problem arises when this rule is applied to the Vibe Coding category, as its reach far exceeds its original design intent.

The core mechanism of Vibe Coding tools is to generate and execute code at runtime via AI. Users describe their needs, and the model outputs logic, with the application presenting results in real time. This process naturally falls into the prohibited zone of 2.5.2—each generation is akin to pushing “unreviewed new features” to the device. In other words, as long as Vibe Coding remains Vibe Coding, it cannot operate on iPhone without violating this rule.

Apple’s statement is that the company is not targeting the Vibe Coding category but is merely enforcing existing rules to prevent applications from making substantive changes without review. While this explanation is technically sound, it sidesteps a critical question: why should a rule designed for static applications be applied to AI tools that generate dynamic content?

Anything attempted a compromise path by migrating the code preview feature to a web browser, allowing AI-generated content to be displayed without executing directly within the native app. The logic behind this solution is that the browser itself is a sandbox environment, circumventing the local code execution restrictions of 2.5.2. Apple rejected this submission and subsequently removed the entire app. This indicates that Apple is not only enforcing rules but also narrowing possible exceptions.

For other developers, the current enforcement of this rule creates a highly uncertain situation. Apps like Replit and Bitrig remain available but cannot update; some teams, like Vibecode, have proactively abandoned iPhone development in favor of pure web solutions. The same rule produces vastly different enforcement outcomes, and Apple has yet to provide clear boundary explanations.

The Cost of a Closed Platform: How Can Entrepreneurs Coexist with Apple?

After Anything was removed, Amin stated, “This is the problem with Apple and closed platforms—either they are making a mistake, or they decide that your category is not allowed to exist.” This statement highlights a structural dilemma that entrepreneurs face in platform ecosystems, which is rarely addressed.

In the mobile internet era, the App Store is the only legal channel to reach iPhone users. For consumer-facing applications, losing this entry point is almost equivalent to losing the entire market. Before its removal, Anything had accumulated thousands of user-published applications through this channel, establishing a real product ecosystem. All these assets lost visibility to iOS users the moment the app was removed.

The unpredictability of the timeline is even more challenging. The iPhone version of Anything passed the App Store review team’s formal approval at launch, only to face a freeze months later. Approval does not guarantee long-term compliance; the interpretation of platform rules remains solely in Apple’s hands and can be redefined at any time. For early-stage startups, this uncertainty is nearly impossible to hedge through any conventional business planning.

Faced with this situation, entrepreneurs have few options. Amin is currently evaluating whether to shift focus to the Android platform, which means rebuilding the product on a new tech stack while bearing the friction costs of user migration. Another option is to completely transition to the web, bypassing all native app store controls—Vibecode has already made this choice, abandoning iPhone development. Both paths mean sacrificing the established iOS user base, which comes at a real cost.

From a broader perspective, Apple’s handling of the Vibe Coding category exposes the adaptability issues between platform rules and emerging technologies. The existing App Store review framework is designed for static, functionally fixed native applications. As AI blurs the boundaries of applications, the original review logic begins to fail—but the cost of this failure is borne by developers.

Apple itself has profit considerations. Xcode has recently integrated Anthropic’s Claude and OpenAI’s Codex, launching AI programming assistance features for professional developers. The core value proposition of Vibe Coding tools is to enable non-professional users to build applications directly, bypassing professional tools like Xcode. This competitive relationship complicates the interpretation of Apple’s stance on this category.

The Future of Vibe Coding Is Not in the App Store

Amin’s judgment is worth highlighting: “The scale of Vibe Coding will far exceed Apple’s current imagination.”

The essence of Vibe Coding is to lower the barriers to software production. When someone without any programming background can describe their needs in natural language and receive a runnable application, software development transforms from a specialized skill into a tool accessible to ordinary people.

This shift in magnitude parallels the democratization of financial modeling through spreadsheets and website building through no-code tools, representing a paradigm shift of the same scale. The App Store’s blockade cannot change this direction; it can only influence where it lands.

Currently, the direction is becoming increasingly clear: the web. Vibecode’s choice is representative—abandoning the iPhone native side and focusing on browser-based product experiences. This path circumvents the App Store’s review controls, at the cost of sacrificing some native experience and distribution benefits. However, for tools like Vibe Coding, the core value lies in the generation capability itself, rather than platform nativeness—the web can sufficiently carry this value.

From a distribution logic perspective, a web-first strategy is more flexible in the current environment. Users can access directly through links without going through any app store review nodes, and the speed of product iteration is not constrained by third-party approval cycles. This aligns perfectly with the pace needed for AI-native products—models are rapidly evolving, and products must be updated in sync; any review friction can lead to competitive delays.

Regulatory variables are also worth noting. Apple’s systematic blockade of emerging AI tools has drawn the attention of antitrust observers. In the context of ongoing scrutiny of large platform behaviors by regulatory bodies in Europe and the U.S., whether Apple’s actions constitute improper exclusion of competitive development tools is a question still under discussion. If regulatory pressure ultimately forces Apple to open sideloading or relax review standards, there may still be a window of opportunity for Vibe Coding tools to return to iOS.

However, until that day arrives, the main battleground for this category has quietly shifted. Anything is evaluating Android, while other teams are betting on the web, and the entire industry’s focus is moving away from the App Store as a singular entry point. Apple’s blockade has, to some extent, accelerated the diversification of the Vibe Coding ecosystem—likely not the outcome Apple intended.