[WA]

Many many apps are made with JS, HTML and CSS and run in a thin wrapper on top of WKWebView (Cordova, nowadays Capacitor). It is Electron sans a browser engine and has been around forever. Support for PWAs don't change a thing about how apps are developed at all. They only change how apps are deployed. Hence, your whole point about "better quality apps by banning PWAs" is completely wrong.

[coldtea]

>Many many apps are made with JS, HTML and CSS and run in a thin wrapper on top of WKWebView (Cordova, nowadays Capacitor). It is Electron sans a browser engine and has been around forever.

I know, I already covered all that.

>They only change how apps are deployed. Hence, your whole point about "better quality apps by banning PWAs" is completely wrong.

I didn't say banning PWAs will result in better quality apps in general. I said:

(1) "Add to home screen PWAs" are not that used in the first place.

(2) "PWAs wrapped as native apps" are, but iOS encourages native apps more.

(3) Giving more parity to PWAs (going the opposite route of the current removal) will encourage them to be used more, which I don't particularly like, for the same reason I don't like Electron (including iOS wrapped-PWAs).

[WA]

Fair enough. Regarding (3): The alternative to Electron-Cordova-Wrapper-JS apps is not "native app" but "no app at all". Most people think about flashy apps that probably should be native. You mentioned Slack. But many apps are just stuff that don't have to be an app in the first place, like apps for specific hotels, bus tickets in a local city, app for the local library etc.

These (web) apps as PWAs would offer a better interface and more capabilities than a pure in-browser web app, but they lack the resources to provide a truly native app.

Banning PWAs doesn't encourage native apps, but even shittier web apps. I'd bet 90% of web apps wrapped in Cordova are there only because they need a) local storage and b) push notifications.