<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for The Usability Blog</title>
	<atom:link href="http://www.theusabilityblog.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theusabilityblog.com</link>
	<description>The highlights and lowlights of usability</description>
	<pubDate>Fri, 21 Nov 2008 03:39:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on Designing for Mobile Users by David Hamill</title>
		<link>http://www.theusabilityblog.com/usability-tips/17-designing-for-mobile-users/#comment-68</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Wed, 22 Oct 2008 09:27:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=17#comment-68</guid>
		<description>I don't really agree with your 'Focus on information' advice. You should always focus on tasks when creating a website. This advice does not change from device to device. However the device that is being used, may allow you to prioritise some tasks over others. Because the context of use is likely to be different.

This is what then puts into to question point 6. People tend to use a phone to access the internet because they are not at a computer. I'm not sure there is a great need to optimise every task for mobile use. Doing so will just clutter the important tasks that people using phones want to do.

The Right Move mobile site is a perfect example on focussing on the appropriate context of use. http://mobile.rightmove.co.uk/. Incidentally it focusses on one primary task.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really agree with your &#8216;Focus on information&#8217; advice. You should always focus on tasks when creating a website. This advice does not change from device to device. However the device that is being used, may allow you to prioritise some tasks over others. Because the context of use is likely to be different.</p>
<p>This is what then puts into to question point 6. People tend to use a phone to access the internet because they are not at a computer. I&#8217;m not sure there is a great need to optimise every task for mobile use. Doing so will just clutter the important tasks that people using phones want to do.</p>
<p>The Right Move mobile site is a perfect example on focussing on the appropriate context of use. <a href="http://mobile.rightmove.co.uk/" rel="nofollow">http://mobile.rightmove.co.uk/</a>. Incidentally it focusses on one primary task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by Has Google Chrome got room for Improvement or will it beat Firefox and IE? &#124; Josh Chandler's Blog</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-67</link>
		<dc:creator>Has Google Chrome got room for Improvement or will it beat Firefox and IE? &#124; Josh Chandler's Blog</dc:creator>
		<pubDate>Sun, 19 Oct 2008 21:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-67</guid>
		<description>[...] browser whether this means Google will begin to build out a more substantial UI is yet to be seen, UsabilityBlog.com had a good feature on the Chrome UI which you might want to check out, but I think for Google to be [...]</description>
		<content:encoded><![CDATA[<p>[...] browser whether this means Google will begin to build out a more substantial UI is yet to be seen, UsabilityBlog.com had a good feature on the Chrome UI which you might want to check out, but I think for Google to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by led</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-66</link>
		<dc:creator>led</dc:creator>
		<pubDate>Tue, 07 Oct 2008 06:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-66</guid>
		<description>well, chrome is not that fast. it is only a hype. with the kind of clutter it has it is bound to be much slower than IE</description>
		<content:encoded><![CDATA[<p>well, chrome is not that fast. it is only a hype. with the kind of clutter it has it is bound to be much slower than IE</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by Lee</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-65</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 26 Sep 2008 14:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-65</guid>
		<description>I agree that the average user shouldn’t want to use chromes task manager, but it is a great development tool.  If chrome didn’t have helpful development tools nobody would ever try to fix issues there site might have rendering on chrome.

I really like the fact that address bar is under the tabbar.  It just seems more correct.  But the whole thing is definitely still a beta.</description>
		<content:encoded><![CDATA[<p>I agree that the average user shouldn’t want to use chromes task manager, but it is a great development tool.  If chrome didn’t have helpful development tools nobody would ever try to fix issues there site might have rendering on chrome.</p>
<p>I really like the fact that address bar is under the tabbar.  It just seems more correct.  But the whole thing is definitely still a beta.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google&#8217;s New Chrome Browser and Fitts&#8217;s Law by Nathar Leichoz</title>
		<link>http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/#comment-64</link>
		<dc:creator>Nathar Leichoz</dc:creator>
		<pubDate>Thu, 25 Sep 2008 11:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=32#comment-64</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google&#8217;s New Chrome Browser and Fitts&#8217;s Law by john</title>
		<link>http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/#comment-63</link>
		<dc:creator>john</dc:creator>
		<pubDate>Wed, 17 Sep 2008 07:13:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=32#comment-63</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Tabs at the top, besides Fitt&#8217;s law advantages (re ian), also reuses the otherwise useless window header. I think Chrome is trying to minimize the total &#8220;toolbars&#8221; area. Merging the URL entry bar and the search bar is another strong example to maximize the browser area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by roberts</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-62</link>
		<dc:creator>roberts</dc:creator>
		<pubDate>Tue, 16 Sep 2008 23:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-62</guid>
		<description>there are so many advantages and features with Chrome, such as it's speed, for example; now if only they would take care it's quirky cookie management...</description>
		<content:encoded><![CDATA[<p>there are so many advantages and features with Chrome, such as it&#8217;s speed, for example; now if only they would take care it&#8217;s quirky cookie management&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by J. J. Gould</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-61</link>
		<dc:creator>J. J. Gould</dc:creator>
		<pubDate>Tue, 16 Sep 2008 15:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-61</guid>
		<description>Hi all --

Very good points as to Chrome.  My own biggest peeve is the current Bookmarking functionality and user flow; I find it hard to believe that the powers-that-be at Google did not simply mimic FF or IE7 browser-based bookmarking features for this Beta launch.  There is no need to break this convention if breaking it offers no real benefit (and in fact, more detriment than benefit).

However, on a tangent, I would really have to dispute that: "youâ��ll find that many people in the field of user experience favor Mac."  At least on this side of the pond (in Canada), I know of zero UX Professionals/IAs/Interaction Designers who work primarily in Mac.  For example, an established and extremely powerful Usability Test tool like TechSmith's Morae (http://www.techsmith.com/morae/systemreq.asp) has not been launched in Mac.  I find that telling.

It just smacks to me as yet more Microsoft and Vista bashing.  Sure they've ripped off so many of Apple's GUI elements, but it doesn't mean that UX Professionals wouldn't be using it without complaining every day.</description>
		<content:encoded><![CDATA[<p>Hi all &#8211;</p>
<p>Very good points as to Chrome.  My own biggest peeve is the current Bookmarking functionality and user flow; I find it hard to believe that the powers-that-be at Google did not simply mimic FF or IE7 browser-based bookmarking features for this Beta launch.  There is no need to break this convention if breaking it offers no real benefit (and in fact, more detriment than benefit).</p>
<p>However, on a tangent, I would really have to dispute that: &#8220;youâ��ll find that many people in the field of user experience favor Mac.&#8221;  At least on this side of the pond (in Canada), I know of zero UX Professionals/IAs/Interaction Designers who work primarily in Mac.  For example, an established and extremely powerful Usability Test tool like TechSmith&#8217;s Morae (http://www.techsmith.com/morae/systemreq.asp) has not been launched in Mac.  I find that telling.</p>
<p>It just smacks to me as yet more Microsoft and Vista bashing.  Sure they&#8217;ve ripped off so many of Apple&#8217;s GUI elements, but it doesn&#8217;t mean that UX Professionals wouldn&#8217;t be using it without complaining every day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google Chrome:  A User Interface Review by Dave Musson</title>
		<link>http://www.theusabilityblog.com/misc/37-google-chrome-user-interface-ui-usability-review/#comment-60</link>
		<dc:creator>Dave Musson</dc:creator>
		<pubDate>Tue, 16 Sep 2008 15:13:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=37#comment-60</guid>
		<description>Ah, web applications.  Thanks for pointing them out Francis because I'd missed them.  Interesting feature, now my Gmail can be in its own window instead of a tab.  Not sure if it is useful yet but at least I know about it now.  Something I'd missed.

Anyway I wanted to highlight the nightmare that is the downloads window, it is hard to find and all the 'downloaded file' options are hidden in the right click context window.  And my real issue; I'm downloading a file but no longer want to use the browser so I close it and guess what happened, the file download was cancelled.  Opps.  Beta or not that was annoying and against the 'norm' for browsers now a days.</description>
		<content:encoded><![CDATA[<p>Ah, web applications.  Thanks for pointing them out Francis because I&#8217;d missed them.  Interesting feature, now my Gmail can be in its own window instead of a tab.  Not sure if it is useful yet but at least I know about it now.  Something I&#8217;d missed.</p>
<p>Anyway I wanted to highlight the nightmare that is the downloads window, it is hard to find and all the &#8216;downloaded file&#8217; options are hidden in the right click context window.  And my real issue; I&#8217;m downloading a file but no longer want to use the browser so I close it and guess what happened, the file download was cancelled.  Opps.  Beta or not that was annoying and against the &#8216;norm&#8217; for browsers now a days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Google&#8217;s New Chrome Browser and Fitts&#8217;s Law by simon</title>
		<link>http://www.theusabilityblog.com/bad-usability/32-googles-new-chrome-browser-and-fittss-law/#comment-59</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Sun, 14 Sep 2008 09:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.theusabilityblog.com/?p=32#comment-59</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>You&#8217;re absolutely right Ian, it&#8217;s widely accepted that interface elements at the edge of the screen are calculated as having larger target areas than they physically posess. You&#8217;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&#8217;t positioned at the top of the window, there&#8217;s a gap above them. This, in my opinion puts them into that dangerous &#8220;not quite at the edge&#8221; area. And of course there&#8217;s nothing to guarentee the browser must be used full screen anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
