I am skeptical if this for the only reason that iOS hasnt followed suit and I guess it won't do it as well. They have a big engineering team and if they wanted to support PWAs, they would have done it by now (not having push notifications, native add to home screen and a few others)
I feel they want to exert a better control over the ecosystem and with PWAs working out of the box, their 30% commission would be in danger - also with the risk of ruining user experience and lack of security thereof.
PWAs are here to stay but to beat them on iOS would be tough.
Apple is actually behind on multiple fronts but finally catching up (which was showing during the last WWDC).
If you look at Jake Archibalds: Is ServiceWorker Ready you can see that it has been updated to YES, since iOS 11.3 (this all started with 11.1 and later), which quietly shipped full Service Worker support.
The next big update came with iOS 12.2 adding a PWA browser and other full-fledged support features. Yes, it was all in Beta but this shows the intent of Apple.
If that was the focus, it would have come up in iOS 13 - unfortunately, it did not. Until web push and background sync is done perfectly, none of it matters IMO
Those features we're not present in Chrome when PWAs landed; the whole point is that all these features are additive. They are progressively enhancing the applications.
PWAs are much more than those two, and it matters, even if it doesn't matter to you.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am skeptical if this for the only reason that iOS hasnt followed suit and I guess it won't do it as well. They have a big engineering team and if they wanted to support PWAs, they would have done it by now (not having push notifications, native add to home screen and a few others)
I feel they want to exert a better control over the ecosystem and with PWAs working out of the box, their 30% commission would be in danger - also with the risk of ruining user experience and lack of security thereof.
PWAs are here to stay but to beat them on iOS would be tough.
Apple is actually behind on multiple fronts but finally catching up (which was showing during the last WWDC).
If you look at Jake Archibalds: Is ServiceWorker Ready you can see that it has been updated to YES, since iOS 11.3 (this all started with 11.1 and later), which quietly shipped full Service Worker support.
The next big update came with iOS 12.2 adding a PWA browser and other full-fledged support features. Yes, it was all in Beta but this shows the intent of Apple.
In short: iOS is following suit .
If that was the focus, it would have come up in iOS 13 - unfortunately, it did not. Until web push and background sync is done perfectly, none of it matters IMO
Those features we're not present in Chrome when PWAs landed; the whole point is that all these features are additive. They are progressively enhancing the applications.
PWAs are much more than those two, and it matters, even if it doesn't matter to you.