Apple BANNED These AI Coding Apps

Apple just banned AI apps. Not some random little startup nobody's heard of. Repl.it, a company worth nine billion dollars, has been blocked so they can't update their app, they can't ship new features, can't fix bugs and the reason Apple gave a rule that's been sitting inside their terms and conditions for years. A rule nobody cared about until now, until Vibe coding showed up.

Here's what Vibe coding is in one sentence. You type what you want in plain English, the AI builds it for you, no coding, no engineering degree, no experience needed. And that one sentence is the reason Apple is panicking because if anyone can build an app with their phone just by talking to an AI, then Apple doesn't control who gets to build software anymore and that changes everything. Let me show you exactly what happened, why it matters and what it means for you, whether you've ever written a line of code in your life or not.

So let's start with the facts. Apple quietly blocked Repl.it and a smaller app called Vibe Code from publishing updates to the iPhone apps on the App Store. Not a big announcement, no press release, just silent gone. Vibe Coding tools let people with little to no programming experience build apps, websites and games using nothing but natural language prompts.

You type build me a task manager with a login screen and the AI does actual work in software. Repl.it is most recently valued at nine billion dollars. Since its last update in January, Repl.it's app dropped from first to third place in the developer tools downloads chart. Repl.it actually partly says the decline is because it can't push updates.

Think about what that means. A nine billion dollar company dropped in rankings because they can't send out a bug fix because Apple said no. Apple says the Vibe Coding features violate long-standing App Store rules that say an app can't run code that changes the way it or other apps function. That's a rule simple on the service, but here's what's really going on underneath it.

So Apple made a hundred billion dollars last year. Consumer spending on iOS reached a hundred and seventeen point six billion dollars in 2025. That's money flowing through the App Store. Money they take a cut off.

Fifteen percent, sometimes thirty percent. Every app that gets bought, every subscription, every in-app purchase, Apple gets a slice. That's a machine and Vibe Coding is a wrench in the machine. Vibe Coding apps present a potential concern for Apple because they enable users to build applications that operate outside the App Store ecosystem whilst also competing with Xcode, Apple's own development tool.

Let me say that again plainer. If you build an app with Repl.it, a web app, a tool for your business, a game, it doesn't have to go through the App Store. It lives on the web. Apple never sees a penny and that's a big threat.

It's not about broken rules, it's about broken revenue. Now here's where this gets really interesting. Repl.it just raised four hundred million dollars in fresh funding. Their valuations tripled from three billion dollars to nine billion dollars in six months.

The company says it's on track to hit a billion dollars in annual recurring revenue by the end of 2026 and for context, most software companies take seven to ten years to reach a billion in revenue. Repl.it is trying to do it in less than two. Employees from 85% of Fortune 500 companies already use Repl.it. So the total registered users is actually 50 million people using one app to build software without even knowing how to code.

The number is the thing that you need to sit with because that's not developers, that's regular people. Business owners, teachers, nurses, shop owners, people who had an idea for a tool and then just went out and built it. That's what at stake here, right? And Apple looked at that number and quietly said no.

I want to take a second to give Apple a fair hearing here because it's easy to paint them as a villain. The argument isn't crazy. The issue is a long-standing App Store policy, guideline 2.5.2, which says apps must be self-contained and cannot implement code that changes their own functionality or the functionality of our apps. That rule exists for a reason.

Security. If an app can download and run new code on your phone after it's been approved, that's a real risk. A bad actor could use that to sneak malware through. Apple's App Store is famously safer than Android's open ecosystem and that's partly because of rules like this one.

And Apple says it doesn't have any rules specifically against vibe coding apps. They're not saying the category is banned, they're saying the way these specific apps work, generating and running code inside a web view inside the app, breaks the rules. So steel man accepted. But here's the thing.

Other apps with similar functionality, like for sales v0, have been able to continue publishing updates without the same limitations. Same category, different treatment. And that's a problem. Competition attorney Gene Burrus told The Information that Apple has a history of blocking apps or features that create competition on its platform.

History. This isn't the first time. Remember when Apple removed apps that let you manage your own music library because it competed with iTunes? Remember when they blocked third-party browsers from using their own engine on iPhone?

Remember when they said Fortnite violated the rules? The same week Epic started letting you buy directly, skipping Apple's cut. The pattern is a pattern. When a new thing threatens Apple's control over distribution, over revenue, over the relationship between developers and users, Apple finds a rule that technically applies and uses it.

That's not a conspiracy theory. That's a business strategy and it works until it doesn't. Here's what actually happened behind the scenes. The main point of contention is the preview feature.

Apple doesn't want dynamically generated code running with an app. After months of escalation, compromises are starting to take shape. Repl.it would open previews in an external browser and Vibecode would remove the ability to create apps specifically for Apple devices. So Apple didn't just shut or slam the door.

They said change how it works and we'll let you back in. Repl.it would get the green light if its developers configure the app to open a Vibecoded app in an external browser rather than the in-app web view. Vibecode is also close to being approved if it removes the feature to develop apps specifically for Apple platforms. That sounds reasonable on paper, but think about what it actually means in practice.

