An empty state appears when a user reaches a part of your product that has no content yet — an empty inbox, a new dashboard, a fresh account. Most products treat this as an edge case to handle. The best products treat it as a design opportunity, because the empty state is the first interaction many users have with a feature.
The Three Jobs of an Empty State
Explanation: What is this space for? New users don't always know what a feature does until they see it populated. The empty state should clearly communicate what will appear here when they use the product.
Motivation: Why should the user take action to fill it? What's the value they'll get? This is a conversion moment.
Direction: What's the first step? A clear call to action that answers "what do I do next?" eliminates the blank-page paralysis that causes new user drop-off.
Empty State Design Principles
Use real illustrations rather than generic placeholders — they communicate personality and context. Keep copy short and action-oriented. Don't make users work to understand what the feature does. The call to action should be the most obvious element on the screen.
The Specific vs Generic Problem
Generic empty states ("No data yet") are missed opportunities. Specific empty states ("You haven't made a transfer yet — send money to friends and family in seconds") are conversion tools. The specificity signals that the product was designed for the user's actual situation.