> So Apple will be collecting 27% (instead of 30%) for... what exactly?
Off the top of my head...
- Bandwidth
- Running the App Store for users
- Marketing the App Store
- App review
- Security efforts to keep malware off the store
- Making App Store optimisation tools for developers
There's a lot of moving parts to this. You could argue that none of this is necessary if you sideload, but distribution is worth a lot in general to businesses, and I think it's clear that the App Store is a good distribution channel in many ways – easy to use for sellers (vs via traditional publishers, or physical retail), and easy to use for buyers.
If that's true (and I even believe that it is to a large extent!), there should be no problem for Apple to let its value proposition stand for itself and allow some competition.
Besides that, that list is very bundled. What if I e.g. want the convenient subscription payment processing, but want to (or need to) bring my own CDN for most content? What if I want their marketing and am willing to pay for it, but prefer my own payment processing?
I agree, although I think this is doing that to some extent. Sure there's some scary text in the popup that I think could be toned down, but I'm not an expert, and to be fair there are risks going externally.
Allowing other app stores would be the big win in competition here, properly forcing Apple to win on value proposition. The DMA could force this, but I'm not certain about the details.
The scary text doesn't matter nearly as much as the fact that they are not unbundling anything. They are charging an effectively equal/higher fee for less services than developers would get from just sticking with in-app purchases.
It's an arguably quite sloppy illusion of competition/choice.
Digital distribution is much easier than burning discs, sending them to shops, etc. It's also not just the process but the visibility, a million tiny storefronts will be much harder for users to browse and likely result in fewer overall sales, than one massive storefront.
I get that there's no competition on iOS, but I was comparing to other ecosystems and mechanisms.
> So basically nothing that companies couldn't do themselves if Apple didn't explicitly block it. You pay 27% for fuck all.
No, you pay 27% for those services I mentioned. Those things aren't free if developers do them themselves. Developers may prefer to do some themselves because they think they can do them for cheaper, and in this case payments have been opened up so that there can be competition there – the DMA in the EU will do similar and I look forward to it.
You may disagree with the price (and I personally feel it's high), but these things cost real amounts of money to do. Not just this, but free app developers would also need to pay all these costs despite potentially having no revenue directly attributable to the app.
All of that can easily be funded by the margins Apple makes off device sales alone combined with the fees you pay to become a developer.
Even if for some reason you believe that's not true, there's no way they need 27% of all purchase revenue on the store to fund that stuff. The numbers simply don't check out. 30% was an arbitrary cut and that's why they can easily drop it to 27% or (for small devs as of recently) 15%.
In the situations we're discussing, both the app developer and every customer have already given apple hundreds if not thousands of dollars worth of revenue. Out of that, Apple has a healthy margin.
Now we're talking about Apple sticking their fingers into developers' pockets for every single transaction even if Apple's participation in that transaction is limited to updating a couple database rows to indicate that Customer XXXXX bought DLC Package YYYY in App ZZZZZ. There is simply no way that is worth 30%. They're not doing that much work.
Sure, all these things cost a lot of money. What if I would like to market, host, and distribute my own app, without any Apple involvement?
From my own experience, the app store brings negative value to both the users and the developers in many cases. It's most often seen not as the godsend like Apple portrays it, but as a stupid obstacle course that you need to clear every time you publish a new app or an update to an existing one, and sometimes even when you don't.
So charge a fee based on usage of the specific services then? Flat 30% of monthly subscriptions when they're not even providing the service of sending that audio and video to the device is insane.
I agree, but I also don't know what actually would be a fair price for either of these specific services.
The advantage of mandating alternative distribution channels (i.e. sideloading or alternative app stores, both with their own payments infrastructure) would be that it wouldn't be up to a regulator to figure that out – the market could decide.
> You can probably include development of SDKs and documentation as well.
With limited exceptions, platform vendors (Microsoft, IBM, Sun/Oracle, etc) are generally not in the business of paywalling their development documentation, tools, and SDKs, otherwise it makes their platform far less attactive to third-party developers that they absolutely need in order to.
...and ever and never-mind that Apple's documentation is sub-par[1], even with the billions of dollars they're raking in. It boggles the mind because nothing is stopping Apple from hiring the people it needs to ensure decent documentation and DX, which can be paid-for directly from the $99/yr developer membership fee.
My company's SaaS product used to have an iOS and Android app which we discontinued a couple of years ago when Safari finally started supporting more web-standards that enabled our PWA to more-or-less have parity with the old app (confession: our app was using Xamarin instead of being truly native, not that it mattered much).
...so with that context in-mind, we don't benefit from - nor really need at all, most of those services you're referring to;
> Bandwidth
We're a small B2B SaaS with a userbase sized under 100,000 users and our old app bundle was around ~20MB and updated a handful of times per year, so even if 100% of our users used the iOS app with auto-updates then that's less than 2GB of data-transfer per published update - the cost of serving that is far less than a rounding-error on AWS/Azure.
> Running the App Store for users
I accept that.
> Marketing the App Store
No-one should be paying for Apple to market their own App Store - and as a B2B SaaS app, Apple would never promote us or do marketing for us.
> App review
I also accept this - but ostensibly this is what your $99/yr developer fee pays for.
> Security efforts to keep malware off the store
This is the same thing as App review; if we look more broadly, then it's better to compare this to Microsoft's Windows Defender which is free, and is funded independently of the Microsoft App Store.
> Making App Store optimisation tools for developers
Again, this is Apple's responsibility to pay for, not ours - and even-then consider that efficient update/patch distribution systems have been around for decades so it's hardly cutting-edge development (e.g. those ~KB-sized binary diff patches for CD-installed games in the late-1990s when we were on dial-up, like EA had for SimCity 3000 or C&C Red Alert 2)
For a B2B SaaS client app for BYOD users the iOS App Store is perfectly fine as a distribution system, and morally I'm fine with paying Apple some kind of fee for the benefits of their distribution system, but Apple has no legitimate claim to any percentage of the subscription fees we get from our users - so what this means is that we can make our app available for free to our users (which is fine, honestly) but (as per my understanding of the rules) we cannot offer any kind of account-management or billing-management for their SaaS subscriptions from within the app which isn't ideal.
I think Apple's main mistake here was deciding that having a single set of rules and fee-schedules/commission/etc for everyone, because the revenue models for exploitative mobile games (especially their gold/gems IAPs) differs massively from my company's unimaginatively dry B2B SaaS client.
> I think Apple's main mistake here was deciding that having a single set of rules and fee-schedules/commission/etc for everyone
On the other hand, non-equal fees ironically seem to be exactly what's made US courts decide in favor of Apple but against Google in two superficially quite similar cases regarding app store fees:
I think the main mistake isn't the fixed percentage fee, but rather holding on to the golden goose that is an app store monopoly for too long.
Google has been providing sideloading since day one for example, and except for a few high-profile exceptions, people do genuinely seem to prefer the platform's native app store.
Apple always aims for total control and authority over everything: Their supply chain, the apps running on their systems, the devices allowed to interface with them – and while that obsession with keeping it as *their own platform
arguably is part of what makes their devices attractive, I think it won't keep working forever in this case.
Off the top of my head...
- Bandwidth
- Running the App Store for users
- Marketing the App Store
- App review
- Security efforts to keep malware off the store
- Making App Store optimisation tools for developers
There's a lot of moving parts to this. You could argue that none of this is necessary if you sideload, but distribution is worth a lot in general to businesses, and I think it's clear that the App Store is a good distribution channel in many ways – easy to use for sellers (vs via traditional publishers, or physical retail), and easy to use for buyers.