The research question
A laptop loses its connection during a customer visit. Reading cached agreements, drafting notes and preparing a proposed update may remain useful, while confirming a shared commercial decision may require an authority that is currently unreachable. Describing the whole application as simply online or offline hides these different capabilities and can lead users to expect more than the system can safely establish. Local-first research connects collaboration with ownership and useful offline work. The design challenge is to specify which local operations remain meaningful when other participants or the authority for a business decision cannot be reached.
A concrete design choice
The proposed interface lists the relevant operation states: local reading available, draft saved, synchronization pending or authoritative confirmation unavailable. The distinction should follow the action, not just the network icon. A user can continue preparing work without mistaking a local draft for a completed shared transition. The application should preserve the draft across restarts and make the remaining step clear when connectivity returns. If required source documents were never downloaded, that limitation belongs in the same view rather than appearing only after the user opens a broken link during the visit.
What would demonstrate usefulness
Test a realistic disconnected session involving reading, drafting and a proposed business action. Ask users what they believe has been saved, shared and approved. Verify those expectations after reconnecting. The acceptance question is whether useful work continues with clear boundaries, not whether every button remains enabled without a network.