What is the empty state problem?


The empty state problem is something every designer encounters - it's that moment when someone first opens your app or arrives at a screen with no content yet. The temptation is to just show a blank page or maybe throw up a tutorial, but that's often the wrong move.

When Vevo tested their intro tour, they found most people were just skipping through without reading any of the copy. In a test with over 160,000 participants, getting rid of the tutorial actually increased the number of people who got into the app. More people completed sign-up too.

The real challenge is answering "What do I do now?" for users while balancing their needs with business goals. Empty states shouldn't just be blank pages - they need to guide users on what to do next with a clear call to action, maintain context so people know where they are, and maybe use placeholder content to show what the page will look like when populated.

The key insight is you want to get people to your app's core value as quickly as possible. Instead of front-loading tutorials and explanations, teach in the moment when things are relevant. For example, in an app I worked on where you could vote on things by swiping, we only showed the "swipe to skip" tip after someone pulled up for more content - right when they'd actually use that gesture.

Empty states are really an opportunity. When designed thoughtfully, they can reduce confusion and encourage engagement with your product. But the goal is always the same: get people engaged with the actual product, not stuck in some pre-game show.