If Repl.it has to kick you out to a browser every time you want to see what you built, that's friction. That's a worse experience. That's the thing that makes you put down your phone and come back to it on a laptop later. And later often means never.

The information says Apple's intervention risks undermining Vibecoding apps usability and growth. That's the point. You don't have to ban something outright to kill it. You just have to make it annoying enough that people stop using it.

Now let me zoom out for a second because what Apple is doing here is a symptom of something bigger. Something that's happening across the whole tech industry right now. The old gatekeepers are scared and they should be. Here's the old world, right?

You had an idea for an app. You needed to hire a developer or learn to code yourself. That takes months. It costs money.

Then you have to submit the app to the app store, wait for approval, pay Apple their cut, hope people found you. Every single step of that process required someone else's permission. Apple's permission, a developer skills, a budget. Here's a new world.

You have an idea for an app. You open Repl.it on your phone. You type what you want. 20 minutes later you have something that actually works.

There's no developer. There's no code. There's no waiting. And that's not a small change.

That's really a write-out and a rewrite of who gets to build things. Repl.it CEO Amjad Massab has been building toward this for years. He grew up in Amman, in Jordan, in a lower-caste, sorry, a lower-middle-class family. His father bought home an IBM PC in 1993.

By the time Amjad was 7 years old, he had learned to code. His whole mission from the beginning was one thing, let anyone build anywhere. That kid in Jordan who learned to code on an IBM PC doesn't think software should only be for people with the right degree or the right job title. He thinks software should be like language, something everyone can use to say what they want to say.

And now Amjad runs a $9 billion company. And Apple is blocking this app. The irony is not lost on anyone. Here's the thing that really bothers me about this.

It's not the policy. It's not even the revenue grab. It's who gets hurt. It's not the developers.

Developers will find a way. They'll use a desktop app. They'll use a browser. They'll adapt.

The people who get hurt are the people who just figured out they could build something. The person who, running a small bakery, realized they could make a loyalty app for their customers. The freelancer who figured out they could automate the annoying part of their invoice tracking. The teacher who wanted to make a quiz for a class.

Those people built something on Repl.it on the phone in the gaps between other things. And now the experience is getting worse with more friction, more steps, and less magic. And some of them will stop. That's the real cost here.

It's not Repl.it's app ranking. It's not Apple's revenue numbers. It's the people who almost became builders who got pushed out right at the moment of entry. Now, let me tell you what this tells us about where things are going.

Repl.it's platform has been adapted by employees at 85% of the Fortune 500. Corporate customers include Atlassian, LabCorp, PayPal, Zillow, Talkdesk, and Adobe. Personnel management company UKG, with over 16,000 employees, uses Repl.it for rapid prototyping and a development of internal tools. So this isn't a toy anymore.

This is enterprise infrastructure. And when enterprise infrastructure gets blocked from the app store, the enterprise starts asking questions. Why are we using iPhones? Why are we locked into this ecosystem?

What does it cost us to leave? Apple is playing a dangerous game here. Rival Lovable, a vibe coding startup founded by Swedish entrepreneurs Anton Sigur and Fabian Hedin, just reached $400 million in annual recurring revenue, after seeing roughly 200,000 projects created per day, right, on one platform. Not Repl.it, Lovable, a competitor.

And that's not counting the dozens of other vibe coding tools that are exploding right now. You know, you've got Cursor, you've got Lovable, people like that. These companies are growing faster than any software in history, and they're all building towards the same thing, which is a world where coding knowledge is optional. And Apple, in some ways, is holding back a tide.

Now here's what I want to think about, you know, and here's how I want you to think about something most people aren't thinking about, right. So this isn't just a story about apps. This is a story about who controls the tools to build the future. Right now, most of the power in the digital economy sits with people who can code.

Developers get paid more, developers have more options, developers can build the thing they imagine. Everyone else has to ask someone else to build it for them, and that costs money and time. And often the idea dies before it gets made, because people run out of resources, or people are scared to take a risk. Vibe coding is changing that equation.

Repl.it's CEO says vibe coding is unlocking new opportunities for solo entrepreneurs, from Uber drivers tinkering with side projects, to doctors prototyping medical apps. An Uber driver building an app on his phone between rides, for example. A doctor prototyping a tool for his patients without waiting for a hospital's IT department. That's a shift, that's what's real.

It's not five years away, it's happening right now. Now this is the part where I need to be direct with you. If you're a business owner, a freelancer or creator, someone who has ideas and has always had to rely on other people to build them, the window to learn this stuff is right now. It's not going to be wide open forever.

The tools that you have right now, you're early, you understand this better than anyone else, and the Apple Store is a perfect example of the tension underneath all of this. The old world is trying to hold on, the new tools are breaking through anyway. And the question is, which side of that are you on? Are you someone who watches that happen to other people, or are you someone who figures out how to use it?

