Augment

Empty States in SaaS: Turning Blank Screens into Activation

An empty screen is the first thing new users see in many features. Treat it as a chance to teach and to start the task.

Hand-drawn mobile app wireframes on paper
Photo by Amélie Mourichon on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • Empty states do three jobs: tell the status, teach the feature, and offer the next step.
  • Never leave a container blank without explanation.
  • Use a clear primary action that starts the task right there.
  • Distinguish between empty because new, empty because filtered, and empty because of an error.

Three kinds of empty

TypeCauseWhat to show
First useNothing created yetWhat this area is for and a button to create the first item
No resultsA search or filter matches nothingSay so, show the active filters, and offer to clear them
ClearedThe user completed or removed everythingA short acknowledgment, and optionally what to do next
ErrorLoading failedWhat went wrong and a way to retry

Treating them all the same, with a blank panel or a vague "No data", is a common source of confusion.

What NN/g recommends

NN/g's guidance on empty states in complex applications points to three themes: communicate system status, offer learning cues, and provide direct pathways to key tasks. A blank container does none of these. It also risks the user thinking the app is broken.

They also warn against messages that change a moment later. A "No records" note that is replaced a second later by a list makes people distrust the interface. Show a loading state until you know the answer.

A pattern that works

An effective empty state

A plain headline
Say what belongs here in a few words.
One supporting line
Explain the benefit or what will appear.
A primary action
A button that starts the task, not a link to documentation.
An illustration or example
Optional. Use it to show what a filled state looks like.

Write it in your users' words

Skip "No items found". Try "No invoices yet. Create your first invoice to get paid." Specific, short, and helpful. Test the copy with a few new users to see if they know what to do next.

Frequently Asked Questions

What a screen shows when there is no content yet, no results, or nothing left to do.

Sources and further reading

  1. Designing Empty States in Complex Applications: 3 GuidelinesNielsen Norman Group · Published · Updated · Accessed
  2. Shopify PolarisShopify · Undated page · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Amélie Mourichon on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

Empty States in SaaS: Turning Blank Screens into Activation | Augment. Lab