| name | ios-empty-states-and-first-run |
| description | Use when designing onboarding, first-run, zero-state, or no-data experiences for iOS apps so people understand what the product does, what to do next, and how to reach value quickly without heavy setup friction. |
iOS Empty States And First Run
The first useful action matters more than a long explanation.
Principles
- teach the next move, not the whole product
- keep onboarding narrow
- let users reach the real interface quickly
- empty states should reduce uncertainty
Good Empty State
- one clear title
- one useful supporting sentence
- one obvious action
- optional secondary hint only if needed
Avoid
- forcing setup before value
- long educational walls
- vague encouragement without an action
- dead-end empty states