GNOME HIG Guidelines for Application Empty States

The GNOME Human Interface Guidelines (HIG) provide detailed design patterns for application empty states to ensure users are never left facing confusing, blank screens when an app has no content to display. These guidelines define how applications should inform users why a view is empty, reassure them that the software is functioning properly, and provide intuitive, actionable pathways to populate the interface with data.

Preventing Confusion and Reassurance

When a user opens an application or navigates to a view with no existing data—such as a new music library, an empty document list, or a clean inbox—a completely blank window can appear broken, unmaintained, or frozen. The primary purpose of an empty state in the GNOME HIG is reassurance. By presenting a deliberate, well-structured screen instead of void space, the application explicitly communicates that it is working as intended and is simply waiting for input or data.

Providing Context and Education

Empty states serve an educational role by explaining what belongs in a particular space. Rather than requiring users to read external documentation, the empty state uses concise messaging to describe the view's purpose. GNOME HIG emphasizes brevity and clarity:

• Header: A short, descriptive title summarizing the situation (e.g., "No Bookmarks").
• Body Text: A brief explanation offering context on what the view handles and how data appears there.

This contextual information ensures that first-time users immediately grasp the functionality of the interface without guesswork.

Guiding User Action

A fundamental principle of GNOME's empty state design is actionability. An empty screen should not be a dead end; it should actively guide the user on what to do next. The guidelines recommend embedding a primary call-to-action (CTA) button directly within the empty state layout. For instance, an empty photo manager might include an "Import Photos" button, or an empty contact list might display an "Add Contact" button. Providing a direct trigger eliminates friction and encourages immediate engagement.

Differentiating Scenarios Gracefully

GNOME HIG distinguishes between various types of empty states, advising developers to tailor the presentation based on the root cause:

• First Run: Welcoming the user and prompting initial setup or content creation.
• Cleared Content: Acknowledging that all items have been resolved or deleted (e.g., an empty task list or cleared notifications).
• No Search or Filter Results: Clarifying that no items match the current query, suggesting users check their spelling or broaden their search terms.

Ecosystem Consistency

GNOME establishes standardized visual patterns for empty states—typically featuring a large symbolic icon, a bold heading, secondary explanatory text, and a suggested action button centered in the view. Adhering to these patterns ensures visual and behavioral consistency across all native GNOME applications, allowing users to navigate new tools using familiar paradigms.