Comments on: Google’s New Chrome Browser and Fitts’s Law http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/ The highlights and lowlights of usability Fri, 30 Oct 2009 11:02:27 -0700 http://wordpress.org/?v=2.9.1 hourly 1 By: Nathar Leichoz http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-64 Nathar Leichoz Thu, 25 Sep 2008 11:26:25 +0000 http://www.theusabilityblog.com/?p=32#comment-64 Maybe they did a study and found that people used the back-forward buttons more than switching tabs and so moved the back-forward buttons closer to the webpage and the tabs farther away. Maybe they did a study and found that people used the back-forward buttons more than switching tabs and so moved the back-forward buttons closer to the webpage and the tabs farther away.

]]> By: john http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-63 john Wed, 17 Sep 2008 07:13:53 +0000 http://www.theusabilityblog.com/?p=32#comment-63 Tabs at the top, besides Fitt's law advantages (re ian), also reuses the otherwise useless window header. I think Chrome is trying to minimize the total "toolbars" area. Merging the URL entry bar and the search bar is another strong example to maximize the browser area. Tabs at the top, besides Fitt’s law advantages (re ian), also reuses the otherwise useless window header. I think Chrome is trying to minimize the total “toolbars” area. Merging the URL entry bar and the search bar is another strong example to maximize the browser area.

]]> By: simon http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-59 simon Sun, 14 Sep 2008 09:22:44 +0000 http://www.theusabilityblog.com/?p=32#comment-59 You're absolutely right Ian, it's widely accepted that interface elements at the edge of the screen are calculated as having larger target areas than they physically posess. You're also right about areas that are near the top of the screen being particularly difficult, especially for users who have difficulty using a mouse. Looking at Chrome, the tabs aren't positioned at the top of the window, there's a gap above them. This, in my opinion puts them into that dangerous "not quite at the edge" area. And of course there's nothing to guarentee the browser must be used full screen anyway. You’re absolutely right Ian, it’s widely accepted that interface elements at the edge of the screen are calculated as having larger target areas than they physically posess. You’re also right about areas that are near the top of the screen being particularly difficult, especially for users who have difficulty using a mouse. Looking at Chrome, the tabs aren’t positioned at the top of the window, there’s a gap above them. This, in my opinion puts them into that dangerous “not quite at the edge” area. And of course there’s nothing to guarentee the browser must be used full screen anyway.

]]> By: ian http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-57 ian Sun, 14 Sep 2008 06:43:10 +0000 http://www.theusabilityblog.com/?p=32#comment-57 And actually stuff "near" the top of the screen (like the regular old tab positions) is actually pretty much the worst possible position to put anything on screen, because it is at a large distance from most stuff, but still of small "finite" size. And actually stuff “near” the top of the screen (like the regular old tab positions) is actually pretty much the worst possible position to put anything on screen, because it is at a large distance from most stuff, but still of small “finite” size.

]]> By: ian http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-56 ian Sun, 14 Sep 2008 06:38:53 +0000 http://www.theusabilityblog.com/?p=32#comment-56 Stuff on the perimeter of the screen actually has "infinite size" (you can aim for anywhere above the screen), essentially making the size part of the equation huge while only increasing the distance by a little bit. So when you apply Fitt's Law, stuff on the perimeter ends up having a big advantage. There are lots of HCI papers verifying this, and it is implied in the analysis of Fitt's Law. Mouse triggers on the corners are particularly effective (also papers documenting this). Stuff on the perimeter of the screen actually has “infinite size” (you can aim for anywhere above the screen), essentially making the size part of the equation huge while only increasing the distance by a little bit. So when you apply Fitt’s Law, stuff on the perimeter ends up having a big advantage. There are lots of HCI papers verifying this, and it is implied in the analysis of Fitt’s Law. Mouse triggers on the corners are particularly effective (also papers documenting this).

]]> By: Martin http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-55 Martin Fri, 12 Sep 2008 01:47:03 +0000 http://www.theusabilityblog.com/?p=32#comment-55 Yes, Chrome is doing things a little differently. Maybe I'm naive, but wouldn't they have had extensive user testing which backed up their tab position change? The interface looks quite different from the other browsers, would this not somehow intervene muscle memory? Personally I find it quite refreshing to use! But then again, I'm reading a usability blog. :) Yes, Chrome is doing things a little differently.

Maybe I’m naive, but wouldn’t they have had extensive user testing which backed up their tab position change?

The interface looks quite different from the other browsers, would this not somehow intervene muscle memory?

Personally I find it quite refreshing to use! But then again, I’m reading a usability blog. :)

]]> By: Google Chrome: A User Interface Review | The Usability Blog http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/comment-page-1/#comment-43 Google Chrome: A User Interface Review | The Usability Blog Thu, 04 Sep 2008 00:11:05 +0000 http://www.theusabilityblog.com/?p=32#comment-43 [...] The Usability Blog The highlights and lowlights of usability « Google’s New Chrome Browser and Fitts’s Law [...] [...] The Usability Blog The highlights and lowlights of usability « Google’s New Chrome Browser and Fitts’s Law [...]

]]>