Build · founder · 6 min read

Apple's App Store Crackdown: What Founders Building Mobile Apps Need to Know

Apple is removing vibe coding tools from the App Store. Here's what happened, why it matters, and what to do if mobile is your distribution plan.

Published April 15, 2026 ·

mobile App Store Apple distribution risk

If you’re a non-technical founder who planned to build a mobile app with a vibe coding tool and ship it to the App Store, you need to read this before you start.

Apple has been quietly blocking and removing vibe coding apps from its platform since late 2025. In March and April 2026, the conflict went public. The vibe coding tool Anything was removed from the App Store twice in three weeks. Replit and Vibecode have had their iOS updates blocked. The number of new apps submitted to the App Store jumped 84% in a single quarter — and Apple, facing a flood of AI-generated apps, is responding with enforcement action.

This isn’t a panic situation. But it is a real risk that should shape how you think about mobile distribution.

What Apple is actually doing

Apple hasn’t announced a policy against vibe coding. Their public position is that they’re enforcing existing rules — specifically, Guideline 2.5.2, which prohibits apps from downloading and executing code after review. An Apple spokesperson told The Information that the company is “not targeting vibe coding as a category.”

In practice, the enforcement looks different. Apple told Anything’s co-founder Dhruv Amin that his app was removed because it “could be used to download malicious code” — a vague rationale that could be applied to any platform that generates code. Replit and Vibecode had their update submissions frozen, not rejected outright, leaving their apps in limbo.

The underlying anxiety Apple is responding to is real: if a vibe coding tool can generate an app that passes review, that app gets Apple’s implicit approval stamp — even if the AI built something harmful. Apple’s review process is designed around human-authored code. Vibe coding breaks that assumption.

Why the 84% surge matters

Apple saw app submissions jump 84% in a single quarter. That’s not a product trend — that’s infrastructure stress. Review times have stretched from the usual 24-48 hours to 7-30 days as teams try to process the volume. Developers who relied on fast review cycles for bug fixes and feature launches are sitting on two-week queues.

The flood is also changing how App Review approaches new submissions. Reviewers are reportedly asking more questions, requesting more documentation, and taking longer on apps that look AI-generated. This affects you even if you’re not using a vibe coding tool — the backlog doesn’t discriminate.

Which tools are affected

The three most visibly impacted tools as of April 2026:

Anything (createanything.com) — Removed twice. Currently rebuilding via a desktop companion app and iMessage-based distribution. Web platform is unaffected.

Replit — Updates blocked since late 2025. The core Replit web platform and deployment tools are fully functional; it’s the iOS app that’s frozen.

Vibecode — Updates blocked. Similar situation to Replit.

Tools that build web apps and progressive web apps (Lovable, Bolt, Base44, v0, and most others) are unaffected. Apple’s enforcement is specifically targeting tools that submit directly to the App Store or generate native iOS apps.

What this means for your project

The right conclusion depends on what you’re building.

If your app only needs to work in a browser — Lovable, Bolt, Base44, and most full-stack builders ship web apps. A web app hosted at your domain works on mobile too. PWAs (Progressive Web Apps) can be added to a user’s home screen and behave like native apps for most use cases: push notifications, offline access, camera, location. If your product works as a web app, you may not need the App Store at all.

If you specifically need an App Store listing — This is where you should pause and think carefully. The App Store gives you discoverability, payment infrastructure (Apple IAP), and the trust signal that comes with the apple badge. But right now, the path from vibe coding tool to App Store listing is more complicated than the marketing suggests. Tools are adapting, but the situation is in flux.

If you’re pre-build — Choose your tool based on where this is likely to land, not where it is today. Anything is working on a Mac desktop app that builds iOS apps on-device, which would sidestep Apple’s objection. Apple may clarify its policy, or developer pressure may push them to loosen enforcement. The category is too big to block indefinitely — 72% of developers now use AI coding tools daily.

The workarounds founders are using

The vibe coding tools haven’t accepted defeat. Here’s what’s happening on the ground:

Desktop generation: Anything is shipping a desktop companion that generates and builds your iOS app locally on your Mac, using your own developer account. This puts the code generation on your device — not in a cloud tool — which Apple has less jurisdiction over.

iMessage mini apps: Anything briefly launched iMessage app generation as a direct response to the App Store removal. It’s a niche workaround, but it signals the willingness to find alternate distribution channels.

PWAs as default: Lovable and Bolt have always defaulted to web. For many product categories — internal tools, SaaS dashboards, simple consumer apps — a well-built PWA is indistinguishable from a native app in daily use.

Testflight distribution: Testflight (Apple’s beta testing platform) has different rules from the App Store. Some founders are shipping via Testflight while the main submission situation resolves. Testflight has a 10,000-user limit per app, which is more than enough for an early-stage product.

The honest risk assessment

Apple’s enforcement is inconsistent and the rationale is vague — which makes planning around it difficult. There are a few plausible scenarios:

The enforcement continues at current levels, and mobile vibe coding tools adapt by moving code generation off the cloud (desktop apps, local tools). In this case, App Store distribution remains possible, but the frictionless “describe and submit” experience is gone.

Apple clarifies policy — either loosening it (under developer pressure and regulatory scrutiny) or tightening it with explicit rules. Either outcome is better than the current ambiguity.

The 84% submission surge creates so many false positives in App Review that Apple builds AI detection tools rather than trying to ban the category outright. This is probably the most likely long-term outcome.

None of these scenarios suggests mobile vibe coding is dead. But they do suggest that launching on iOS in 2026 involves more uncertainty than it did 18 months ago.

What to do right now

If you’re building something where App Store distribution matters:

1. Don’t build exclusively for App Store distribution. Build a web version first. It’s faster, it works today, and it validates your core idea. App Store can come later.

2. Watch the Anything desktop app. If it ships and works as described, it’s the cleanest path to App Store submission for vibe-coded apps. Sign up for early access.

3. Consider Testflight for early users. If you have a small initial cohort (under 10,000 users), Testflight is a legitimate distribution channel that doesn’t require going through the same review process as the App Store.

4. Don’t count on Apple’s timeline. Review queues are at 7-30 days right now. If you have a launch event, partnership announcement, or funding tied to a specific date, plan for delays.

The broader point is this: the App Store has always been a risky distribution channel because Apple controls it unilaterally. Vibe coding has just made that risk more visible. Build something people want first, then figure out the best path to their phone.