PWA is an acryonym that you don't need to worry about, unless you buy in to the argument that web apps are lacking certain desirable characteristics of native m

PWA is an acryonym that you don't need to worry about, unless you buy in to the argument that web apps are lacking certain desirable characteristics of native mobile apps. Most of the PWA required characteristics are pretty obvious: "Progressive" and "Responsive" - not new ideas. "Discoverable", "Linkable", "App-like" - the classic problems of single-page web apps "Fresh" and "Safe" - as if some people desire apps that are stale and dangerous. Then there are the characteristics that set PWAs apart: "Connectivity-independent" (should work offline) - My app lets you check yesterday's weather. "Re-engageable" (receives push notifications when the browser is closed) - Because users really love push notifications. "Installable" (can be installed on the devices home screen) - Isn't there something called a link that does this? The PWA requriements seem to be as set of priorities for websites heavily influenced by the experience (pros and cons) of native mobile app development. As such, they seem out of touch with what should be the priorities for a web app.