Apple's App Store Math Stopped Being a Single Number in 2026. If You're Shipping a Paid App, Your 2023 Napkin Math Is Wrong.
If you're about to ship a paid app and your business model rests on "Apple takes 15%," stop and check, because that number is no longer a number you can plan on. The global Small Business Program rate is real and still 15%. But in 2026 the App Store fee structure became layered and region-dependent enough that the effective take on your first dollar depends on where your customers live, how you process payments, and which optional services you opt out of. The clean single percentage you did your napkin math with a couple years ago doesn't exist anymore.
I'm not writing this to rage at Apple. Plenty of people do that and it doesn't change your spreadsheet. I'm writing it because solo developers price products off a remembered number, and the remembered number is now wrong in ways that can quietly turn a thin-margin app into a losing one.
The part that's still simple
The Small Business Program is the solid ground. If you earned under $1 million in proceeds in the prior calendar year, you qualify for a 15% commission instead of 30% on paid apps and in-app purchases. New developers qualify too. Cross $1M in a year and the standard 30% applies to sales above the threshold for the rest of that year; drop back under $1M and you re-qualify the following year. That mechanism has been stable since the program launched in 2021, and for a developer selling mostly outside the EU, "15% under the Small Business Program" is still a reasonable planning number.
So if your market is, say, primarily the US and you're under the $1M line, you can mostly still trust the old math. The trouble starts when your users are in Europe.
The part that stopped being simple
In the EU, Apple has been restructuring fees under regulatory pressure, and the result is no longer one rate: it's a stack. The old per-install Core Technology Fee was slated to be replaced, as of January 1, 2026, by a Core Technology Commission: a percentage on digital goods and services revenue rather than a flat per-download charge. Alongside it sit other components (an initial-acquisition fee and tiered store-services fees), so that what you actually pay is a sum of parts that varies with the options you choose. Depending on how you distribute and monetize, developers can assemble a combined rate well below the old flat 30%, or not, depending on which services they keep.
And here's the detail that matters most for planning: as of mid-2026, this transition is still in motion. Reporting through June indicates the move to the new model has not fully settled and Apple remains in discussion with the European Commission about the final shape. So the EU fee structure right now is not just complicated: it's a moving target. You cannot pin it to one figure because Apple itself hasn't pinned it to one figure.
Why this is a solo-operator problem specifically
A big company has a finance team that models this per-market and updates the model when Apple changes the terms. You have a weekend and a memory of "15%." That asymmetry is the actual risk. The fee structure didn't get dramatically worse in headline terms; it got harder to know, and "harder to know" is more dangerous for a one-person business than a higher flat rate would be, because you'll plan against a number you're confident about and that confidence is the bug.
Concretely, the failure mode looks like this: you price an app at a level that works at a 15% cut, most of your early traction comes from Europe, your real blended take is higher and changing, and you discover the gap only when you reconcile a quarter that should have been profitable and wasn't. Nothing dramatic happened. You just planned with a stale constant.
What I'd actually do
Stop treating Apple's cut as one number and model it per region, with your actual expected user split. For non-EU revenue under $1M, plan around 15% and move on: that part is stable. For EU revenue, do not hardcode a rate; pull Apple's current developer support pages for the EU fee structure at the moment you're pricing, write down the assembled rate for the specific options you're using, and date that note, because it will change. If your margins are thin enough that the difference between a 15% and a 20-something-percent blended EU take decides whether the app is viable, that's not a detail: that's the business, and you need the real number before launch, not after.
The honest counter-take: if you're selling a higher-priced app with healthy margins and most of your users are outside the EU, all of this is noise and 15% is close enough to plan with. That's a real and common situation, and if it's yours, don't over-engineer it. But if you're shipping a low-priced app, leaning on European users, or running margins where a few points decide profitability, "Apple takes 15%" is the kind of confident, outdated number that ends businesses quietly. Check the current rate for your actual markets before you commit to a price. The single number is gone; act like it.
Author
Lukas
@lukcombinator