Empty States Are Your Best Salesperson

Every user meets your empty states. Not most — every one. Before the first project, the first message, the first saved item, there is a screen with nothing to show, and it is statistically among the most-viewed surfaces in your product. It is also, in most apps, a grey illustration of a box and the words "Nothing here yet."

Nothing here yet is a strange thing to say to someone who just arrived. It describes the situation from the database's point of view. The table is empty; true. But the user isn't looking at a table. They're standing in the doorway of a product they were promised would change something, being told by the product itself that it contains nothing.

A working empty state has three jobs, in order. Show what this screen becomes — a ghosted preview of a populated screen outsells any illustration of a mailbox. Give exactly one action — not a toolbar, the single next step that creates the first real object. And set the emotional register — this is the one screen where the product speaks first, before the user has done anything to deserve an opinion.

The pattern to study is any product that makes the empty state do onboarding's job: the blank document that offers templates, the empty inbox that explains how messages arrive, the zero-state dashboard drawn with sample data. None of them say nothing here yet. They say: here is what here is for.