Before I get any further, I want to point two things out. Firstly, Google Chrome is a very early beta product. It’s not ready for your Gran to use yet, it may not be ready for you to use yet, depending on your disposition. So tread carefully. And let’s take this as an IR beta, and not a Google beta. I don’t expect it to be flawless, neither should you.
Secondly, I’m an OSX user (you’ll find that many people in the field of user experience favor Macs). As such I’m testing Chrome on an iMac through Parallels Desktop which is running a Win XP Pro Virtual Machine. Results are indicative of this setup.
Google seem intent on breaking some well established conventions with Chrome. We’ve seen with the iPhone that breaking established conventions can be a liberating thing, something that frees designers from the shackles of the past and allows them to come up with something truly great. There is, of course, a downside. Unless your new interface is truly intuitive, which is very difficult to do in an IT system, there’s going to be a steeper learning curve than usual. There’s also going to be mistakes and failures. And when you knowingly introduce failures and mistakes, you run the risk of user abandonment. Sometimes this will be abandonment of a task, but in cases like Chrome, and the iPhone, it will be abandonment of the tool.
The image to the right (below) highlights some of the differences you will notice between Chrome and a more conventional browser, in this case I’ve used FireFox version 3 on Windows XP in vanilla form.
I’ll be addressing each of these differences in turn." (Continued via The Usability Blog) [Usability Resources]