Common misconceptions about Progressive Web Apps

gistfile1.txt

Common misconceptions about Progressive Web Apps

They have to be SPAs.
They have to live at pwa.*.com
They have to be mobile only.
They're not allowed to be responsive.
They have to use material design.
They only work in chrome.
They don't work in safari or on iOS.
They have to look like your android app.

They can't be progressively enhanced
They can't be built with framework X
They can't be as smooth as native apps
They can't work on desktop
They require a high technical barrier to build

They can't run in full-screen (source).

Also, Gist comments don't trigger notifications, so it might be better to host this list somewhere else.

You must use push notifications
You can't use AMP

They require a rewrite of your web app
They don't support Ads

You must use pull quotes

You must be named "Paul"

They're difficult to monetize
They haven't been proved in production
They require an App Store model for the web

It is difficult to deploy a critical bug fix and have it immediately available to all my PWA users

It's easy to describe these facilities to your users.

Offline is building for Wendy on a plane and isn't worth the effort

They can be installed and discovered via some sort of app store or PWA market… Blame the 'A' in the PWA acronym.