Awesome Service Workers
      
    
    A curated collection of service worker resources.
    
      
      >Service workers are at the heart of every progressive web app. Their
      persistent nature allows progressive web apps to fulfill our expectations
      of what an app should do. They are the missing link between what only
      native apps could do and what modern progressive web apps can do. >
      > –
      Building Progressive Web Apps - O’Reilly
    
    
      If you want to contribute, please read the
      contribution guidelines.
    
    Contents
    
    Must Reads
    
    Learning Resources
    
    Reference
    
    Browser Support
    
    
    
      - 
        UpUp - A popular service worker library
        providing complete offline functionality for your site in 1 line of
        code.
      
 
      - 
        sw-toolbox - A
        collection of simple helpers to simplify implementing common runtime
        caching patterns.
      
 
      - 
        Manifest Generator
        - Generate a web app manifest, required for push notifications and
        installable web apps.
      
 
      - 
        sw-precache -
        Generates a service worker to cache your local App Shell resources.
      
 
      - 
        sw-offline-google-analytics
        - A service worker helper library to retry offline Google Analytics
        requests when a connection is available.
      
 
      - 
        Workbox -
        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.
      
 
    
    Videos
    
    Case Studies
    
      - 
        Service Workers in Production
        - A case-study about how Google I/O 2015 web app was built.
      
 
      - 
        Measuring the Real-world Performance Impact of Service Workers
        - 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?