Lukas Mathias writes a very interesting and insightful blog posting on the right degree of realism for UI design. Essentially, button icons can’t be too realistic or they are confusing, and they can’t be too vague or they are also confusing. However, with application icons (icons on the desktop), more realism is essential as it differentiates the program from others.
A great (but short) read with lots of pictures: http://ignorethecode.net/blog/2010/01/21/realism_in_ui_design/
I would like to elaborate on Mathias’ article however, saying that in the former; button icons on an interface, the realism is confusing mainly because it breaks conceptual standards. Some time ago, we did not have the technological capacity to create icons that were very realistic. So for a long time, these vague looking icons developed into design patterns. The camera button icon (demonstrated in Mathias’ article) is vague, yet universally accepted to demonstrate ‘Camera’ or ‘Take a picture’. A more realistic camera button icon would break this pattern, therefore beg consumers to question its functionality- to question whether the realism was intentional, suggesting that its function is not to ‘Take a picture’, or to question if it a button at all.
Another reason that realistic icons are confusing is that realistic icons are often quite detailed, and therefore it is likely that the icon used by each program would look significantly different. This forces users to figure out the meaning of the icon each time they view it (recall over recognition – a violation of usability guidelines).
Although a camera icon for ‘Take a Picture’ is very intuitive, there are some icons that are not intuitive to their functionality, yet we continue to use them as an industry standard. We take a ‘cog’ in a program to represent ‘More/Advanced Options’; however, in real life a cog does not represent this. We *could* change to a different and “more intuitive” icon, but then users would be confused as this breaks the design pattern we have become accustomed to.
The Application Icon is different because it wants to break these design patterns. Windows Media Player is in direct competition with QuickTime Player, therefore Microsoft and Apple respectively want these applications to have markedly different icons. Perhaps this is also a design pattern – perhaps we have come to accept and expect that program icons will be all different.
It’s amazing how something so small and seemingly insignificant such as the level of detail in icons really affects our overall experience of a product. A great article by Mathias that really opens up a world of ideas.
Thanks to William Darling for finding and passing along this interesting blog.