The Web Platform Podcast : 24: ServiceWorkers and High Performance Offline Apps

Offline access for applications is becoming more and more necessary for web development today due to increasing client usability demands. The HTML AppCache are a partial solution but is very sticky, often provides stale data and is not dynamic or adaptable. Developers can easily find themselves doing hacks with the deprecated Web SQL API, IndexedDB, & localStorage or a framework like to achieve a fully supported offline application.


Jake Archibald (@jaffathecake), Google software engineer, wrote an infamous article on A List Apart about the inadequacies of AppCache. This turned into the beginnings of ServiceWorker, an API for offline access that provides “scriptable primitives that make it possible for application developers to build URL-friendly, always-available applications in a sane and layered way.” ServiceWorkers allow developers to to make sites work faster and/or offline and also use network intercepting as a basis for other 'background' features such as push messaging and background sync

Jake, along with Google Engineer, Alex Russell (@slightlylate) & Mozilla engineers Anne Van Kesteren (@annevk) & Ben Kelly (@wanderview) talk about ServiceWorker’s current state and how we will use it in our applications.


The spec -

How to build with ServiceWorkers -

The Offline Cookbook -

ServiceWorker Cache Polyfill -

ServiceWorker Github -

The article that started it all -

Offline First Organization -

Potential Resource Implications -  

Understanding ServiceWorker Cache in Firefox -

Intro to Service Worker -

Using Service Workers -

Web Spec Framework -

Brendan Eich Quote -

The early state of ServiceWorker -

Support in browsers -