Another example is Apple's privileged access to your wifi credentials. Basically this means if you want to share wifi access via your app, as you might want to do in setting up an IoT device, this is only possible if you enter Apple's expensive MFI program.
So in other words, to have a seamless and competitive IoT hardware setup process, you essentially have to enter an agreement with Apple which involves giving them a percentage of your overall hardware sales revenue on MFI devices.
Let me pose it to you this way: if you are developing an IoT product, the only way to have a UX competitive with Apple's own offerings is to pay them a toll on every device you sell. In return, you get a couple dozen bytes of data Apple prevents other apps from accessing.
Does that sound like anti-trust regulation is operating as it should?
The browser for me is still an issue. I know the question is more broad, but if Firefox could run natively on iOS, I’d feel substantially better about Apple’s promise to be more privacy-oriented. I don’t expect their platform to have zero telemetry, but it is larger projects like this that speak volumes to me because that indicates they at least entertain the notion of privacy for people who care enough to try to opt out of tracking (versus the many many individuals who are unaware or don’t care).
This is primarily for privacy and security reasons. One wouldn't want a funny casino app, or the likes of Google or Facebook to hijack people's web access.
Another aspect is the user experience - a piece of web content will render exactly the same way anywhere on the system. There is no need for people to be concerned with webapps asking absurd things like "Download browser X to view this page".
A third aspect is actually very helpful to developers - you can count on 100% of the APIs you intent to use being available on the system's web browser, creating in-app experiences significantly easier (and cheaper) to develop.
This would still be true in the case where external web browsers were allowed - you can still rely on Webkit being available on all phones, but if you need access to APIs not provided by apple you can revert to bundling a different browser engine
I doubt all the Chromium clones would evenly support "normal" iOS integrations, and the ability to (privately) deal with, for example, universal links, App Clips, or even that banner offering a website visitor to use the native app.
I understand the sentiment for wanting to use custom features on desktop, but a phone needs to be much more reliable than this - you can't have something working "sometimes" or for users to have to retry or change settings on the go. Imagine a stressful situation at the airport, and the app you are using needs you to switch browsers or download another app to work...
This is something that works just fine for me over on Android, in Firefox mobile. Actually, i assume that the mobile browsers would offer all of these capabilities, assuming apple allows access to, and documents their apis appropriately.
Why is it that we somehow defend apple having proprietary/exclusive Apis that nobody else has as good? It's essentially the same game as it was with internet explorer.
I think if apple just opened up their eco system the other browsers would support these features before long, or app developers would include them in their apps instead of relying on browsers.
It's not like apple is the only one with capable engineers, they just stop everyone else from using their stuff to the fullest
But then... folks will complain that some apps open content in Safari and not their preferred browser.
So we don't buy this as an excuse when government use it to justify searching your house without probable cause or silencing dissent.
But when a private company uses same excuse, somehow are we cool with it?
At this time there is but one of the FAANG(M) companies that has no commercial use for user data. This is Apple. You can see this reflected well in their products where we see hardware and software services that prioritise on-device processing + strict regulation for app developers not to abuse user trust.
But then Apple has apps that can do much more than everyone else has access to, in ways that have nothing to do with security or privacy.
- Apps access to NFC (e.g Apple Pay vs you being able to make your own nfc card)
- Inability to have non WKWebView type browsers. Safari can do the one it wants, which is Apples choice.
- Health app has access to nicer push notifications than standard
- Federated Identity type login only works with Apple. So login with Apple is built tightly into the OS, where you can't make an app that does that.
- Wallet app can access 2FA SMS code without having to type it
The list is much longer but it is not a level playing field with regards to the access to apis. If Apple has an app like Messages, other apps should be able to access the same things too.
I pretty much couldn't care less about the app store and review process, but the asymmetric access to APIs really helps Apple cement their moat (e.g with iMessage, Wallet), basically any app where they do it has serious market power.