These Human Interface Guidelines are primarily targeted towards new GTK and GNOME applications, with an emphasis on GNOME 3 integration. However, they are also intended to be useful to cross-platform applications, as well as older applications, which may have been designed and implemented in accordance with the GNOME 2 HIG.
Generally speaking, the design patterns found in the HIG can be used on any desktop platform. Most of the conventions, like menus and menu buttons, views and view switchers, and popovers, are common and will be generally understood.
The primary example of a design pattern that varies across desktop platforms is the, which takes different forms on different platforms. See the design page on this for more guidance on cross-platform considerations.
These Human Interface Guidelines are an evolution of the GNOME 2 HIG. Applications that follow the new version of the HIG will use space more efficiently, will provide a more focused user experience, and will use modern interpretations of key functionality, such as search, online integration, or notifications.
Following some of the design patterns in these guidelines may imply larger-scale design changes for GNOME 2 style applications, particularly if those applications are complex. In particular, replacing window title bars andwith a could be a big change for your application.
However, much of the advice contained within this HIG can be incorporated into GNOME 2 style applications with minimal disruption, and will lead to an improved experience for users. This includes:
Utilizing new user interface elements, such as popovers.
Guidance on new GTK abilities, like animations.
Modernized guidance on subjects such as visual layout, typography and icon usage.
Incorporating these elements of the guidelines can enhance your application without requiring a major redesign, and all GTK and GNOME applications can benefit from them.
These Human Interface Guidelines have been designed to assist you in determining the best design for your application, rather than proposing a single template to be used in all applications. As such, while they recommendover , they provide guidance on both approaches.
This work is licensed under a.
Got a comment? Spotted an error? Found the instructions unclear? Send feedback about this page.