11 ms·
> (Conversely, if Safari refuses to implement some alleged 'feature', it becomes much less useful even if Chrome does implement it.) The fact that Apple refuse
by heavyset_go 6y ago
> (Conversely, if Safari refuses to implement some alleged 'feature', it becomes much less useful even if Chrome does implement it.)
The fact that Apple refuses to implement basic features in mobile Safari that Firefox and Chrome have had for years now, and the fact that they refuse to allow other browser engines on iOS is the reason why we can't have nice things like progressive web apps.
I recently worked on a health app related to the COVID pandemic. The most common use case would be served really well by a PWA, and as such, there's no reason users would need to install an app on their phones to access the web app's full set of features.
Despite the web app working perfectly on Android and across Windows, Linux and macOS without native integration, we now must dedicate time and resources to develop an additional iOS app just so iOS users, which over half of Americans are, aren't left out.
This is an expensive endeavor time-wise and money-wise, during a pandemic where time is of the essence and resources are stretched thin. It shouldn't be this way, but it is.
- chrisseaton 6y agoWhat is Safari on iOS missing specifically?
- jdauriemma 6y agoProgressive Web Apps
- chrisseaton 6y agoBut what exactly? Wikipedia says it does support it https://en.m.wikipedia.org/wiki/Progressive_web_application https://en.m.wikipedia.org/wiki/Progressive_web_application: And I know I’ve written Progressive apps for iOS myself - manifests etc. So I know it’s not as simple as you’re saying. What do you really mean?
- jdauriemma 6y agoSafari absolutely does not support PWAs in a meaningful way when compared with other platforms. Service Worker support is fine, but one of its main features is its use in combination with the Push API, which is not supported in Safari. This omitted feature alone alone makes web apps on iOS far less valuable than native apps. There are other omissions as well, but this one in the most glaring.
- heavyset_go 6y agoFor this specific use case, it's missing the Web Push API[1], which can be used to implement push notifications, and the Web Notification API[2], which can also be used for the same thing. [1] https://developer.mozilla.org/en-US/docs/Web/API/Push_API https://developer.mozilla.org/en-US/docs/Web/API/Push_API [2] https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API https://developer.mozilla.org/en-US/docs/Web/API/Notificatio...
- chrisseaton 6y agoIsn’t the entire point of progressive web apps that they’re tolerant of different features being available or not? That’s ‘progressive enhancement’. Your app is supposed to work if the functionality isn’t there, or equally if it’s there but denied access. You can have it show updates when the user checks the app if that’s what they want. Complaining a browser doesn’t support a progressive feature is a contradiction in terms!
- heavyset_go 6y agoIt works, but users don't get the notifications they sign up for and expect without using a native app on iOS.
- chrisseaton 6y agoRight... isn’t that the whole point of progressive web apps? Users get as many features as their browser supports or they permit? That’s the point. If your app doesn’t work like that then it’s not progressive... so you can’t complain it doesn’t support your progressive app because it’s not progressive.
- heavyset_go 6y agoTry explaining to users that the feature they want and expect doesn't work for them because their particular browser doesn't support it, despite it working on every other browser and platform. The only solution I see is telling users to "use the app", which doesn't exist yet.
- fragile_frogs 6y agoWeb Push Notifications, ShardeWorker, BroadcastChannel. Native Add to Homescreen, Good Developer tools to debug things on a non Apple computer, Background Sync, Notification Badging API, App Shortcuts These are only the ones that I remember right now, but I know there is more
- olliej 6y agoweb push notifications, notification badging, shared worker, etc are user hostile features. They burn battery life, the former two exist almost solely to spam users (Mozilla did a study and it turns out no one wants notifications from random websites). Safari has had add to home screen for the best part of a decade. Giving web pages the ability to spam users to add it is an anti feature.
- fragile_frogs 6y ago> Safari has had add to home screen for the best part of a decade On Chrome you can trigger a add to home screen prompt from your own UI, making it a two touch experience. On iOS IIRC it only works on Safari and not in Chrome, but I could be wrong. > no one wants notifications from random websites I am not talking about random websites, but rather web applications that you interact with on regular basis, if Apple cared about the user experience they could have just moved the notification prompt behind a user interaction. > shared worker ... They burn battery life If you are building more demanding websites shared workers are a great way to share state and computing resources across and thus saving battery life. Spawing a Worker per tab is more demanding.
- ksec 6y agoHow about Web Push Notifications that only works in sort of a PWA mode once it is added to Home Screen?
- saurik 6y agoIn addition to the issues other people are bringing up, there are a ton of decentralized video use cases crippled by the lack of Media Source Extensions on iPhone (they finally I think decided to deign to include it on iPad, just not iPhone).
- userbinator 6y agoThe more I see posts like this that complain about other browsers lacking features and essentially encouraging the "Google-isation" of browsers, the more convinced I am of the power of Google's gigantic monopoly-enhancing propaganda-machine. Firefox unfortunately has no choice but to be dragged along by Google.
- heavyset_go 6y agoI'm a mobile and desktop Firefox user, and Firefox has supported the features that are missing from iOS Safari like the Web Notifications API since 2013, and the Web Push API since January 2016.
- nexuist 6y agoiOS dev since 2014 here. So many of my app ideas would have been completed 2-5x quicker if mobile Safari supported push notifications. It is unreasonable gatekeeping.
- diebeforei485 6y agoIt is very reasonable gatekeeping. People would be inundated with notifications on their phones.
- saurik 6y agoNo: you would--at worst--be asked more often than you would like to approve notifications for random websites, all of which you would click no on; this feature doesn't just magically cause notifications... hell: it already even exists on desktop Safari and I just click "no".
- ArchOversight 6y agoYeah, having to click no all the time on desktop Safari is terrible. Also websites have realized that I am going to click No in the browser, so now they popup first asking if I want to allow push notifications in JavaScript so when I click no, they can ask me again later, vs if they popped up the browser and got a "No" there they could never ask me again.
- jojobas 6y agoThe answer is to make the nice things and force Apple to implement them lest its user feel left behind.
- heavyset_go 6y agoI agree with the sentiment, but the real result of that would have sick people punished for the wrong choice of phone.
- jojobas 6y agoYou choose crap you lose, always been like that. Refusing nice things to those choosing (more) open platform so as not to punish them makes no sense.
- katbyte 6y agoOr you just send them a text?
- heavyset_go 6y agoWe already do texts and emails[1]. Users wanted desktop and mobile notifications, as well. [1] https://news.ycombinator.com/item?id=26520303 https://news.ycombinator.com/item?id=26520303
- Google234 6y agoI don’t want websites to be able to send notifications to my phone. Sites abuses this and are always asking on my computer and it’s too easy to accidentally say accept.
- heavyset_go 6y ago> I don’t want websites to be able to send notifications to my phone. You might not, but our users requested desktop and mobile notifications. The notifications let sick patients know when their prescriptions are ready, facilitate care-provider check ups, etc.
- Google234 6y agoHave those users download some simple app if this is so important to them. Or let them enter their phone number to get more reliable text notifications. Just because you have a good use doesn’t outweigh the all the bad abuse.
- cforrester 6y ago> Just because you have a good use doesn’t outweigh the all the bad abuse. Personally, this is how I feel about downloading apps to my phone for every individual service and product. I see no need to download a separate app for each individual service I'm interested in, as the potential for abuse is higher than getting the occasional notification from my browser app and visiting their website. However, it sounds to me like the focus should be on minimizing the potential for any avenue of information delivery to be abused, not to remove or decline to add features for fear that they will be. From the user side, I'm not interested in being told by a developer, "download my app if it's so important to you." I'd probably never discover how useful a service can be if I would have to download another app to try it. From the developer side, I'm not interested in telling potential users, "you actually don't want that feature."
- Google234 6y ago99% of apps you download aren’t spam unlike the 99% of web notification requests that are spanmy
- irrational 6y agoHalf of Americans use an iPhone? Is that true?
- simonebrunozzi 6y ago~47% [0]. [0]: https://www.statista.com/statistics/236550/percentage-of-us-population-that-own-a-iphone-smartphone/ https://www.statista.com/statistics/236550/percentage-of-us-...
- bouke 6y agoI’d say being able to target 50% of your market with a single codebase/binary isn’t a bad investment.
- Anktionaer 6y agoI don't get that, why not just not support safari if they intentionally make it difficult?
- djxfade 6y agoBecause Safari has like 50+ percent of the mobile market share in the west
- heavyset_go 6y agoBecause we don't think it's fair that sick people can't access the care they need because they have the wrong phone or tablet.
- tobr 6y agoIf your progressive web app stops working because the browser is missing a feature, by definition you have not built a progressive app. It’s supposed to work everywhere, with progressive enhancements if platform features are available.
- enumjorge 6y agoThe parent comment didn’t say their PWA stops working on Safari, only that it doesn’t have a full set of features on it. For some applications, features like push notifications are essential.
- tobr 6y agoThey said Safari is > the reason why we can't have nice things like progressive web apps I.e. implying that progressive web apps are only possible if a specific set of features are supported everywhere. It’s like saying that accessibility is only possible if no users have disabilities.
- merdadicapra 6y agoYou're overthinking it. It's the other way around. Apple is saying that the only way to make secure software is remove features that they don't want or don't know how to implement in a secure way. It's like saying that cars are safer if you remove the wheels. In your analogy, you are implying that progressive web apps are possible only if they support the smaller set of shared features among all the vendors. Meaning that a single actor can ruin the game for everybody else. I think that if a vendor is the only one refusing to support something that is common everywhere else, it's the vendor that is at fault, not the developer.
- africanboy 6y agoI think OP is implying that if Safari is the only one lacking a feature that is part of the W3C standard[1], Safari is at fault. [1] https://www.w3.org/TR/push-api/ https://www.w3.org/TR/push-api/
- krzyk 6y agoProgressive web apps is not a feature. It is one of the worst bugs a browser can have. It is almost Electron level bad.
- intricatedetail 6y agoThis is another example of Apple anti competitive and anti consumer behaviour and regulators should start to look into it. Unfortunately Apple managed to amass so much wealth through various tricks and loopholes, they are now in position to buy any regulation they want and probably that's why they are allowed to continue with these practices.
- fragile_frogs 6y agoI wouldn't care about what Safari is doing if iOS would allow you to install browsers that are not based on webkit. The fact that Apple only allows webkit browser makes it so much worse and means that no one can compete on iOS against Apple
- GekkePrutser 6y agoYeah it's strange because PWAs were Apple's original plan for iOS apps :)They didn't yet exist under the PWA name but this was definitely what they were aiming at. But Safari will never be a serious option for me. I want the same browser on all my systems and I use a lot more than Mac and iOS. So Firefox it is.
- heavyset_go 6y agoI still remember the early days of iOS and webOS via Palm and HP, and now LG. We had HTML/CSS/JS powered mobile apps available on the Palm Pre in 2009, and it was pretty great.
- Klwohu 6y agoSome "features" are harmful to the users and only exist for the convenience of Google and other data mining and spying companies.
- busymom0 6y ago> and the fact that they refuse to allow other browser engines on iOS is the reason why we can't have nice things like progressive web apps. Is that against the App Store guidelines? Or is that a programming limitation? I am aware all the iOS browsers are just a wrapper around WKWebView but am curious why another engine can't be implemented.