service workers

I hadn't considered the fact that if you're fingerprinting your assets (e.g. style.987987090897.css) to take advantage of browser cache, you'll need to update your Service Worker every time you do that. But I guess you've got a build step anyway, so it can be updated in both places:

... we used a NodeJS module called Stacify to automatically create new version numbers in all the places when a file is changed.

A straightforward tutorial by Una Kravets on caching assets and individually requested articles with Service Workers for offline reading.

I'm curious what the best practice will become. It's possible that asking users to click something is it. Also possible: passively caching articles based on recently published, currently viewing, or related to currently viewing.

Mariko Kosaka:

I finally figured out, it's an alien you can invite to live on user's browser.