Show downloaded visits when route refresh fails
An offline refresh replaces the route with an empty screen. Retain downloaded visits and identify staleness.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Offline UX · Caching
Estimated field mix
- Mobile100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional maintenance coordinator Elm dispatches non-safety-critical inspection visits. Implement a mobile application in an emulator with local API stubs; physical devices and credentials are unnecessary.
Setup prerequisites
- Create synthetic visits and a local sync adapter.
- Provide controllable connectivity and process-restart simulation.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Cached visits remain visible
- Last sync time appears
- Retry does not delete cache
Implementation constraints
- Distinguish empty success from network failure.
Verification to include
- Load cached route offline
- Return successful empty route
Deliverables
- Route loading states
Rollout and recovery
Disable refresh clearing if cache disappears.
Value of the work
For the engineer: Practice durable mobile state and explicit sync conflicts.
For the team: Inspect how an engineer protects field work during disconnection.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.