Apple enforces restrictions on app-building tools
Apple is enforcing restrictions around “vibe-coding” and other mobile app-building tools, according to reporting by TechCrunch. The company has blocked updates or removed apps from the App Store, affecting multiple services including Replit, Vibecode, and Anything. Anything’s app was removed twice, after which the company began exploring alternative distribution methods—such as launching iMessage-based building and planning a desktop companion—while also considering Android as a platform option.
What Apple is targeting: developer agreement clause 2.5.2
The core issue centers on developer agreement clause 2.5.2, which Apple cited to Anything. In an email screenshot shared by Anything on X, Apple stated the app was restricted or removed because clause 2.5.2 “prevents apps from downloading, installing, or executing code.”
Apple’s stated position, as described by Anything’s co-founder Dhruv Amin in a TechCrunch conversation, is that vibe-coding tools present certain risks. Amin said Apple told the company that the app was removed due to the potential to “download malicious code.” The report also notes that Apple raised a scenario where a user could build an app, sideload it on their phone, and then claim it passed Apple’s App Review process.
From a technical standpoint, Apple’s enforcement appears focused on the underlying capability that these tools enable: generating or moving executable code toward a device. Anything’s app, according to Apple’s description in the email screenshot, markets itself as a mobile app builder for iPhone and advertises features including “1-tap App Store submissions,” “code export,” and “full source code editing.” These capabilities can blur the line between an app that helps with editing or previewing and an app that could facilitate code installation or execution under iOS rules.
Anything’s removal timeline and the App Store approval process
TechCrunch reports that Apple removed Anything’s app on March 26, after which Anything was unable to get the app approved. Amin told TechCrunch the company experienced “no problems through December,” but after December “we and everyone else in the category started getting our updates blocked.”
The report notes that Anything’s app experienced a brief reinstatement before being removed again. Amin said the company’s efforts included “emails, calls, appeals, and four technical rewrites” intended to comply with Apple’s requirements. The article describes the situation as a “long saga,” and notes that Anything’s app was restored on April 3 only to be removed shortly afterward, with Apple telling the company it “couldn’t market itself as an app maker.”
Apple’s stated rationale appears to shift between code-related restrictions (clause 2.5.2 and concerns about malicious code) and marketing positioning (the claim that the app cannot be marketed as an app maker). TechCrunch states that it reached out to Apple for comment.
For developers and platform observers, the technical implication is that “vibe-coding” workflows are being evaluated not solely by their stated purpose, but by what they could enable on iOS—particularly around downloading, installing, or executing code. If the enforcement is interpreted broadly, builders may need to redesign their products so that user-generated outputs remain within Apple’s acceptable boundaries, or so that the app’s marketing does not cross lines Apple associates with “app maker” functionality.
Workarounds: iMessage building and desktop companion
Following the App Store removals, Anything is exploring alternative approaches to let users build mobile apps. TechCrunch reports that the company launched a feature allowing users to build apps using the iMessage platform. The company also said it would develop a desktop companion app that lets users build mobile apps on their computer.
These shifts move parts of the workflow off the phone and into environments Apple may treat differently. While the report does not specify how the desktop companion affects compliance, the direction suggests a strategy: keep the build experience available while restructuring where code generation, editing, and submission occur.
Anything’s approach highlights a practical constraint for mobile app builders: if iOS distribution and review processes limit certain capabilities, developers may route the user journey through other Apple surfaces (like iMessage) or through a desktop interface that can produce artifacts for downstream use. Observers may watch closely to see whether these product changes address the specific triggers Apple cited—particularly clause 2.5.2-related concerns and the “app maker” marketing framing.
Platform strategy: Android and app submission volume
The report notes that Amin may also evaluate Google’s Android operating system for building apps, noting that the platform is “more open than iOS.” This reflects a common industry response: when one ecosystem’s rules constrain a workflow, developers evaluate where similar capabilities can be offered with fewer restrictions.
TechCrunch also situates the Apple dispute in a broader context around app creation. It references “AI-powered coding tools” and notes that The Information reported Apple saw an 84% jump in app submissions in a single quarter due to those tools. The report suggests this could prompt Apple to reconsider “human-led review processes.” It also notes that as AI-powered coding becomes more accessible, “consumers might demand that platforms like Apple allow them to create apps for themselves.”
These points suggest a tension between (1) the growing availability of tools that generate code and (2) platform controls designed to limit how executable code reaches devices. As app submission volume rises and code generation becomes more accessible, platform policies and review approaches may face increased pressure. For developers building vibe-coding experiences, compliance requirements may expand beyond the app’s user interface into the mechanics of what the tool can do, how it is marketed, and where the workflow runs.
Industry response
Beyond Anything, the report notes that Epic Games CEO Tim Sweeney has commented on Apple’s actions. In a reply to Replit’s Amjad Masad on X, Sweeney said Apple needs to “stop blocking development tools apps ASAP.” The report also includes Sweeney’s reference to Steve Wozniak’s statement about Apple’s founding principles, including the idea that early Apple II computers booted to a programming language prompt and treated using and making software equally. These remarks, as presented by TechCrunch, connect the policy dispute to a longer-running debate about developer tools and platform openness.
The public nature of these disputes indicates that developers of app-building tools are increasingly vocal about platform friction, which can influence how quickly app makers iterate their workflows, how they describe their products, and whether they seek alternative distribution paths.
Source: TechCrunch