After learning more about “What is usability,” different ways to test usability, personas, scenarios, and scenario tasks, the research phase is over. We are now starting the usability testing phase which should be really exciting!
Next step is Reviewing GNOME design patterns, before we jump into creating scenario tasks for the final usability test. Throughout this week I spent some time getting familiar with GNOME Human Interface Guidelines(HIG).
The primary role of the HIG is to enable people to design high-quality, integrated and consistent applications for the GNOME platform. It also serves a secondary role in helping new GNOME contributors to learn the project’s design goals and approaches. Patterns and user interface elements form the core of the HIG. Together, they are the building blocks for application design.
Patterns are the primary elements that make up an application design. Some patterns are highly recommended and others are optional.
Core design patterns- Application menus, Dialog windows, Grids, Header bar menus, Header bars, In-app notifications, Lists, Notifications, Primary windows, Search, Selection mode.
Supplementary design patterns- Action bars, Empty placeholders, Info bars, Overload controls, Sidebar lists, View switchers.
For more details and appropriate uses of each pattern, I suggest visiting GNOME design patterns page, since they are explained really well there.
The goal for the usability test is to examine as many Design Patterns as possible. I managed to create a 7×7 matrix to better understand what design patterns are used across different applications.
So, we can notice how many patterns are being used in each application:
Nautilus, Software, Web, Music, and Gedit: 5 patterns
Photos: 6 patterns
Maps: 4 patterns
We can also notice that the most used patterns are: Application Menus, Primary Windows, Header Bars, and Search.
Next week I will be creating a “set” of scenario tasks for these particular applications and some of their features!