Live data from Hacker News

Apple's intentional crippling of Mobile Safari

pwa.gripe

21–30 of 343 posts

Re: Apple's intentional crippling of Mobile Safari

#22
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.

These are not features of functional websites, these are features that make every website an "app" and deprecate the idea of a traditional website. Google is embrace, extend, extinguishing the web as we know it. If Apple gives in, it's over, every website will just be an app and want access to your contacts, and your family history, and whether or not you are on Santa's naughty list or whatever.

Re: Apple's intentional crippling of Mobile Safari

#23
post #5

Absolutely nothing listed on that site as unsupported by Safari has any business being part of the web. In fact several supported APIs should be chucked too. Fuck giving websites motion data or push notifications.

They should just ban unsolicited prompts. That's it.

Push notifications are the #1 featured requests of my online community. Some even switched to Android over it.

And people don't understand adding sites to their homescreen, especially since Apple buried that feature in the Share menu.

No Android user of my website ever complained about the WebPush notifications.

Re: Apple's intentional crippling of Mobile Safari

#24
I very much appreciate the secure baseline Safari settles on. The entire ecosystem is protected by Safari being slow and reasonable.

My only peeve is that Apple resets the feature flags with every update. So the one experimental feature I use I have to reenable each and every time I get a phone update.

Re: Apple's intentional crippling of Mobile Safari

#25
Worth noting that Apple doesn't just cripple iOS Safari, it cripples all iOS browsers because it also forces them to use WebKit, the crippled browser engine underneath Safari.

It would be fine if they just made Safari bad, that's their choice. But they don't stop there: they make the entire web bad on iOS purposely to promote the native apps they can tax.

Re: Apple's intentional crippling of Mobile Safari

#26
post #25

Worth noting that Apple doesn't just cripple iOS Safari, it cripples all iOS browsers because it also forces them to use WebKit, the crippled browser engine underneath Safari. It would be fine if they just made Safari bad, that's their choice. But they don't stop there: they make the entire web bad on iOS purposely to promote the native apps they can tax.

[dead]

Re: Apple's intentional crippling of Mobile Safari

#28
How many of these features that chrome offers have been fully flushed out and in a true working stable state? Google Chrome has a habit of pushing features out before they're really ready and Safari is usually on par with Firefox for features from what I have seen.

Re: Apple's intentional crippling of Mobile Safari

#29
Like most people (at least on this thread). I’m okay with the vast majority of these things not supported in mobile safari. But man, Bluetooth would be nice. I often provision esp32 devices for various things and either I need an app or a laptop when my phone is perfectly capable.

Re: Apple's intentional crippling of Mobile Safari

#30
post #28

How many of these features that chrome offers have been fully flushed out and in a true working stable state? Google Chrome has a habit of pushing features out before they're really ready and Safari is usually on par with Firefox for features from what I have seen.

I’ll ask the dual question: how many of the mobile safari checkmarks are fully fleshed out? Media Session has a check, but I have absolutely fought obvious Media Session implementation bugs in my own PWAs when designing for mobile safari
Post reply on HN