The importance of consistency
Consistency in design is important.
It allows users to use existing knowledge and thus makes it easier when being confronted with a new interface. If the whole system uses certain design principles, common layout, and wording of error messages, a good designer should use this to his advantage.
One of the first thing students in Human-Machine Interaction learn is how familiarity makes it easier for a user to get started with a new application. A lot of text books teach the reader how to consider spatial memory, visual perception and embodied cognition during design. Students learn the difference between working memory, long-term memory and short-term memory. Why humans remember things and why they forget. This is important knowledge to consider when designing a successful and easy-to-use interface.
For some reason all this knowledge is thrown away when it comes to real world development. Looking at music players for Windows 7 as an example, it is easy to see that each application sports its own interface principles, its own look and feel, its own way of structuring data and controls, its own world. Each new to the user. Each slightly different.
The Stoffi project
I will try not not make this article into a large ad for my project but a little history is still needed. For those of you not interested it's OK to skip this section and go right to the last (next) one.
The Stoffi project is an attempt to take what makes all music players great (such as a queue, history list, automatic scanner, silent upgrades, and vast support for file formats) and put these features into an interface that has been tailored to the operating system it runs on. The first being Windows 7.
It uses Jumplists, buttons in the taskbar previews, scans Windows 7 Libraries of type Music automatically, comes with an interface that is highly inspired by "native" applications such as Windows Explorer and the Control Panel. All with the aim of feeling like it was shipped with Windows 7 and more a part of it than a third party application.
Using the power of the community
Now the turn has come to other operating systems. Work has started to port this project to both Linux and Mac OS X. As I am not very familiar with OS X (I have never owned a Mac) and I have been away from KDE for 5 years and Gnome for 3 years, I need your help to create this same feeling of a "native" application.
So please, tell me in the comments what I should focus on, where should the interface draw inspiration from, what principles need to be adhered to, what should I avoid. Are there any features that should be included (like how Windows 7 has Libraries, Jumplists and Taskbar thumbnails)? Anything from installation, upgrades, look, feel, icons, dialogs or message phrasing.
No user, no matter his platform of choice, should ever feel like a second class citizen. Each user should get the impression that the application was designed for his operating system only.
About the author
Christoffer Brodd-Reijer is a student at Uppsala University in Sweden where he studies computer science. In his spare time he works on his pet project Stoffi or reads articles and comments on OSNews.