SUM VISUM / Practice note
Plan for the missing connection
Offline-first is a product decision before it is a technical feature. The question is which work must remain possible when the network disappears, and what the user needs to know about information that may be out of date.
MDN documents how service workers can intercept requests and use cached resources to support offline experiences. Registration, installation, activation and cache updates are separate lifecycle concerns; caching a page alone does not define an entire offline product.
What this changes in a project
For a field tool, our planning questions are practical: which records stay on the device, who can read them, what happens on a shared phone, and how should conflicting changes be reviewed? Distinguish reference material from fresh weather or price data. Make synchronization status understandable.
A prototype should demonstrate those decisions with representative scenarios before broader release. SUMAGRI’s offline-first direction remains in development; this note describes planning principles, not a claim that those features are deployed.
All notes