The funny/sad thing about PWA and how broken it's on iOS right now, is that the first iPhone was supposed to work with PWA. I'm not sure if it was Jobs' vision or they didn't have something good to offer for native devs. Safari has been a joke for long time now.

That was before they started printing money from the App Store.

> Windows announced support for PWA natively a while ago [0] but there has been no news since then.

There have been news since February.

UWP hosted apps got replaced with PWAs, including access to UWP APIs if signed, documentation and tooling support is now available.

https://developer.microsoft.com/en-us/windows/pwa

https://docs.microsoft.com/en-us/microsoft-edge/progressive-...

This is what made me have another look at PWAs, start experimenting with them and starting to see, that for plain CRUD applications PWAs are probably the way to go.

FWIW, the official Twitter desktop app for Windows 10 is a PWA and it works great (well, as well as any official Twitter app has worked in my assessment; not as well as third-party apps from their hey-day, but that's a different story).

I also use the Starbucks PWA (app.starbucks.com) and it mostly works well. Again, it seems to work as well as their native apps.

PWA is "Progressive Web Applications".

https://en.wikipedia.org/wiki/Progressive_web_applications

> chrome right now is the only one which supports PWA as "native" app..

What do you mean with "'native' app" exactly? When I use my PWA with a Firefox on Android I can't see that it is a PWA. It just looks like any other Andoird app.

Granted that is only one more browser and on the desktop side Firefox still has a lot to do, but at least there is one more player in the race ;-)