|
|
|
|
|
by shuckles
1001 days ago
|
|
Being the vanguard? Usage based pricing is not new, and framework makers have charged developers for access for a long time. Making an API public, even if the necessary code runs entirely on-device, is not free. It incurs immense upfront and perpetual R&D costs. Apple has spent the last three releases trying to slowly fix privacy issues with API as basic as copy and paste. The digital markets act is about facilitating competing entrants to “essential platform services.” Charging for the Apple technology those entrants use would not be inconsistent with its aims. A developer could use their own UI framework that draws straight to the window server itself! And maybe use some of that famous Android audio processing software! |
|
Sorry, that's like saying the Apple Developer program fulfills the DMA qualifications because it's not "inconsistent with it's aims".
Apple is of course welcome to try any of these things; nothing stops them as a private business. They failed to defend the mandatory value of the App Store in Europe though, so I fail to see how they could defend an arbitrary charge on other API calls. Apple quite literally cannot call Europe's bluff - that's what my original upstream comment was about in the first place. You can talk confident smack about Apple's talent in the pissing contest, but none of that means anything when the capitalist leash gets tugged and the alternative is losing money.
There is not a single value Apple holds that they would not forgo for money.