Does Apple deserve a piece of the action for every instruction executed on iPhone?
They've allowed web to go untaxed. Kind of.
There are web standards for accessing more of the device that they've ignored and have chosen to treat differently. Maybe a judge should tell them they're not allowed to have a browser if they're going to treat apps differently.
They've corralled 50% of Americans into their bubble, and they're telling businesses to get in the correct lane to access them.
> There are standards for accessing more of the device that they've ignored and have chosen to treat differently.
Developers who have signed Apple's developer agreement and utilised the libraries/APIs are being held to the terms laid out in that agreement.
A website is a website.
Whether you agree or disagree with how Apple has chosen to operate their iOS ecosystem—again, I believe that reasonable people can disagree—it's certainly not unlawful for Apple to distinguish between developers who rely on Apple's work (SwiftUI, Metal APIs, etc) and developers who publish web pages with open standards without any involvement by Apple.
The context of this discussion is government commissions putting pressure on Apple to revise their policies "or else".
Developer agreements and rules being unlawful or not doesn't seem to me to be a relevant framing here. One of the party can basically change the law if it goes against common sense or society's wellbeing.
To be clear, what you're advocating for is the nationalisation (internationalisation?) of Apple's intellectual property as a reward for building a very successful product.
I'm not saying this isn't a valid opinion to hold—I'm not necessarily opposed to nationalisation in other contexts—but I just wanted to make sure you were aware of what your opinion entailed.
It was a regression to go from a world where we could repair and freely install to one where we could do neither.
It's further mired by the fact that Apple went from less than 10% market share to over 50%.
As consumers, we can't repair our devices or run the software we want to on them.
As small businesses, we can't ship software the way we want to anymore. It has to be in the form of an app to reach the target audience. We're audited, policed, and taxed. This isn't for some niche hobby or market - this is the primary form of computing for most Americans. We have to waste effort to develop applications twice because reasons, and we're treated like dog shit all the while.
Both sides of the coin suck, and the 800 lb gorilla in the room isn't going away. It feels like we woke up in bizarro world, because this shouldn't have ever become the status quo.
We are not talking about forcing them to GPL their OS or publish their API sources, or even allow uses of whatever they invented outside of their system.
Just "don't prohibit app devs from putting links to external web pages".
> Does Apple deserve a piece of the action for every instruction executed on iPhone?
"Deserve" is an entirely subjective question to which reasonable people can honestly disagree. To which reasonable people can express differences in degrees or in the margins.
The law (currently) says yes.
• If you write code that embeds or hooks directly into GPL libraries/APIs, then the FSF would insist that your creation inherits responsibilities under the GPL license and must be made available under a compatible license. In a sense, the open source community gets "a piece of the action".
• If you write code for distribution on a PlayStation, Sony would insist that you comply with the license terms associated with their developer agreement. Sony gets "a piece of the action".
• If you write code that relies on material supplied to you through the Apple developer agreement, if your app hooks directly into Apple iOS libraries/APIs, then Apple Inc says that distributing this software must be done in compliance with the license terms you agreed to under the Apple developer agreement.
1 and 3 seem to hinge on the ideas reimplementing apis is impossible without infringing on copyright for which google v oracle has already shown this isn't the case. For 1 whether dynamic linking counts is also still an unclear topic but still not relevant for the API portion. There is also the point that "and we limit the only way you can do anything on our device is via this licensed path" is different than "and these are licensed paths". Similarly it may be more steps but it still doesn't change that it's a forced contract to work on a device at all regardless if that's a direct decree or a forced path.
2 is a semi reasonable comparison but "and x does it" isn't proof "and therefore y is right". It could be that both x and y are wrong and y was just challenged first due to prevalence or that y is subtly different than x.
Google vs Oracle answered a very different question. In that case, it was ultimately determined that Google could mimic an API in their own code, when building their own independent work-alike system.
Whereas in the case of iOS applications, developers are agreeing to the Apple developer agreement and then directly embedding and/or linking to Apple intellectual property when compiling their binaries.
--
As for the analogy I made to the GPL, this was only to demonstrate that the open source community also leverages the enforceability of license agreements to require developers who use GPL code in a certain way to comply with community expectations. It's the same legal principle, even though it's used to very different effect.
They've allowed web to go untaxed. Kind of.
There are web standards for accessing more of the device that they've ignored and have chosen to treat differently. Maybe a judge should tell them they're not allowed to have a browser if they're going to treat apps differently.
They've corralled 50% of Americans into their bubble, and they're telling businesses to get in the correct lane to access them.