Apple’s App Store rules collide with ‘vibe coding’: why Replit-style builders are getting blocked

Original article (source): MacRumors - “Apple Quietly Blocks Updates for Popular ‘Vibe Coding’ Apps [Updated]” (Mar 18, 2026)

• https://www.macrumors.com/2026/03/18/apple-blocks-updates-for-vibe-coding-apps/

What happened (the short version)

MacRumors reports (citing The Information) that Apple has been blocking or delaying updates for AI “vibe coding” apps like Replit and Vibecode.

Apple’s stated reason is not “we dislike vibe coding”, it’s that certain implementations appear to violate long-standing App Store rules around downloading/executing code that changes app functionality (Guideline 2.5.2).

MacRumors also included an update: Apple told them there are no vibe-coding-specific rules, and that App Review is applying existing guidelines consistently.

The practical rule that matters (Guideline 2.5.2, in real life)

The story is a good reminder that App Review cares less about what you call your product (“builder”, “assistant”, “generator”) and more about what it does:

• If your app can generate something that behaves like a new app (or materially changes your app’s behavior), Apple will look hard at whether that’s effectively “executing new code”.
• If that generated experience is rendered inside the app (for example, an embedded web view), it can look like you’re shipping a platform-within-a-platform.

MacRumors says Apple may be more comfortable if generated apps open in an external browser rather than running inside the host app.

Why app marketers should care (even if you don’t ship dev tools)

This isn’t just a dev-tools drama.

If you run an app with:

• user-generated “mini apps” (templates, automations, dashboards)
• scriptable workflows
• embedded web experiences that unlock materially new “features”

…this is the same edge of the map.

The marketing risk is simple: when your update cadence gets throttled by review back-and-forth, you pay for it in conversion and retention.

Tiny win

If your product roadmap includes “let users build/run things”, do a quick App Review pre-mortem:

• List what is generated (HTML? JS? workflows? executable logic?).
• Write down where it runs (in-app web view vs external browser vs server-side).
• Check if the generated thing could be reasonably described as “introducing or changing features or functionality of the app”.

That 10-minute exercise can save you a quarter of awkward review ping-pong.

Read the original: https://www.macrumors.com/2026/03/18/apple-blocks-updates-for-vibe-coding-apps/