3 ms·

Apple intentionally doesn't support many the functionality required by PWA's.

by rydre 6y ago

jfoster 6y ago
That's true, and it's probably for this very reason. That said, at a minimum it's very possible to have a somewhat usable website on iOS. If ever that stops being the case, hopefully consumers will finally stop buying iOS devices.
niutech 6y ago
PWAs are supported well by iOS 13 and you can add a shortcut to the home screen since the beginning - see https://love2dev.com/pwa/ios/ https://love2dev.com/pwa/ios/
- rydre 6y ago
  No push notifications, limits of 50mb on storage whereas a good email app requires around 500mb to 1.5gb including local indexes for quick search etc. Storage cleared after a week of no interaction. No way to do photo preview. No contact picker. No picture in picture API support. And lots of other missing API's. Look at the WebKit forms and see how many developers are begging Apple to support them for years. The ignore any request. The web browsers that meets the PWA requirements are Chrome, Edge, Firefox (to a large extent), Brave, Vivaldi, all available on Windows, Linux, Mac, Android. Not Safari. And all browsers including Chrome and Firefox are just Safari under the hood (on iOS) so no completion for Apple. Apple does not even allow a competing browser engine. I wouldn't call this "PWA support". When I talk to friends at Google that work at Chrome, and tell them to convince Apple to support many of the features, they tell me that they have given up on them, and I can go talk to Apple if I want. They told me they're gonna keep progressing the web even if Apple wants to stay behind, they won't stop. I've talked to people at Apple about this, they don't care. They always have a far fetched excuse. I know it's not the engineers fault, they are ordered by the upper management. Instead of giving the money to Apple, we could easily reinvest it to grow.

3 ms·

Apple intentionally doesn't support many the functionality required by PWA's.

by rydre 6y ago

Apple intentionally doesn't support many the functionality required by PWA's.

jfoster 6y ago
That's true, and it's probably for this very reason. That said, at a minimum it's very possible to have a somewhat usable website on iOS. If ever that stops being the case, hopefully consumers will finally stop buying iOS devices.
niutech 6y ago
PWAs are supported well by iOS 13 and you can add a shortcut to the home screen since the beginning - see https://love2dev.com/pwa/ios/ https://love2dev.com/pwa/ios/
- rydre 6y ago
  No push notifications, limits of 50mb on storage whereas a good email app requires around 500mb to 1.5gb including local indexes for quick search etc. Storage cleared after a week of no interaction. No way to do photo preview. No contact picker. No picture in picture API support. And lots of other missing API's. Look at the WebKit forms and see how many developers are begging Apple to support them for years. The ignore any request. The web browsers that meets the PWA requirements are Chrome, Edge, Firefox (to a large extent), Brave, Vivaldi, all available on Windows, Linux, Mac, Android. Not Safari. And all browsers including Chrome and Firefox are just Safari under the hood (on iOS) so no completion for Apple. Apple does not even allow a competing browser engine. I wouldn't call this "PWA support". When I talk to friends at Google that work at Chrome, and tell them to convince Apple to support many of the features, they tell me that they have given up on them, and I can go talk to Apple if I want. They told me they're gonna keep progressing the web even if Apple wants to stay behind, they won't stop. I've talked to people at Apple about this, they don't care. They always have a far fetched excuse. I know it's not the engineers fault, they are ordered by the upper management. Instead of giving the money to Apple, we could easily reinvest it to grow.