Work can continue without a signal. What does the site save, and what does it really send?
Design offline work around local saves, pending changes, server confirmation and conflicts after reconnection.
Article language: English

In this article
The exhibition hall has lights, a coffee machine and six conversations at once. The signal seems to have gone to see another stand. The person inspecting equipment presses “Save” and sees a green confirmation. An hour later, the office still has no report of the damaged panel. Did saving fail, or did the screen promise something different from what happened?
In an application that works without a network, saving on the device is a useful result. Someone can continue the inspection, add a note and take a photo. Trouble begins when that result looks just like confirmation that the company has received the data. The entire journey needs designing, from a local action to its resolution after the connection returns.
Consider a fictional company that rents exhibition equipment. Ola, a technician, walks between stands with her phone. She marks checked items, describes damage and attaches a photograph. The office plans the next releases on another device. Her observations must enter a shared workflow in which someone else is working at the same time.
Preparing to go out is part of the work
Before the inspection, Ola needs the equipment list for the right event, identifiers and last confirmed status. A home page remembered by the browser does not supply that set. The design should show what is already available on the phone and what is still waiting to download. A list of a hundred items will not help if each detail opens a blank screen without a network.
Preparing the package can be interrupted too. Suppose the phone saved data for twelve items but did not download instructions for the rest. When reopened, show what is available and how to finish preparation. Starting the application alone does not complete this stage. Ola should be able to inspect the prepared portion or return for the rest, knowing which stands are not yet covered. The event number and missing-items list support that decision without opening every item.
Separate the actions first. Reading an earlier instruction, saving a note and confirming an equipment release may require different levels of freshness. In this example, an inspection can be saved as work in progress. Promising a panel's availability for another event requires reference to the company's current state. One “offline mode” label does not explain those differences.
MDN describes the Background Synchronization API as a way to defer synchronisation until connectivity returns. Its availability is limited and it requires a secure context such as HTTPS.
With automatic sending, Ola needs a place to check receipt. With manual sending, she needs a visible action that finishes the inspection. The technical mechanism's name can remain in the developer documentation. The screen must explain what she can do now and what will happen to waiting material.
Before she enters the hall, the application might summarise: “The equipment list for the Autumn event is available on this phone. Last data from 8:40.” That message must refer to a set actually prepared. If reference photos were not downloaded, identify that gap where they are needed instead of promising the whole application is ready.
This differs from saving a multi-stage form to return later (in Polish). There, a person postpones completing material. Here, she continues working and creates further changes while the company's shared state is temporarily out of reach. The interface must let her assess both her own work and the freshness of the information on which it relies.
Make the place where data is saved visible
Ola adds “cracked corner” to panel P-18. The phone retains the note and displays it in the list. At the office, the panel still has its earlier status. Both people may be looking at a correct record on their own device, but the records concern different times and places. A local change therefore needs a scope: “Saved on this phone. The change is waiting to be sent.”
A pending-changes count helps if it leads to specific items. “4 changes pending” should expand to the panel note, two inspection confirmations and a photograph. At the end of the inspection, Ola need not remember which action she performed before losing the network. She can recognise it in the application.
The photograph needs its own status. A locally saved note does not prove the file was saved too; a sent description does not confirm the photo transfer. The panel view can place both together with different confirmations. The office can then see whether it received only the description or the complete material for a decision.
Also decide what successive edits to one note mean. Ola first writes “crack”, then after closer inspection changes it to “scratch on protective film”. If the aim is to pass on the current observation, the summary must show the revised description. If the company also needs the edit history, separate it from the current content. A count of two operations must not imply two damaged panels. The unit counted must correspond to what the office will receive.
MDN distinguishes best-effort browser storage, the default, from persistent storage. The browser may evict data in the first category; a user can also clear stored data themselves.
For local saving, identify the device and how to send the material. If there is not enough space for a photograph, tell the user beside that photograph, with an option to reduce the material or choose another route. A general message about the whole inspection would conceal that the other notes are already saved.
Installing a site can make the tool easier to return to, but an icon alone does not settle data durability. Assess an offer to install a PWA (in Polish) separately from readiness for offline work. Ola needs to check the prepared set whether she opens the service from an icon, bookmark or message.
The connection is back; confirmation is not
Wi-Fi appears halfway down the corridor. This is a good moment to try the server, but not yet proof that all changes were accepted. “Online” with four items still pending can be correct. A poor design would hide the counter as soon as the network icon changes, preventing the user from recognising unsent material.

