Apple's 30% Tax: Why iOS Development Is So Painful in 2026

You built something good. You did the napkin math on revenue, felt great about it, and then someone mentioned that Apple takes 30% off the top. Suddenly the spreadsheet looks different, and you're wondering whether iOS is worth the headache at all.

Short answer: the 30% number is the part everyone fixates on, and it's the part that matters least for most small apps. The real friction is everywhere else. Let's walk through what actually makes iOS development painful in 2026 — and where the pain is worth paying.

The 30% cut, explained honestly

Apple's standard commission on digital sales is 30%. That's the scary headline. But the number that applies to most people reading this is 15%, for two reasons:

• The Small Business Program. If you earn under $1 million in proceeds per year — which is nearly everyone launching a first app — you pay 15%, not 30%.
• Subscriptions after year one. Once a subscriber has been paying for more than a year, Apple's cut on that subscription drops to 15%.

And a lot of apps pay nothing. If you sell physical goods or real-world services — a restaurant order, a haircut booking, an e-commerce checkout — that money is billed outside Apple's system, and Apple doesn't take a commission. The 30% (or 15%) only applies to digital goods and services consumed inside the app.

The real pain: the review gauntlet

Here's what nobody warns first-time developers about. The commission is a known, predictable number. App Review is not. You can build a flawless app and still get bounced for reasons that feel arbitrary:

• Metadata rejections — a screenshot shows a status bar Apple doesn't like, or your description mentions a competing platform.
• "Spam" / 4.3 rejections — your app is deemed too similar to others, even when it isn't.
• Guideline reinterpretations — something that passed last release gets flagged this release, because a different reviewer saw it.
• Privacy and data-use questions — incomplete privacy labels or unexplained permissions trigger back-and-forth that eats days.

None of these are hard to fix. The problem is the loop: submit, wait, get a vague rejection, guess at the fix, resubmit, wait again. When you're trying to hit a launch date, that uncertainty is the genuinely painful part — far more than the percentage on the invoice.

The 30% is a line item. App Review is a coin flip you can't schedule around. That's the real tax.

The DMA, sideloading, and why 2026 feels familiar

If you followed the news, you'd think 2024–2025 blew the App Store wide open. The EU's Digital Markets Act forced Apple to allow alternative app marketplaces, sideloading, and external payment links. In theory, freedom.

In practice, Apple's response added a new layer: alternative distribution comes with its own terms and a Core Technology Fee charged per install above a threshold. For many developers, the math of leaving the App Store doesn't clearly beat staying in it. And critically, most of this applies only in the EU. If your users are in the United States, the day-to-day experience of shipping an iOS app in 2026 looks a lot like it did before the headlines.

There's ongoing legal and regulatory pressure in the US too, and the rules around linking to external payment pages have loosened in places. But "loosened" is not "gone." Treat any external-payment strategy as narrow and subject to change — not a loophole to build your business on.

How the two big stores actually compare

iOS gets the complaints, but it helps to see the trade-offs side by side with Google Play before you decide where the pain is worth it.

This is exactly the trade-off we dig into in iOS vs Android: where should you launch your first app? — if you only have budget for one platform at launch, the answer is rarely "whichever annoys me less."

So is iOS still worth it?

For most consumer products, yes — and not grudgingly. iPhone users, on average, spend more inside apps and convert better on paid features. If your audience carries iPhones, "skipping iOS to avoid Apple" is skipping the customers most likely to pay you. The friction is a cost of reaching a high-value market, and like any cost, the right move is to plan for it.

Where people go wrong (and when to call a pro)

The expensive mistakes we see aren't about the commission. They're structural:

If you're shipping your first iOS app and the revenue matters, the value of working with someone who's been through the gauntlet isn't the code. It's not stepping on the mines that cost you weeks.

Frequently asked questions