I've seen claims that Safari's limits on iOS and iPadOS make web apps less competitive with native apps. Is that mainly about App Store revenue, or are there good technical reasons for the missing features?
Is Apple holding back web apps on iOS to protect the App Store?
Answers
The App Store gives Apple a financial incentive to favor native apps, and limited web capabilities can make those apps the more practical choice. That's a competition concern worth scrutinizing, even if the incentive alone doesn't prove why any particular feature is missing.
For developers, the practical issue is that a web app may need extra workarounds or a native companion to offer the experience they want on Apple devices. More choice of browser engines could help, though allowing alternatives on paper doesn't guarantee developers will release them.
Reply to this answer
A missing feature list isn't proof of deliberate sabotage. Some proposed web APIs raise real concerns about security, privacy, fingerprinting, or battery use. Mozilla has also declined to ship some hardware APIs, including Web Bluetooth, so this isn't always Apple against everyone else.
I'd look at each feature separately. Is it a broadly supported standard, or mainly implemented in one browser engine? What risks does it introduce, and could permissions or other safeguards address them? Counting every Chrome feature that Safari lacks as a defect skips those questions.
Reply to this answer
There's also a usability issue that's separate from the argument over hardware APIs. Installing a web app and relying on it offline should feel straightforward. Storage eviction can be a particular worry for local-first tools if users expect their data to stay on the device.
For anything built around offline storage, check the current Safari behavior and test the installed and browser-tab cases separately. Don't assume local storage is a permanent backup.
Reply to this answer
Browser diversity cuts both ways here. People should have meaningful choices on their devices, but a web where one engine's feature set becomes the default has its own risks. Safari and other independent engines can push back on APIs they consider unsafe without every omission being anti-competitive.
Reply to this answer
Not everyone wants web apps to replace native apps anyway. Native apps can be a better fit for some experiences, and App Store revenue also goes to developers, not just Apple. The question is whether developers and users have a fair choice between those models.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_n83!zavdeli.4:
Permissions might help with some risks, but the fact that an API asks permission doesn't automatically settle the privacy or security question.