4 ms·
Chrome is implementing a standard that pretty much all other modern browsers are also implementing. For example, service workers - implemented by Chrome initial
by connorelsea 9y ago
Chrome is implementing a standard that pretty much all other modern browsers are also implementing. For example, service workers - implemented by Chrome initially and pretty heavily integrated into Android/PWAs - but Firefox and Safari are also shipping this feature currently. And also most features, such as service workers, can be effectively used with progressive enhancement, still providing a working experience to the user when they are using an older browser. Most sites I've seen that say "Must be used in Chrome" or whatever really have no reason to do that. There is more nuance to the progression of the modern web platform than the OP article gives off.
- RobertRoberts 9y agoSorry, the op is right. Safari IS the new IE. Service workers is one of the most egregious failures on their part. And I believe it's been done on purpose. With service workers you get full control over building your JS based app, something Apple does not want, they want everyone to got through their store. Considering that the only way (moving forward) to create an offline JS app now is through service workers, and Apple is just starting to get it working, _maybe_ for the next version of Safari. https://caniuse.com/#search=service%20workers https://caniuse.com/#search=service%20workers What does this mean? It means that it may take one or two more _years_ of _hardware_ updates to get iOS users able to use a javascript feature in their browser. As far as I know, iOS and Safari are knitted together like MS did to Windows and IE. Try and get a new version of Safari that doesn't match with the version of iOS you are running. I could go on about the state of local storage and other HTML5 debacles on Safari, but it's total loser and I am only going to make myself upset.
- mreid 9y agoAccording to this article Service Workers is on by default in the latest Safari Tech Preview: https://9to5mac.com/2017/12/20/safari-preview-46-service-workers/ https://9to5mac.com/2017/12/20/safari-preview-46-service-wor...
- RobertRoberts 9y agoYah, I keep tabs on that stuff. But most of my clients actually use Apple hardware for a few years now, and even if this update goes out tomorrow, and all iOS 11 users get it. iOS 10 users and below are out in the cold, and that accounts for 99% of my users. And you know what it's like trying to use a feature even when 70% of users can take advantage of it, it's still a no-go. So Apple totally blew it on this one. MS Edge appears to be further along than Apple...
- connorelsea 9y agoApple has unusually high adoption (compared to Android) for new versions of their OS, I am not too worried. You can ship a service worker and it will not degrade the experience for users on older browsers.
- RobertRoberts 9y agoI have a 3rd gen iPad right here, I can't upgrade to iOS 11. So, it's a forced _hardware_ upgrade to get a browser update. That's just insane.
- alwillis 9y agoSince Service Workers were enabled in STP as of a couple of days ago, the next upgrade to Safari in a few months will likely have it—it’s not 1-2 years away as you suggested. I’m pretty sure I’ll be running PWAs on my iPhone 5s the first half of 2018.
- connorelsea 9y agoThis is the dream, but I doubt Apple will offer any kind of proper home-screen integration like there is on Android. I can only hope tho
- alwillis 9y agoPart of what’s required is Web Manifest and that’s on the WebKit roadmap: https://webkit.org/status/#?search=manifest https://webkit.org/status/#?search=manifest