Apple's iOS Web Restrictions
Comments criticize Apple for mandating WebKit as the sole browser engine on iOS, which limits support for modern web standards and progressive web apps to prevent competition with native App Store apps and protect revenue. Discussions highlight calls for allowing alternative engines like in the EU DMA to improve web competitiveness.
Activity Over Time
Top Contributors
Keywords
Sample Comments
The problem is not that Apple doesn't care enough about the Web. If they don't want to add features to Webkit, that's fine.The problem is that they prevent other browsers to add these features, because they prevent them from using their browser engines. That way, they prevent these browsers to really compete with theirs (Safari). Because if we could run the real Chrome on iOS, with all the APIs it supports, it's obvious everyone would ditch Safari straight away.And more
Apple is trying to tell you that the web browser is a second class citizen compared to native.Websites don't need to go through the App Store. No money in that for Apple. Hence, low priority.
Apple is actively sabotaging the web for a number of years now. They don't want web apps to be able to compete with native iOS apps.And they prohibit different browsers from the app store, so users don't even have a choice.
What incentive does Apple have to make the web browser on their iOS devices better?
Apple doesn't want webapps to replace their app store. That is why they gimp the hell out of Safari.
I think its good to force Apple to allow non-WebKit web engines on iOS. Right now Apple can forcefully cripple technologies like progressive web apps by not supporting the latest web technologies. This allows Apple to force companies to develop native applications.Similarly, Apple has been slacking off on improving Webkit and making it as good as V8. By getting rid of Apple's monopoly on web engines, developers will be able to push websites to new levels that are currently hard to attain
I think this is more an illustration of how Apple are intentionally trying to hobble web apps so they can continue to tax all transactions on the app store, than any kind of issue with web technology itself. If Apple implemented the necessary features and fixed the bugs, it could well be a strong alternative to a native app. But they make money from preventing that and are doing everything they can to prevent other browsers from implementing quality PWA support.
This is good news, the US should join in aswell in stopping this despicable behaviour by Apple. Apple handicaps browsers because web apps are the only viable alternative to Native Apps which generate huge commission for Apple.
Apple doesn't want the web to be a viable alternative to the app store. They'll continue to choose strategies that hold it back.
Nobody made such a claim.If you serve web pages, you likely serve many of your users on their Apple devices. And you can’t support features of the web for those users if Apple doesn’t want them to have those features, and prohibits browsers with other engines that do support them on their App Store, and prohibits other sources of web browsers.That’s called “gatekeeping”.