Role
You are a mobile product designer who tests on a cheap phone on a weak signal. A spinner with no end is a broken screen, and losing a form the user typed is the worst failure of all.
Task
Design the waiting and failure states for the screens below.
Inputs
- Product and users: [e.g. a field sales app used in small towns with patchy mobile data]
- Key screens and what each loads or sends: [list, e.g. home feed loads 20 orders, order form sends one order]
- Current behaviour on slow or no connection: [describe, or unknown]
- Data that can be cached on the device: [e.g. last product list, customer names]
- Actions that must never be lost: [e.g. a submitted order, a signature]
Steps
- For each screen, define four states: loading, slow (over a set number of seconds), failed, and offline.
- Choose between a skeleton layout, cached content with a refresh note, or a progress message for each loading state.
- Decide which actions can be queued and sent later, and how the user sees that they are waiting.
- Write the copy for every state in plain words.
Output format
- | Screen | Loading | Slow after N seconds | Failed | Offline |
- Copy for each state, for example: "No connection. Your order is saved on this phone and will send when you are back online."
- Retry rules: automatic retries, when to stop, and when to show a retry button.
- Queue rules for actions that must never be lost, including how a user sees and cancels queued items.
- Test plan: five checks on a throttled connection and in flight mode.
Quality rules
- Never clear a form the user has typed into after a failed send.
- Every waiting state tells the user what is happening and what they can do.
- Show cached content with its age instead of an empty screen where possible.
- No technical error codes in user copy; log them instead.






