Skip to content

Instantly share code, notes, and snippets.

@sentenza

sentenza/KeyConcepts.md

Created December 7, 2016 08:12
Show Gist options
  • Save sentenza/137c1feaeb6779649ddea40556d90bd5 to your computer and use it in GitHub Desktop.
Save sentenza/137c1feaeb6779649ddea40556d90bd5 to your computer and use it in GitHub Desktop.
Download ZIP
Progressive Web Apps (PWA)
Raw
KeyConcepts.md

What's a Progressive Web App?

  • Obviously, no install required
  • It loads quickly, even on flaky networks
  • Can send push notifications
  • May have an icon on the home screen (loading as a top-level)
  • Should support full-screen mode

Key features

  • Progressive enhancements will be added by using them
  • These apps should be easily discoverable by a Google search
  • They can be linked together, because they are part of the Web
  • Responsive
  • Indistinguishable from a mobile app
  • Offline and cache support via service workers (see the previous point)
  • Push notifications would be a nice way to gain engage with the users
  • A setup-like process could be possible through an home-screen linking and the full screen support (mobile-app behaviour)
  • Update frequently (no real installation required and client-server approach for the view layer)
  • Secure: always on HTTPS
  • Instant loading is now possible using service workers

But why this kind of change is needed?

  • No real installation process
  • Typical mobile usage average is 25 app per month versus 100+ sites navigated to
  • No more version fragmentation

Technological core of PWA

  1. Service workers: enabling push notifications and background sync. Future features will be periodic sync and georeferencing
  2. Restrains on using a service worker today:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment