Created
August 23, 2016 15:10
-
-
Save adewale/6e2baa8fdea65108b257fe9fbdae3b77 to your computer and use it in GitHub Desktop.
Common misconceptions about Progressive Web Apps
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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. |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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).