While it might not work for everything, I have a number of sites that are used for field work that would benefit from these approaches. Things like dashboards an configuration tools.
Arguably, the tools should be desktop apps, or something of the like, but the reality is that using PWAs in this way is easier for everyone (the developer, the distributor, the user).
PWA has always supported all of that. It’s just that companies like to spy on your data more by making native apps
Here is the list of PWA capabilities. This is discounting those that Google has on their site (web dev)
Why is this called 2.0? PWA without offline is assumed to be 1.0?
I don’t like them randomly defining and attributing version numbers to standards. These versions don’t exist. And they don’t even define them.
PWA and offline capability has been around for a while. PWA typically raises the question of offline capability. That’s not a new thing or a new standard.
I REALLY don’t trust JavaScript developers nor their braindead cargo-cult community to implement this correctly.
