Design
Empty state that earns its keep
Explain, then give the one action that fills it.
- empty state
- onboarding
- ux writing
The prompt
Write the empty state for {{screen}}.
The user's next step is: {{action}}
Give me a heading of at most six words, one line of body that says why the
screen is empty rather than apologising for it, and one button or hint pointing
at that action. If the action needs no button because it happens outside the
app, say so and write the hint instead.
Avoid "No items yet" as a heading — it tells the user something they can already
see. What to fill in
- {{screen}}
- Which screen — e.g. snip history, first launch, nothing copied yet
- {{action}}
- The action that fills it — e.g. copy something anywhere on the Mac
117 prompts, in the app you already paste from
The whole library, searchable, with your own prompts alongside it. Free to browse here; Pro to keep them a keystroke away on every device.