Live data from Hacker News

Apple's intentional crippling of Mobile Safari

pwa.gripe

11–20 of 343 posts

Re: Apple's intentional crippling of Mobile Safari

#11

Frankly I am very happy indeed for Apple to "cripple" Safari. 99.9% of the things listed in that stupid table in the blog just stink of being potential attack vectors. And we know just how heavily smartphones are targeted and how smart and sneaky some of the latest vectors are.

Related: Firefox stance on Google's web proposals: https://mozilla.github.io/standards-positions/

Re: Apple's intentional crippling of Mobile Safari

#13
post #3

Yeah sorry but as an end user I’d rather have an actual app than some PWA thanks. Keep going Apple.

This is the first time I've actually heard the opinion that someone thinks we need more apps instead of more functional websites.

I think it reflects the general HN sentiment that native apps > progressive web apps.

Re: Apple's intentional crippling of Mobile Safari

#15
post #6

Imagine if these countless of "Safari bad" sites didn't shill for Chrome by pretending that Chrome-only APIs are essential and standard web apis.

> Chrome by pretending that Chrome-only APIs are essential and standard web apis

Reminds me of the days when all the corporate coders thought the IE apis were the only ones worth using.

So if you accessed $megacorp website on a non-IE browser it was your fault for not using IE and not their fault for failing interop.

Re: Apple's intentional crippling of Mobile Safari

#16
As a daily Safari on iOS user, I don’t care about any of this, but since iOS 26 basic Safari features such as bookmarks and text search have become so buried deep underneath, they are basically unusable at this point.

It infuriates me a lot more than all the liquid glass stuff (on which I’m neutral overall).

Re: Apple's intentional crippling of Mobile Safari

#17
post #6

Imagine if these countless of "Safari bad" sites didn't shill for Chrome by pretending that Chrome-only APIs are essential and standard web apis.

I noticed how they've marked the features that only Chrome supports (e.g. installation) but not the feature that only Firefox supports (orientation).

(tbh I don't know if the list is simply Chrome-centric or if there's a good reason behind, but it struck me as interesting)

Re: Apple's intentional crippling of Mobile Safari

#18
post #3

Yeah sorry but as an end user I’d rather have an actual app than some PWA thanks. Keep going Apple.

This is the first time I've actually heard the opinion that someone thinks we need more apps instead of more functional websites.

Functional websites would be wonderful.

Instead we get “webapps”.

Re: Apple's intentional crippling of Mobile Safari

#19

As a daily Safari on iOS user, I don’t care about any of this, but since iOS 26 basic Safari features such as bookmarks and text search have become so buried deep underneath, they are basically unusable at this point. It infuriates me a lot more than all the liquid glass stuff (on which I’m neutral overall).

Yes. "Add to homescreen" is in the "Share" menu.

That's where they burry all bodies.

Re: Apple's intentional crippling of Mobile Safari

#20
I'm not sure the other commenters claiming all these features are attack vectors actually read the list?

How is the barcode detection API a security risk for example? Having it implemented would be amazing for web apps.

Also there's features like deep linking into PWAs that ought to be pretty basic PWA functionality that's not on this list that even Safari on Mac OSX has but Safari on iOS doesn't. Even the add to home screen menu option is deliberately made hard to find.

Apple doing this for the benefit of the user is one of the less likely hypotheses.

Post reply on HN