First-Run Empty

First-run empty is the screen every new user hits the moment they finish signup. Nothing exists yet because they have done nothing yet. This state exists to close the dangerous gap between creating an account and doing the thing that makes the product valuable. It must teach the core loop, set the emotional tone, and hand the user a specific next action that beats closing the tab.

Teams ship this screen last and design it least. That is backwards. The first-run empty is not marketing. It is the product in its most honest form. Users arrive full of hope. Give them a shrug and they leave forever. No re-engagement email fixes that moment.

A first-run empty is not a zero-state. Zero-state assumes the user already knows your app and is looking at a fresh project. First-run has to explain what the app even is. Do not confuse the two. The knowledge gap is totally different. It is also not an error state. The user did not break anything. They just showed up.

The biggest confusion comes from the generic template trap. Most products use the same sad illustration and vague button for every empty screen. That erases all nuance. First-run needs to teach. Other states need to celebrate or rescue. Treat them the same and you waste the highest leverage real estate in your product.

Stripe nailed first-run empty years ago. New users land on a fully populated dashboard with test data. Charts have numbers. Tables have rows. A clear toggle says Viewing test data. One click flips to their real empty account. They see the destination before they build the path. Activation rates jumped. Figma shows example files in the drafts wall on first login. You learn the product by looking at it instead of staring at nothing.

Things 3 ships with an onboarding project that uses real tasks to teach every feature. Finish the list and you have used the app while clearing the first empty state. The next empty state feels like real life instead of failure. Granola offers a test recording or sample transcript on first launch so the AI tool never faces the chicken and egg problem. These teams treat the first-run as the product. Everyone else treats it like a footnote.

Deploy a rich first-run empty when your product needs user content before it becomes useful. Task managers, design tools, CRMs, and AI interfaces live or die here. The first sixty seconds predict retention better than the next sixty minutes. Fix this screen before you touch your onboarding flow.

Skip heavy first-run design for products with instant obvious value. A calculator or weather app does not need sample data and teaching illustrations. It feels like hand holding. The tradeoff is design time against activation lift. A strong first-run empty is the cheapest retention lever you have. A lazy one leaks users every single day.

Run the audit. Open an incognito window as a new user. Screenshot every blank surface. Label them. Ask three questions. Does it teach. Does it give a specific action. Does it sound like the brand. Most products discover ten to thirty empty states. Only one or two were designed on purpose. Start with first-run. It moves the graph fastest.

Combine two or three of the four moves. Sample data plus suggested actions works here. Add tone-setting copy that matches your voice. Never use all four at once. It gets noisy fast. Avoid the sad illustration at all costs. The user is not sad. They are waiting for you to keep your promise.

First-run empty is your product's handshake. Make it firm, clear, and human or do not bother.