Re:Tim Cook’s Fortnite trial testimony was unexpectedly reve...
by hnlmorg on Sunday May 23, 2021 @06:59PM
(#27259412)
> Their point is that Apple could charge based on bandwidth used, and that this could be more fair for some developers.
That is what the 30% cut is meant to cover (amongst other things too). Like with a high street retail store, the mark up is intended to cover the running costs of the store. Which brings us full circle to why Apple deduct it from transactions.
Sure you "could" have an App Store that calculates the operational costs and then charges it to the developer, but you then potentially destroy the free app market (and contrary to what people often say about the App Store, there are a lot of decent free apps on there).
Having a split payment and billing system also adds complexity to invoicing. Did you know that AWS and other cloud providers don't provide credits and refunds as payments into the customers bank accounts? No, what they do is they offset your costs against your credits and invoice the difference if owed to AWS. If Apple were to adopt that then we'd basically be back at deducting $n from transactions again. And once again we've come full circle.
There is so many arguments about what Apple "could" do but when you start to distil the requirements down to a workable operation you almost always end up right back at the status quo.
Now I'm not saying that Apple aren't taking advantage of developers either. The cost of development on a Apples ecosystem is ridiculously high and Apple are notoriously hostile towards their developers too. But charging a percentage of transactions is a reasonable approach to the problems outlined above and limiting transactions outside of Apple's payment channel does at least solve the problem of developers cheating by funnelling funds in via a side channel (as exampled in an earlier comment which discussed people selling items on eBay for $1 but with a $49 shipping fee before eBay clamped down on exaggerated shipping fees).
That is what the 30% cut is meant to cover (amongst other things too). Like with a high street retail store, the mark up is intended to cover the running costs of the store. Which brings us full circle to why Apple deduct it from transactions.
Sure you "could" have an App Store that calculates the operational costs and then charges it to the developer, but you then potentially destroy the free app market (and contrary to what people often say about the App Store, there are a lot of decent free apps on there).
Having a split payment and billing system also adds complexity to invoicing. Did you know that AWS and other cloud providers don't provide credits and refunds as payments into the customers bank accounts? No, what they do is they offset your costs against your credits and invoice the difference if owed to AWS. If Apple were to adopt that then we'd basically be back at deducting $n from transactions again. And once again we've come full circle.
There is so many arguments about what Apple "could" do but when you start to distil the requirements down to a workable operation you almost always end up right back at the status quo.
Now I'm not saying that Apple aren't taking advantage of developers either. The cost of development on a Apples ecosystem is ridiculously high and Apple are notoriously hostile towards their developers too. But charging a percentage of transactions is a reasonable approach to the problems outlined above and limiting transactions outside of Apple's payment channel does at least solve the problem of developers cheating by funnelling funds in via a side channel (as exampled in an earlier comment which discussed people selling items on eBay for $1 but with a $49 shipping fee before eBay clamped down on exaggerated shipping fees).