zlacker

[return to "Apple’s refusal to support Progressive Web Apps is a detriment to the web"]
1. pluma+E2[view] [source] 2017-07-27 11:39:35
>>jaffat+(OP)
I think push notifications and offline support are the real killer features that Apple currently doesn't support.

It's kind of funny as a web developer because for the longest time Apple seemed to be the one pushing the mobile web forward but now that web apps are reaching for feature parity with native, Apple's initial momentum seems to be ancient history.

It seems Apple still thinks of the mobile web as a content delivery platform rather than an application platform. Their proprietary additions (mostly CSS) largely focused on making things prettier, their rationale for opting out of standard features (e.g. autoplay) often only work under the assumption that the only use for those features would be in the context of traditional content pages.

You want an app? Develop for our walled garden we tightly control to offer our users the best possible experience. If you want it on the web, stick to creating content our users can consume in Mobile Safari, our app for reading websites.

◧◩
2. rimliu+p3[view] [source] 2017-07-27 11:46:46
>>pluma+E2

   > web apps are reaching for feature parity with native
Not even remotely close.
◧◩◪
3. kartan+x5[view] [source] 2017-07-27 12:08:29
>>rimliu+p3
This is Papa Pear: https://king.com/game/papapear

The HTML5 version is compiled from the same source that the App that goes to the Apple App Store (https://itunes.apple.com/us/app/papa-pear-saga/id572542612?m...).

What's so different? It is literally the same code base (minus some platform specific code).

◧◩◪◨
4. rimliu+X7[view] [source] 2017-07-27 12:30:46
>>kartan+x5
I am talking about possibilities provided by iOS SDK and what is provided by web stack. It is amazing that React Native does not even have something UINavigationControll-ish. UIKit alone gives stuff which is lightyears ahead of the web. Even some more basic stuff: how easy it is to add accessibility to PWAs? Localization?
◧◩◪◨⬒
5. royal_+1a[view] [source] 2017-07-27 12:49:23
>>rimliu+X7
Most Frontend-Frameworks do have Localization-features so that's kind of easy to do. But other features like Bluetooth are nowhere to be seen (Blink Browser can do this - but it's far far away from a standard)
◧◩◪◨⬒⬓
6. vetina+Xv[view] [source] 2017-07-27 15:21:37
>>royal_+1a
Web Bluetooth: https://webbluetoothcg.github.io/web-bluetooth/ (not yet standard, but supported by Chrome, for example).

A11y is also being taken seriously.

[go to top]