Modern web apps can work when the network is unreliable, or even non-existent. No more blank connectivity error pages or dinosaurs running through the desert. A clear separation between UI and content in addition to offline caches and service workers allow you to store the application's data and core assets for future use.
The basic ideas behind network independence are to be able to:
- Revisit a site and get its contents even if no network is available.
- Browse any kind of content the user has previously visited at least once, even under situations of poor connectivity.
- Control what is shown to the user in situations where there is no connectivity.
- Using service workers
- A simple guide for those new to the Service Worker API.
- Using IndexedDB
- The basics of IndexedDB, explained in detail.
- Using the Web Storage API
- The Web storage API made simple.
- Instant Loading Web Apps with An Application Shell Architecture
- A guide to using the App Shell coding pattern to create apps that load quickly.
|Technology||Description||Support summary||Latest spec|
|Web Storage||A simple API for storing name-value pairs on the client-side.||Widespread (more detail)||Web Storage (Second edition)|
- An Express-like microframework for easy Service Worker development.
- Not only a template but a tool for deploying Offline Web Apps to GitHub Pages.
- A node module to generate service worker code that will precache specific resources.
- A tiny script that makes sure your site is always there for your users.
- The service worker cookbook
- A series of excellent service worker recipes, showing how to implement an offline app, but also much more.