Re:Foundations of a good UI
by matthewmacleod on Monday July 27, 2015 @10:04AM
(#9955238)
I think there's still value in this list of principles - they are so often violated that it seems that they are less than self-evident!
I've seen lots of engineers advocate for the opposite of consistency or convention in the past, when building particular features. Things like consistency; the attitude that your app doesn't have to follow the rules of the platform and act the same way as others do is surprisingly common!
Similarly, minimising clutter is often overlooked. How often do you see an engineer add a knob or checkbox to control a function without proper consideration of where that should appear in the workflow and whether or not it clutters the user's view? I definitely see that quite often.
So yeah, nobody will actively state that convention is bad, but many will treat it as being less important than it is. So it's definitely worth bearing these principles in mind, IMO.
I've seen lots of engineers advocate for the opposite of consistency or convention in the past, when building particular features. Things like consistency; the attitude that your app doesn't have to follow the rules of the platform and act the same way as others do is surprisingly common!
Similarly, minimising clutter is often overlooked. How often do you see an engineer add a knob or checkbox to control a function without proper consideration of where that should appear in the workflow and whether or not it clutters the user's view? I definitely see that quite often.
So yeah, nobody will actively state that convention is bad, but many will treat it as being less important than it is. So it's definitely worth bearing these principles in mind, IMO.