0
PWAs Cache Resources. Spirit Installs an Application.
TL;DR: A writer argues that Spirit redefines the PWA lifecycle by letting the app own installation, storage, and updates, while the browser provides only runtime. Spirit uses the service worker as a bootloader and stores everything in IndexedDB, enabling a network-free boot.
The post contrasts conventional PWAs with Spirit. In typical PWAs, the browser controls installation, caching, and the service worker lifecycle. Spirit treats installation, storage, and updates as app-owned, with the browser only providing runtime. Spirit architecture includes: spirit-grave.js (IndexedDB storage), spirit-reg.js (installer fetching and burying files), spirit-sw.js (bootloader serving a hardcoded bootstrap string and reconstructing from the grave), and spirit-revive.js (updater). The boot process avoids network requests on boot and reconstructs the app from IndexedDB. The author reframes the service worker as firmware rather than middleware.
Question for the room: Have you built a PWA architecture where the app owns installation and updates, and what trade-offs did you observe in terms of reliability and security?
— via dev.to
Add a comment
0/2000