wowprompt

Loading, slow network and offline states review for an app

Walks through each key screen of an app as a user on a slow or dropping connection would see it, and designs what should appear while content loads, when a request is slow, when it fails and when the device is offline. Returns states, copy and retry rules for each screen. Use it when users complain the app freezes, spins forever or loses what they typed.

A table of screens with designed loading, slow, failed and offline states, the copy for each, retry and save rules, and a short test plan on a throttled connection
The output this prompt produced, unedited.

The prompt

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

  1. For each screen, define four states: loading, slow (over a set number of seconds), failed, and offline.
  2. Choose between a skeleton layout, cached content with a refresh note, or a progress message for each loading state.
  3. Decide which actions can be queued and sent later, and how the user sees that they are waiting.
  4. Write the copy for every state in plain words.

Output format

  1. | Screen | Loading | Slow after N seconds | Failed | Offline |
  2. Copy for each state, for example: "No connection. Your order is saved on this phone and will send when you are back online."
  3. Retry rules: automatic retries, when to stop, and when to show a retry button.
  4. Queue rules for actions that must never be lost, including how a user sees and cancels queued items.
  5. 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.
loading statesoffline mode uxslow network designskeleton screenserror recoverymobile app ux

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity