-
-
Save adewale/6e2baa8fdea65108b257fe9fbdae3b77 to your computer and use it in GitHub Desktop.
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. |
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.
They have to build their own browser and sites use other people's browsers.
https://twitter.com/ade_oshineye/status/871325198259281920
It's telling that both sessions on PWAs at Build started by changing Progressive Web Apps to Progressive Web Sites. Apps versus sites a distinction without meaning and ignores that many "apps" will be used as "sites" long before they are installed to home screen (if they ever are).
PWAs are all about getting the icon on the home screen.
Installation happens when the icon is added to the home screen.
You can add a service worker and a manifest to an insanely slow site and get the full benefits of a PWA.
You must be named "Paul"
Phew. Canceling my name change appointment.
Here's a real life misconception that was just posted:
https://www.reddit.com/r/web_design/comments/6f830a/does_offlinefirst_progressive_web_apps_make_sense/
I'd reply, but I boycott Reddit.
It's easy to describe these facilities to your users.