# Keep work moving beyond the desk.

Mobile & progressive web apps

Design for touch, variable connections and real device constraints with installable web experiences where they fit.

## Work continues beyond a reliable connection

Illustrative workflow.

- Assigned work: The details needed before leaving coverage
- On-device draft: Changes saved with visible sync status
- Reconnection: Conflicts resolved before final submission



## A smaller screen needs a different sequence

### Shrink the desktop application

Dense tables, hidden controls and optimistic sync messages make field work fragile.

### Build for the device and the connection

Prioritise the next action, preserve local work and show exactly which changes still need to sync.

## Design the disconnected journey first

Field teams need large touch targets, short forms and a clear distinction between saved on the device and received by the server. Choose offline behaviour around the task and the data it is safe to retain.

Illustrative scenario, not a customer case study.

Regional field teams need to record work when connectivity is intermittent.

Keep a local operation queue with stable identifiers and explicit sync states. Resolve conflicts using business rules and make unsynchronised work visible to the worker.

Verification: Test connection loss, process termination, duplicate submission and account changes with pending work.

## A useful mobile journey, online and offline.

### Touch first journeys

Use readable content, reachable actions and input controls that work with device keyboards.

### Connection changes

Preserve drafts and show what is saved locally, waiting to sync or confirmed by the server.

### Installable experiences

Add an app manifest and a deliberate caching strategy where an installed web experience fits the task.

## What needs attention in your system?

Select the areas you want to discuss. The HTML page can download your selections.

- [ ] Touch first journeys: Use readable content, reachable actions and input controls that work with device keyboards.
- [ ] Connection changes: Preserve drafts and show what is saved locally, waiting to sync or confirmed by the server.
- [ ] Installable experiences: Add an app manifest and a deliberate caching strategy where an installed web experience fits the task.

## Is a PWA always a replacement for a native app?

No. Compare device integrations, background execution, distribution and offline requirements before choosing a web or native delivery model.