awesome-service-workers

The WIP spec for Background Sync.

The official service workers spec.

A general introduction to service workers and using UpUp to provide offline functionality in minutes.

A fascinating look at design and UX considerations for dealing with various states of connectivity.

A collection of recipes for different use cases.

An infographic summarizing the most important parts of service workers API.

Shortest available introduction, by

A hands-on guide and reference for service workers, caching strategies, push notifications, and more. Everything you need to build a modern progressive web app.

Service workers explained by

Up-to-date browser support table of ServiceWorker API.

Current status of ServiceWorker support in different browsers.

A quick dive into the most common technologies and techniques for building progressive web apps.

Explains how to structure your web app to optimize load time for initial and return visitors, and cover helpful service worker libraries that minimize the amount of boilerplate code you'll have to write.

This free Udacity course is a must if you're planning to dive deep into service workers.

Generate a web app manifest, required for push notifications and installable web apps.

A service worker helper library to retry offline Google Analytics requests when a connection is available.

Generates a service worker to cache your local App Shell resources.

A collection of simple helpers to simplify implementing common runtime caching patterns.

A popular service worker library providing complete offline functionality for your site in 1 line of code.

a set of libraries and Node modules that make it easy to cache assets and take full advantage of features used to build progressive web apps.

One of the most significant benefits of service workers (from a performance perspective, at least) is their ability to proactively control the caching of assets. A web application that can cache all of its necessary resources should load substantially faster for returning visitors. But what do these gains actually look like to real users? And how do you even measure this?

A case-study about how Google I/O 2015 web app was built.