Offline UX

on YouTube ↗45m

" summary

Most sites break badly when connectivity drops; the concrete fix is to install a service worker to serve a branded offline page, precache pages users actually visit, and offer explicit downloads for big assets (lodash docs ≈ 40–50KB per version worked well). Use analytics-driven prefetch (Guess.js) rather than hidden megabytes for Easter eggs — Guardian removed its offline crossword because almost nobody used it and it wasted bandwidth. Background sync lets forms submit after closing the tab but testing is awkward (Puppeteer support exists but has a blocking bug) and real-time conflict resolution (Google Docs style) remains hard.

AI-written summary · about

" chapters (7)

1. 0:00The reality of offline
2. 2:37When and why to be offline
3. 11:17Implementing offline support
4. 23:32Serving content effectively
5. 26:55Forms and user interaction
6. 35:25Complex application features
7. 38:42Challenges and considerations

" related talks

• 06mI'm Offline, cool. What now?Ola Gasidlo · Voxxed Days Zurich 2017
• 24mBuilding an Offline Page for theguardian.comOliver Joseph Ash · JSConf Budapest 2016
• 45mOffline First (Web) AppsAlex Feyerke · ColdFront Conference 2015
• 26mBuilding an Offline Page for The GuardianOliver Joseph Ash · Front-Trends 2016
• 44mOffline first!Rowdy Rabouw · Jfokus 2023
• 21mGo Offline First to Save The WorldMaureen McElaney · JSConf EU 2017
• 58mOffline SecondAleksey Bogachuk · HolyJS 2017 Piter
• 44mDesign principles and implementation strategies for better offline experienceBoyan Mihaylov · NDC Oslo 2017