4 ms·
Unfortunately, Apple refuses to implement basic features into Safari that Chrome and Firefox have supported for a while, and they refuse to allow developers to
by heavyset_go 6y ago
Unfortunately, Apple refuses to implement basic features into Safari that Chrome and Firefox have supported for a while, and they refuse to allow developers to use browser engines other than the embedded Safari on iOS. This forces developers to release iOS apps if they want to target iOS users.
What we need is some anti-trust litigation with teeth.
- zepto 6y agoWhat features?
- jedberg 6y agoNotifications is the big one. Only way to push a notification to a user on iOS is to have an app (even through Safari on desktop supports notifications).
- zepto 6y agoWeb notifications aren’t power efficient the way APNS notifications are. That’s why it’s easy to build support for it on Desktop safari but not iOS. I except they’ll support Web notifications on iOS once the technology is mature enough to meet the power budget.
- swiley 6y agoweb notifications work exactly the same way APNS do. If OS vendors are reasonable and expose the APIs needed to use them efficently that is.
- zepto 6y agoThis is not correct. Web push notifications rely on running a persistent service worker in a JavaScript runtime, which is not anything at all like how they are received by native iOS Apps. Additionally with iOS apps, Apple can and does work directly with developers whose apps are overusing the notification system and draining power, which they cannot do with arbitrary web apps.
- dzhiurgis 6y ago> What we need is some anti-trust litigation with teeth. Indeed. We need big tech to divest some of their eye watering profits into actual user support. With so much depending on tech, kicking out users at a whimsical ML bit flip can be super damaging.