Instant Loading: Building offline-first Progressive Web Apps - Google I/O 2016
Why Stack Overflow recommends it
Stack Overflow users link it as the reference walkthrough for building offline-first PWAs and service worker caching, both as a basis for their own code and when asking whether the approach fits other kinds of sites.
Recommended by 2 people across 2 different months, 2016 to 2018.
What it is
Jake Archibald's Google I/O 2016 session takes an online-only site and turns it into an offline-first, installable progressive web app through small iterative steps. It covers ServiceWorker, web manifests, add-to-homescreen banners, IndexedDB and BackgroundSync.
What people said
Recommends ncubica · 2017-01 · Stack Overflow · on “Migrating to Meteor/React”
I think what you want is explained perfectly in this youtube video Google I/0 2016 `Building offline-first Progressive Web Apps` [this video]
Recommends Adam McGurk · 2018-08 · Stack Overflow · on “Service worker uncaught in promise not sure where”
I'm building my web app offline first based on this video: [this video] And I'm running into trouble with the service worker. Here is my sw.js code: const FILES_TO_CACHE = [ "/js/app.js", "/js/authenticate.js", "/js/forms.js", "/js/head-scripts.js", "/js/remember.js", "/js/style.js", "/style/style.css", "/index.html", "/tracker/index.html", "/assets/LongShineLogo.png", "/assets/shineSolarLogo.png", "/assets/ShineSunburst.png", "/error/404.html", " [LINK] ", " [LINK] " ]; const CACHE_NAME = "static-cache-v1"; // Caching files in the cache self.addEventListener("install", event => { event.waitUntil( caches.open(CACHE_NAME) .then(function(cache) { return cache.addAll(FILES_TO_CACHE) }) ); }); self.a
Cites Aaron Bushnell · 2016-05 · Stack Overflow · on “Progressive web applications and CMS-driven websites”
I've been intrigued by offline-first, progressive web applications from talks by developers like Addy Osmani [LINK] and Jake Archibald [this video] . However, when I watch these it always seems to be in the context of a web application where someone would use an SPA to build a chat app, a photo app, and interact with data from an API endpoint. I typically work with clients who use a CMS to build 10k+ pages that have all sorts of different content of various lengths and combinations: WYSIWYG content, banners, forms, etc. Are offline-first, progressive web applications possible for CMS-driven work? If so, what are best practices to consider to maintain progressive-enhancement?