Skip to content

Instantly share code, notes, and snippets.

@adewale
Created August 23, 2016 15:10
  • Star 7 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save adewale/6e2baa8fdea65108b257fe9fbdae3b77 to your computer and use it in GitHub Desktop.
Common misconceptions about Progressive Web Apps
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.
@addyosmani
Copy link

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

@dandv
Copy link

dandv commented Aug 23, 2016

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.

@dalmaer
Copy link

dalmaer commented Aug 23, 2016

You must use push notifications
You can't use AMP

@jmadler
Copy link

jmadler commented Aug 23, 2016

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

@dalmaer
Copy link

dalmaer commented Aug 23, 2016

You must use pull quotes

@dalmaer
Copy link

dalmaer commented Aug 23, 2016

You must be named "Paul"

@addyosmani
Copy link

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

@senthilp
Copy link

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

@stuartlangridge
Copy link

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

@dalmaer
Copy link

dalmaer commented Aug 23, 2016

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

@tomayac
Copy link

tomayac commented Aug 23, 2016

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

@grigs
Copy link

grigs commented Jun 4, 2017

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).

@grigs
Copy link

grigs commented Jun 4, 2017

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.

@grigs
Copy link

grigs commented Jun 4, 2017

You must be named "Paul"

Phew. Canceling my name change appointment.

@grigs
Copy link

grigs commented Jun 4, 2017

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