Task completion when connectivity drops

Making sync state visible

I contributed to Loam’s field-worker task flow, including offline status changes and sync feedback.

With no connection, the app can save a completion locally while the update waits to reach the server. The workflow shows when a completed task is still waiting to sync.

Task row showing a completion waiting to sync. The fixture task label is redacted.
Later web QA, November 2026 — a task marked done on this device is waiting to sync. Synthetic fixture.

September Android pilot

The September Android pilot build included an offline queue, a pending indicator on task cards, and a shared sync sheet with Try again and Discard actions. The offline queue and replay-on-reconnect behavior were also checked on web staging.

Later refinement

A later revision made pending and failed changes visible on the task itself. The later states were checked in local QA with synthetic test data.

If a queued update is refused in the later revision, the task-specific panel offers Retry and Discard change.

Failed task update with Retry and Discard change actions. The fixture task details are redacted.
Later web QA, October 2026 — a simulated refusal exposes Retry and Discard change for the queued task update. Synthetic fixture.

The October refusal and the November completion came from separate local web QA runs. The evidence for the later revision covers implementation and synthetic QA.

Next case
Luqman →