Field work
Working offline with a window-cleaning app
Understand the difference between a screen that was merely loaded earlier and a deliberate offline workflow that protects visits, outcomes and photographs.
Published 23 August 2026 · 6 minute read
Key points
- Open and download assigned work before leaving reliable coverage.
- Queued outcomes must survive an app restart.
- Retries need stable operation identifiers to prevent duplicates.
- Photos should upload only after the related completion is accepted.
Offline should be a designed workflow
Mobile signal can weaken between streets, behind buildings and in rural areas. A field app should not turn one temporary connection problem into lost work or a duplicate charge. Reliable offline support starts by deliberately storing the assigned visits needed for the day on the device.
A previously displayed web page is not the same as offline operation. Ask whether the app keeps the address, service, access warnings and current work state after it is closed and reopened without a connection.
Prepare before starting the round
While connected, sign in, select the correct company and open the assigned day. Confirm the list is complete and that the app reports it is up to date. Do this before travelling to an area where the signal is known to be unreliable.
Only download information the worker is authorised to use. Offline storage should not become a way to copy the whole company database onto every phone.
Keep every queued action visible
When an outcome cannot reach the server, the app should save it durably and show that it is waiting. The worker must be able to distinguish queued, syncing, accepted, failed and conflicting changes. A green tick should mean the server accepted the operation, not merely that a button was tapped.
The queue should survive an app restart. Retrying the same operation must return the original result instead of creating a second completion, charge, payment or next visit.
Synchronise outcomes before photographs
A completion photograph belongs to a specific authorised visit and outcome. The safest sequence sends the completion first, then uploads the private photograph and registers its metadata. If the outcome is still waiting, the image should remain safely queued on the device.
Failed or conflicting work should stay visible until a person retries it or deliberately chooses the confirmed server version. Connection errors should never silently discard a day of work.
Run a controlled offline test
Before relying on any app in the field, use fictional data and complete a repeatable test: open the assigned day, disable mobile data and Wi-Fi, complete two visits, record one cash payment, close and reopen the app, then reconnect. Confirm that each action appears once and the photo uploads after its completion.
Common questions
Frequently asked questions
Will every window-cleaning app work without signal?
No. Some products require a live connection or cache only part of a page. Check exactly which visits, notes and actions remain available, then test it yourself.
What happens if I complete the same visit twice while offline?
Well-designed software uses one stable operation identifier so a retry returns the existing completion instead of creating a duplicate charge or next visit.
Are offline completion photographs secure?
They should be kept in durable app storage, uploaded to private storage only for an authorised visit and exposed through short-lived access rather than a public URL.
Roundflow help