Apple Opened Another Door in Europe. There's a Meter on the Frame.

You can’t talk about the App Store anymore without asking which App Store. Apple has revised its app policies again in response to the EU’s Digital Markets Act, and developers are split roughly down the middle on whether this counts as opening up or just repackaging.

One caveat before we go further. The community signal on this round is thin. There’s no substantial Reddit thread from the past 30 days tackling it head-on. So what follows reads the structure of the last two years of DMA fights and the developer reactions that have repeated throughout, rather than tallying live sentiment. Treat it as a read, not a scoreboard.

What the DMA Demanded, and What Apple Delivered

The DMA’s ask is simple. Platforms designated as gatekeepers can’t force developers through their own distribution channels. Open up alternative app marketplaces. Stop blocking links that steer users to outside payment. Let users pick their own default apps.

On paper, Apple complied with all of it. Alternative marketplaces exist in the EU. Web distribution is possible. External payment links are allowed.

The catch is what came attached. Apple opened the door and rewrote the price list at the same time. Leave the App Store and you still owe Apple money. The line that keeps circulating in developer circles: the door is open, but there’s a meter on the frame.

Developers Ran the Numbers

What EU developers actually did wasn’t ideological. It was arithmetic. They dropped the new terms into a spreadsheet and checked whether switching left anything on the table.

The answers converged. The more downloads you have relative to revenue per app, the worse the new terms look. Per-install charges land hardest on free apps and anything with a weak conversion rate to paid. Flip it around and the math works: high average revenue per user, existing payment infrastructure, enough volume to amortize the compliance work.

So the field split vertically. Spotify and Epic — companies with the balance sheet to fight Apple in court and the engineering budget to run their own storefronts — took the new paths. Solo developers and small studios mostly stayed exactly where they were. The options regulation pried open turned out to be, functionally, enterprise-only.

That’s where the cynicism runs deepest. Some version of “this was supposed to be for us, and we’re the ones who can’t use it” keeps resurfacing, just with the wording changed.

The Real Cost Is Fragmentation, Not Fees

The bigger shift isn’t the commission rate. It’s that the App Store stopped being one thing.

There is no single App Store now. The EU has DMA-compliance rules. The US has the external-link policy Apple adjusted after the Epic ruling. Japan has its own regime under domestic competition law. Which payment methods are permitted, which warning screens you must display, what rate you pay — all of it varies by jurisdiction.

For a developer, that’s an operations problem, not a code problem. You fork the payment flow by region. You track policy changes separately in each market. Your accounting splits. Building the app costs what it always did; running it now scales with the number of regions you serve.

The irony writes itself. The only companies that can comfortably absorb this complexity are, again, the big ones. Every additional layer of regulation advantages whoever can afford a compliance department.

Apple’s Argument Isn’t Nothing

It’s hard to dismiss Apple’s position outright. The commission, Apple says, was never a payment-processing fee. It covers Xcode, the SDKs, the APIs, the distribution infrastructure, the review system — the whole apparatus.

Follow that logic and a developer who exits the App Store is still consuming that value the moment their app runs on iOS. Hence a fee that survives the exit. And you do see the counterpoint in developer threads: nobody seriously argued the platform should be free.

The rebuttal is equally clear. When one party sets the price, there’s no one to negotiate with, and that same party also designs your exit route — that isn’t a market price. That’s a tax. Which means the actual dispute was never whether Apple gets paid. It’s who sets the number, and through what process.

Why Sideloading Never Took Off

Sideloading generated the most excitement in the early DMA days. Then users didn’t show up in the numbers anyone expected.

Several reasons stack. Installing an alternative marketplace means clearing multiple confirmation screens. Security warnings appear mid-flow. To a normal user, the whole sequence reads as “am I about to do something dangerous.” And there was never enough of a killer app available exclusively outside the App Store to make it worth the friction.

That gap — between technically possible and actually happening — is the whole story here. Regulation can build the road. Whether anyone walks it comes down to whether the product at the other end is worth the trip.

What Developers Actually Got

The real win is that negotiation now exists as a category. Apple’s policy used to function like physics. Now there’s a lever, and it’s called a regulator. Apple has revised its terms multiple times specifically because of that pressure.

The tangible gains are still thin, though. For most small developers, this round added one more option to the menu. It did not change the revenue model.

If you’re outside the EU, this may still feel remote. It shouldn’t. Every market with an active in-app-payment debate is watching the same film, just earlier in the reel. Regulation can force a door open. Who writes the price list on the other side of that door is an entirely separate fight, and the last two years have been a demonstration of exactly that.

So run your own numbers. Does moving to one of the new distribution paths actually pencil out for you? Or do you check the math and stay put? If the honest answer for most developers is still the second one, then the DMA is a regulation that’s succeeded at about half of what it set out to do.