zlacker

>>jaffat+(OP)
As an iOS user, I'm actually quite glad that websites can't send me push notifications on it. And app loading screens are a feature?

If people _insist_ on making phone apps as websites, there's Cordova and all that. Such apps are never very good, of course. I still haven't seen a website-based desktop/phone app that wasn't a clunky non-native-looking resource-hogging mess.

>>rsynno+E4
That exact argument can be applied to native apps. Should native apps have push notifications removed?

Why not? Because they can actually be extremely useful. Such as for receiving emails, Facebook messages, Slack pings, or news updates you've subscribed to. Maybe somebody tweeted you. Any of these apps could work as progressive webapps.

Regardless if the platform is native or web-based, the feature remains opt-in. If you don't want them, then don't subscribe to them.

>>Square+Ka
Yes but supporting the feature encourages developers to make web apps. Why would you want to encourage that?

>>interp+rb
Why wouldn't you want that? PWAs are seamless (no downloading/installing), allow native features, can be saved offline for later, run in a secure sandbox, and are completely open and cross-platform.

>>Square+bd
And that was such a great experience with Java applets....

>>scarfa+Cl
False equivalence. The points I listed above were not true for Java applets.

Applets were not seamless (requiring a plugin to be installed), did not allow most native features, and ran in anything but a secure sandbox.

They were open (by nature of the JVM), and cross-platform, but that's it.