If you want help with that second thing, that's exactly what the AI Profit Boarding is built for. It's a community of 2,600 business owners. We give you daily tutorials, 30-day roadmaps, we have a map where you can connect with people locally. It's an amazing community and there's always people online 24-7, which means that you can get the help and support that you need, and you can meet an amazing, supportive community of people actually building with this stuff, not just reading or watching videos about it.

So feel free to check it out, link in the comments description, or go to theaiprofitboarding.com. Now let me show you where this goes next. Apple is not going to win this fight, not long-term, and here's why. The EU is already coming for them.

Regulators in Europe have been pushing Apple to open up the app store for years. They've already been forced to allow third-party app stores in Europe, and that's a crack in the wall. The US Department of Justice has had Apple in its sights on antitrust grounds as well. And the developers, the people Apple needs to keep building great apps, are watching this too.

They're noticing who gets blocked and who doesn't. They're noticing that for sales v0 kept updating whilst Repli gets frozen. That's the kind of inconsistency that turns developers into advocates for regulation. Apple is an incredible product, right?

iPhones are genuinely amazing devices, but the app store has always been a tension point. The 30% cut, the arbitrary rejections of rules that seem to apply differently to different companies. This vibe-coding crackdown is just the latest version of the same story. And every time Apple does this, they make it a little easier for the next regulator, the next core, the next competitor, to make the case that the app store itself is a monopoly protecting itself.

There's another piece of the story that almost nobody is talking about. When it comes to vibe-coding within a development environment, Apple does explicitly support this kind of activity. With Xcode, for example, Apple made it easy for a person without code knowledge to create a simple app in minutes. So let me say that out loud.

Apple is blocking Repli from helping you vibe-code, whilst at the same time adding AI vibe-coding features to Xcode their own tool. They don't want to stop vibe-coding, they want to be the ones who sell it to you. They want you on their own platform, right, using their tools, publishing through their store, paying their cut. That's the actual policy, not the rules in the terms and conditions, the policy underneath the policy.

Control the input, control the output, and take the cut in the middle. And to be fair, it makes sense in a business context, you know, it's exactly what any company with a dominant platform would try to do. But you should know how it is. Now, Claude Code, Anthropic's coding tool, has seen its annualized revenue surge to 2.5 billion dollars.

Now, Repli's biggest competitive challenge right now is Claude Code, which is considered the vibe-coding front-runner. So even inside the vibe- coding world, there's a competition running. You've got Repli versus Claude Code, Lovable, Cursor, GitHub, CodeViolet, Bolt, a dozen others, and the tools are getting better every month. The prices are coming down, and things you can build without knowing code are getting more complex, more useful, and more real.

A year ago, you could build a simple web page with these tools. Today, you can build full-stack applications. AI Studio even just released a new one this week. And that means you can build apps with logging systems, databases, payment processing, real software.

Who knows where we're going to be six months from now. We don't fully know, but the trajectory is obvious. The question isn't whether this changes everything, it is already changing everything, but it's whether you're going to build tools the new way or the old way. Now, let me talk about what this means for four different types of people.

If you're a business owner who's ever had an idea for a tool but couldn't afford to hire a developer, this is your moment. You can start using Repl.it or Cursor or that sort of thing to start doing this, right? If you're a freelancer or a creator, the people winning right now are the ones who can offer AI automation as a service. Not teaching it, doing it.

Building workflows, building tools, building automations that save clients hours every single week. If you're a manager or a team leader, well your job in the next 12 months is to figure out how AI tools fit into what your team builds, right? And not in a vague strategic sense, but in a specific practical sense. You know, what takes your team three hours per day that could take three hours per week?

Where are the bottlenecks that a simple AI built tool could have removed? I would start asking those questions. We actually built one for our LinkedIn agency this week to just improve the speed of everything that we do in operations. And that saves a lot of time.

So here's the thing that keeps me coming back to this Apple story. It's not really about Apple. It's not really about Repl.it. It's about a very old question that shows up every time a technology makes something easier.

Who gets to make things? For most of history, you needed resources and specialized knowledge to make something. You needed the printing press to publish. You needed a recording studio to make music.

You needed a factory to make products. You needed code to make software. The internet knocked down some of those walls and AI is knocking down more. And the instructions that got comfortable, sorry, the institutions that got comfortable being the gatekeepers, the ones who decided who got to make things and under what conditions, are doing what institutions always do when the walls come down.

They're finding the rules that technically let them keep the gates. Apple has a rule. The rule technically applies. So they're using it and I don't blame them.

But these tools are going to get better and people will find a way around it. That's the thing. They always do. So that's where we're at right now.

And right at the edge of that moment, you know, the Apple story is a story about gatekeepers fighting to stay relevant. The Repl.it story is a story about what happens when building software stops being a specialist skill and becomes something anyone could do. And vibe coding has crossed from experimental tech to business critical infrastructure. So check it out today.

See what you can build. See what you can create. If you want to learn more, check out the AI Profit Boardroom and inside there we can connect. We've got loads of training on vibe coding, all these different tools you can use, lots of cool training right there, and also an amazing community of great people.

So feel free to check it out. Link in the comments description or just go to the AIprofitboardroom.com and thanks for watching.