The navigator.onLine documentation explains that a local network connection can produce an online status even without internet access. The indicator alone does not confirm that your service is reachable.
Show the result of successive attempts in the changes list. The note may already be accepted, the photo still uploading and confirmation of one item awaiting a decision. A collective “Synchronisation complete” must match the agreed definition of completion. If it covers only transfer, it must not pretend that a conflict with the office's data is resolved.
A lost confirmation is an especially useful test. The note reaches the office, but the phone does not receive the response before the connection drops again. Ola still sees a pending state. “Not sent” would assert something the application does not yet know. Without a connection, show: “No confirmation. We will check when the connection returns.” “Checking whether the note was received” fits only after a status read has actually started once contact returns. Both states concern the same item. Once the result is known, the user should recognise acceptance or the next step without entering the damage again.
At the office, the same note may already support action. An acceptance scenario should therefore compare both perspectives: a phone without confirmation and an accepted record. The difference is temporary and explainable. Creating a second case or deleting the existing one merely to make both screens look tidy would be the error.
MDN notes that a browser can stop a service worker, a mechanism handling some background actions. It is not a continuously running process under the user's control.
In this design, Ola therefore has a place to return to after the inspection and see each change's confirmed state. She does not have to stand by the router with the phone unlocked. If the solution requires reopening the application, that action should be described as part of finishing work, not discovered only when the office lacks the material.
A manual “Try sending again” must refer to the same note. The person wants to transmit a known change, not create a second damage report. The screen design and handling retries without duplicates (in Polish) meet at a recognisable item with its current result.
If a user deletes a pending note, name that action differently from closing the panel. They may also edit its description before sending. The list should retain the latest intended content, and once contact with the server begins the result needs confirmation. A row disappearing from the screen does not itself retract data that has already travelled further.
The office has already changed the same panel
During the inspection, the office removed P-18 from the next release. Ola has the earlier status on her phone and adds damage. The system may accept the note as an additional observation, but should not accidentally restore the panel's old availability. A design may accept the photograph independently of a decision about the item's future availability. The meaning of a change matters more than a general order for saving the whole record.
Break the working record into what the user actually intends to change. Adding a photograph, confirming an inspection and changing status have different relationships to parallel work. If the design shows only a generic “Save item”, the recipient cannot tell whether it changes one note or the whole set visible before departure.
A discrepancy needs a decision view: what the user's change concerns, what status the office confirmed and what can be kept. The guide to communicating edit conflicts (in Polish) helps plan a comparison. Offline work also allows hours of delay and several changes that do not necessarily conflict with one another.
Ola can finish the inspection even if two items await an office decision. The summary should say so. Blocking the entire task until a response would make her watch the phone although the next decision no longer belongs to her. Conversely, a full-success message would hide work someone still needs to do.
A phone shared between shifts raises the ownership of waiting material. The shared-terminal design guide (in Polish) calls for separating users. In a field tool, signing out should neither leave another person's notes accessible to the next person nor silently remove the only copy of an unsent inspection. Before handing the phone over, show whether material requiring action remains on it.
Review the inspection from another perspective
For a trial, prepare a short fictional equipment set and agree the expected result in advance. One person inspects; another works in the office. After preparing the list, disconnect the phone. The field worker adds a note and photograph, closes and reopens the application, then identifies what is saved. Do not give them the names of states to look for; ask them to describe the situation in their own words.
Restore access and compare the phone with what actually appeared at the office. Part of the trial should include a failed photo transfer and a parallel change to one item. Success means a recognisable result for every item that matches the agreed rules. A disappearing warning bar is too weak a criterion.
A separate run should include losing account access during the inspection. After signing in again, Ola needs to recognise her own pending material and the correct event. If the account or organisation changed, the application must reveal the difference before sending. The guide to returning after session expiry (in Polish) needs to be considered together with the local queue. Material from earlier work should not enter a new context merely because the user regained access to the service.
The worker's own trail should remain clear the next day. The event name, time of last confirmation and list of unresolved items allow a return to the right inspection. This does not require showing the whole technical log. It requires information that distinguishes yesterday's unsent material from today's ready task.
web.dev's offline design guidance recommends explaining available actions and showing state through several means. Colour alone or the technical word “offline” may not tell the user enough.
A conversation with Aeneia Design can start from such a workflow, using materials and roles from your own work. Screens can then show the concrete difference between retaining an observation on a phone and passing it into the shared workflow. Ola can continue to the next hall, while the office knows whether it awaits a photo, a decision or the first report. Each side can see its next step without hunting for one more bar of signal.







