I'm writing this in Safari now, I'm a huge fan. There are several "features" that I actively dislike and disable in other browsers. I wonder if not being implemented in mobile safari is preventing them from being required in some webpages.
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.
Some people feel just as passionate about OS-level notifications and location permissions, and they turn them off. You can turn them off in your browser's settings as well. You'll be okay.
Used to have Firefox as a content filter for Safari on iOS (adblocking), but have since switched to Brave. It's a great option if you ignore all the crypto spam.
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).
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.
Author here. I have no affiliation with Chrome, and use Zen and Firefox Mobile pretty much exclusively. I recently made an ESP32 hardware side project that I can configure entirely in the web browser via Web Bluetooth, got hyped, then immediately sad that my page was never going to work on iOS / iPad OS. So I threw together this webpage from caniuse.com data.
No average person cares about your side project, and most people prefer Apple’s product decisions over the ones you’d like them to make. Based on your history with technology, you are a Windows developer who would like to distribute apps on Apple’s platform without learning about what makes for a great app on that platform.
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.
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.
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.
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.
To be honest, I'm really surprised they let PWAs have notifications. That's literally the only use case we have on that entire page and it actually works.
Gotta meet your audience where they are. As a Mobile Safari user, the foremost way I feel my use of the web is crippled is that pages assume a bigger screen or are just poorly arranged.
This of all web pages ought to be easy to read on an iPhone screen, but the way it's constructed prevents it. You can't zoom the whole page out to see the entire table width because the table is in a scrolling frame and wider than its box. You can only scroll the nested frame sideways to see how row labels relate to iPhone cells. If you give up and use landscape, it still scrolls vertically in its frame. You have to aim for the margin or else you'll scroll just an inch and be halted because you caught the table.
Because it's critical that the web be as free as it is:
• It's natural that some pages turn out like this
• So it's natural the web is a little bit shitty all over
• So it's natural the demand for richer web features is low
I recently posted about how I refuse to buy apple products because of stuff like this. The lock in has made iPhone users dependent on a app ecosystem when we could have had most of our functionality through the open web.
People saying they don't want these features are missing the point. Its about control and if developers have the option to make something as a website that actually works that gives them less incentive to make an app that apple can take 30% of your profit from while you are forced to write in their proprietary language for the stuff that only works on their devices.
So much engineering duplication of effort and waste just to satisfy a bottom line.
It would be useful if the site listed whether these had been standardized outside of Chrome yet.
It’s hard to delineate which of these are Chrome features or actual web standards. And it’s therefore hard to blame either Safari or Firefox for not supporting them if they’re not standardized yet.
I would gladly give up all those “features” to use Safari over Chrome on Android. I don’t even know what kind of dumbass on Hacker News voluntarily raw dogs the internet on Chrome Android. Pathetic that Safari has had extension support for multiple years now while Chrome is still ass.
I argue that developers enable the egregious behaviour by supporting safari in the first place. Just as IE was called out and shunned for its shenanigans, before they started behaving better, so too does safari need to be treated. However, it does also feel too late, they have crippled other browsers too with their platform abuse masquerading as requirements while we celebrated it.
66 comments
[ 2.9 ms ] story [ 67.2 ms ] thread* Vibration
* Background Sync
* Bluetooth
* NFC
* Notifications
* Web Push
Keep going Apple.
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.
It infuriates me a lot more than all the liquid glass stuff (on which I’m neutral overall).
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.
Chrome APIs and Electron crap, and then everyone complains about Microsoft.
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.
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.
This of all web pages ought to be easy to read on an iPhone screen, but the way it's constructed prevents it. You can't zoom the whole page out to see the entire table width because the table is in a scrolling frame and wider than its box. You can only scroll the nested frame sideways to see how row labels relate to iPhone cells. If you give up and use landscape, it still scrolls vertically in its frame. You have to aim for the margin or else you'll scroll just an inch and be halted because you caught the table.
Because it's critical that the web be as free as it is:
• It's natural that some pages turn out like this
• So it's natural the web is a little bit shitty all over
• So it's natural the demand for richer web features is low
People saying they don't want these features are missing the point. Its about control and if developers have the option to make something as a website that actually works that gives them less incentive to make an app that apple can take 30% of your profit from while you are forced to write in their proprietary language for the stuff that only works on their devices.
So much engineering duplication of effort and waste just to satisfy a bottom line.
It’s hard to delineate which of these are Chrome features or actual web standards. And it’s therefore hard to blame either Safari or Firefox for not supporting them if they’re not standardized yet.