> If you are going to change a standard UI behavior, you better have good reason for it; looking cool doesn’t count.
This is why I don't use Chrome (browser or otherwise), FF 4.0, IE 9, or any of the legions of applications that ignore the basics of functional UI design.
For the vast majority of us, the computer is a tool, not a toy. I have work to do, so trying to figure out where you've hidden key features of your application is something I haven't the time or the patience for.
If it doesn't have a menu bar I won't waste time with it.
No good can ever come out of change. If things aren't the way I recognize them and like them, then they are obviously inferior because as we all know, functional UI design never changes. The principles that we had when Windows XP came out should still be in use because that's what I'm familiar with.
And I completely agree with you about using the a computer as a tool not a toy. If I can't immediately change the tool in a way that is familiar to me, it is worthless to me. For instance, the first thing I do when I get a hammer is take it apart and see what kind of different colors I can make the handle. That's how I know it's a good and usable tool. And I've found that the most customizable tools are usually the most usable tools. If I can't choose the font face used on my screwdrivers, I don't even bother.
I think we got two different things out of the article. It seems like you got the impression that it was saying that changing things shouldn't happen. I got the point that change for the sake of change is stupid. But if you identify behaviors that people do and don't do, and you change your product accordingly (like Chrome has done) then it's probably a good case for change.
Chrome has a single icon (wrench, far right) to replace the entire menu system. The first time I used Chrome I was thrown by the lack of a menu bar, but only for the five seconds or so that it took me to find that button.
After getting used to it (another five seconds) I now prefer it to the standard system of using >1cm of space for something I rarely use in a web browser.
At least with Firefox 4 if you hit alt and release it brings up the menu bar, though that may not be enough to make you happy (understandably so, it irks me when the menu is removed from an app that used to have it).
How often do you need something from the menu bar on a web browser? Very rarely is probably the answer. I think Chrome understood this, and optimized their interface around the features most commonly used. Screen real estate is as valuable as private islands, there's no reason to waste an inch at the top of the screen, when you can condense it to half an inch, and get the same functionality.
This is why I don't use Chrome (browser or otherwise), FF 4.0, IE 9, or any of the legions of applications that ignore the basics of functional UI design.
For the vast majority of us, the computer is a tool, not a toy. I have work to do, so trying to figure out where you've hidden key features of your application is something I haven't the time or the patience for.
If it doesn't have a menu bar I won't waste time with it.