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.
Apple's intentional crippling of Mobile Safari
31–40 of 343 posts
Re: Apple's intentional crippling of Mobile Safari
#32Absolutely 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.
Does android still give you a push notification to dismiss whenever you take a screenshot?
Re: Apple's intentional crippling of Mobile Safari
#33Gotta 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
Re: Apple's intentional crippling of Mobile Safari
#34To be fair, some of these features are security issues some users don’t want to have in their browser.
Re: Apple's intentional crippling of Mobile Safari
#35I 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.
Re: Apple's intentional crippling of Mobile Safari
#36Used 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.
> if you ignore all the crypto spam
you can disable all those "features"
Re: Apple's intentional crippling of Mobile Safari
#37It 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.
Re: Apple's intentional crippling of Mobile Safari
#38Worth 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.
Firefox was planning a native gecko based ios app. But Apple decided to limit it to EU forcing developers to choose to maintain seperate projects for a limited users.
Re: Apple's intentional crippling of Mobile Safari
#39I'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. * Vibration * Background Sync * Bluetooth * NFC * Notifications * Web Push
I can understand notifications and vibration.
But why not Bluetooth or NFC? I can’t imagine any way those could be annoyances, or even why websites would want them outside of some extremely specialized applications.
Re: Apple's intentional crippling of Mobile Safari
#40I'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. * Vibration * Background Sync * Bluetooth * NFC * Notifications * Web Push
Yeah, I see that list of disabled features as being a feature in and of itself.