Progressive web apps use modern web APIs along with traditional progressive enhancement strategy to create cross-platform web applications. These apps work everywhere and provide several features that give them the same user experience advantages as native apps. This set of docs tells you all you need to know about them.

PWA advantages

PWAs should be discoverable, installable, linkable, network independent, progressive, re-engageable, responsive, and safe. To find out more about what these mean, read Progressive web app advantages. To find out how to implement PWAs, consult the guides listed in the below section.

Core PWA guides

The following guides show you what need to do to implement a PWA, by examining a simple example and showing you how all the pieces work.

  1. Introduction to progressive web apps
  2. Progressive web app structure
  3. Making PWAs work offline with Service workers
  4. How to make PWAs installable
  5. How to make PWAs re-engageable using Notifications and Push
  6. Progressive loading

Technology guides

Tools

  • localForage — a nice simple JavaScript library for making client-side data storage really simple; it uses IndexedDB by default, and falls back to Web SQL/Web Storage if necessary.
  • ServiceWorkerWare — an Express-like microframework for easy Service Worker development.
  • oghliner — not only a template but a tool for deploying Offline Web Apps to GitHub Pages.
  • sw-precache — a node module to generate service worker code that will precache specific resources.
  • workbox — spiritual successor to sw-precache with more advanced caching strategies and easy precaching.
  • upup — a tiny script that makes sure your site is always there for your users.
  • The service worker cookbook — A series of excellent service worker/push recipes, showing how to implement an offline app, but also much more.

 

See also

Document Tags and Contributors

Last updated by: chrisdavidmills,