<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Usability Friction</title>
	
	<link>http://usabilityfriction.com</link>
	<description>Usability shouldn't be a drag</description>
	<lastBuildDate>Wed, 18 Mar 2009 16:15:53 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForUsabilityFriction" /><feedburner:info uri="commentsforusabilityfriction" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>Comment on iLife and the Untitled Document Syndrome by Ashley Towers</title>
		<link>http://usabilityfriction.com/2009/02/21/ilife-and-the-untitled-document-syndrome/comment-page-1/#comment-142</link>
		<dc:creator>Ashley Towers</dc:creator>
		<pubDate>Wed, 18 Mar 2009 16:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=350#comment-142</guid>
		<description>The iApps can be configured to some degree - probably not as much as it sounds that you want to. But the whole point is that you are worrying about manually managing a file structure - it's not much better than having files in a filing cabinet!

With the iApp approach - the files (if you care to look, and I don't very often!) are logically organised e.g. photos are in a hierarchy for by year/month/date then the image files themselves are what ever you want to call them. Any albums are just symbolic links to the same files. I can't think of how I'd do it better manually!

I bet I could find an arbitrary picture using iPhoto (an app designed from the ground up to manage photos) quicker than you could using your file explorer - however good your hierarchy! 

The location of the file is irrelevant to me - I just have better things to do with my time than to manually keep my filing structure in order - my computer is much better at doing mundane tasks. What counts is how quick I can find the file to print/edit/whatever. As long as I'm safe in the knowledge that if I ever wanted to switch OS or whatever, my files are in a sensible (and easily importable) structure.</description>
		<content:encoded><![CDATA[<p>The iApps can be configured to some degree &#8211; probably not as much as it sounds that you want to. But the whole point is that you are worrying about manually managing a file structure &#8211; it&#8217;s not much better than having files in a filing cabinet!</p>
<p>With the iApp approach &#8211; the files (if you care to look, and I don&#8217;t very often!) are logically organised e.g. photos are in a hierarchy for by year/month/date then the image files themselves are what ever you want to call them. Any albums are just symbolic links to the same files. I can&#8217;t think of how I&#8217;d do it better manually!</p>
<p>I bet I could find an arbitrary picture using iPhoto (an app designed from the ground up to manage photos) quicker than you could using your file explorer &#8211; however good your hierarchy! </p>
<p>The location of the file is irrelevant to me &#8211; I just have better things to do with my time than to manually keep my filing structure in order &#8211; my computer is much better at doing mundane tasks. What counts is how quick I can find the file to print/edit/whatever. As long as I&#8217;m safe in the knowledge that if I ever wanted to switch OS or whatever, my files are in a sensible (and easily importable) structure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iLife and the Untitled Document Syndrome by Richard</title>
		<link>http://usabilityfriction.com/2009/02/21/ilife-and-the-untitled-document-syndrome/comment-page-1/#comment-141</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Wed, 18 Mar 2009 11:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=350#comment-141</guid>
		<description>Yeah but can you change that default behaviour? What if you have your own scheme for file storage? A particular naming scheme, and locations to put those  files. Where to keep the latest and where to store the archives. Can I customise my Mac to accommodate my schema?

You suggest I should let go and conform to Mr. Job's ideal but did he ever consider that his ideal is not suited to me and the way _I_ work? i.e. the way that works for me. I can understand why having a one size fits all solution would be an advantage to a beginner but to a person with thousands of files gathered over the years it can only be a bottleneck.

I want to know where my files are because:
- I don't want them locked into a particular OS's schema.
- I want to be able to blitz and re-install a different OS without my files being tied into my old OS's architecture.
- I want to move them from one filesystem type to another to utilise advances in technology.
- Maybe my filing system makes more sense to me than Mr. Jobs.</description>
		<content:encoded><![CDATA[<p>Yeah but can you change that default behaviour? What if you have your own scheme for file storage? A particular naming scheme, and locations to put those  files. Where to keep the latest and where to store the archives. Can I customise my Mac to accommodate my schema?</p>
<p>You suggest I should let go and conform to Mr. Job&#8217;s ideal but did he ever consider that his ideal is not suited to me and the way _I_ work? i.e. the way that works for me. I can understand why having a one size fits all solution would be an advantage to a beginner but to a person with thousands of files gathered over the years it can only be a bottleneck.</p>
<p>I want to know where my files are because:<br />
- I don&#8217;t want them locked into a particular OS&#8217;s schema.<br />
- I want to be able to blitz and re-install a different OS without my files being tied into my old OS&#8217;s architecture.<br />
- I want to move them from one filesystem type to another to utilise advances in technology.<br />
- Maybe my filing system makes more sense to me than Mr. Jobs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How am I supposed to know I can tilt the iPhone?! by Computing Posts From Across The Web Part II : KillerCodingNinjaBunny</title>
		<link>http://usabilityfriction.com/2008/08/27/how-am-i-supposed-to-know-i-can-tilt-the-iphone/comment-page-1/#comment-135</link>
		<dc:creator>Computing Posts From Across The Web Part II : KillerCodingNinjaBunny</dc:creator>
		<pubDate>Tue, 20 Jan 2009 14:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=43#comment-135</guid>
		<description>[...] How am I supposed to know I can tilt the iPhone?! - A usability post looking at the iPhones tilt function, something which is completely unnatural to those who do not know about it. [...]</description>
		<content:encoded><![CDATA[<p>[...] How am I supposed to know I can tilt the iPhone?! &#8211; A usability post looking at the iPhones tilt function, something which is completely unnatural to those who do not know about it. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be careful with iPhone orientation specific content by Bookmarks about Usability</title>
		<link>http://usabilityfriction.com/2008/08/22/be-careful-with-iphone-orientation-specific-content/comment-page-1/#comment-132</link>
		<dc:creator>Bookmarks about Usability</dc:creator>
		<pubDate>Tue, 16 Dec 2008 23:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=39#comment-132</guid>
		<description>[...] - bookmarked by 6 members originally found by kakashisaidhi on 2008-11-16  Be careful with iPhone orientation specific content  http://usabilityfriction.com/2008/08/22/be-careful-with-iphone-orientation-specific-content/ - [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; bookmarked by 6 members originally found by kakashisaidhi on 2008-11-16  Be careful with iPhone orientation specific content  <a href="http://usabilityfriction.com/2008/08/22/be-careful-with-iphone-orientation-specific-content/" rel="nofollow">http://usabilityfriction.com/2008/08/22/be-careful-with-iphone-orientation-specific-content/</a> &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Importance of Conventions by Nathan Pledger</title>
		<link>http://usabilityfriction.com/2008/11/28/the-importance-of-conventions/comment-page-1/#comment-121</link>
		<dc:creator>Nathan Pledger</dc:creator>
		<pubDate>Fri, 28 Nov 2008 09:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=302#comment-121</guid>
		<description>I agree. You learn a lot of conventions, and then when you design something yourself you have to remember the subconscious learning you have so you don't make mistakes. Some metaphors, icons and techniques are so discrete you don't realise you are using an established control technique. The "triangle on it's side" does everything from "Play" to "Build and Run" - either function it's purpose is pretty clear.

The iPhone. For a technologically inferior phone, this phone seems to have an unwarranted level of hype, which is typical of Jobs. I'm willing to accept it's a preference thing, maybe people prefer the usability which is admittedly a key feature of a Mac (personal preference only, not that any other platform is fundamentally harder to use). But the volume control clearly weakens the "usability" card. If the screen is tall, tough, you need to be as clever in your UI design as you do when your makign tarty coverflow controls. They could of course put a nice, tactile rocker switch on the side of the device like every other phone has - which is physically re-inforced to prevent accidental holding down and consequent deafening.

@programx</description>
		<content:encoded><![CDATA[<p>I agree. You learn a lot of conventions, and then when you design something yourself you have to remember the subconscious learning you have so you don&#8217;t make mistakes. Some metaphors, icons and techniques are so discrete you don&#8217;t realise you are using an established control technique. The &#8220;triangle on it&#8217;s side&#8221; does everything from &#8220;Play&#8221; to &#8220;Build and Run&#8221; &#8211; either function it&#8217;s purpose is pretty clear.</p>
<p>The iPhone. For a technologically inferior phone, this phone seems to have an unwarranted level of hype, which is typical of Jobs. I&#8217;m willing to accept it&#8217;s a preference thing, maybe people prefer the usability which is admittedly a key feature of a Mac (personal preference only, not that any other platform is fundamentally harder to use). But the volume control clearly weakens the &#8220;usability&#8221; card. If the screen is tall, tough, you need to be as clever in your UI design as you do when your makign tarty coverflow controls. They could of course put a nice, tactile rocker switch on the side of the device like every other phone has &#8211; which is physically re-inforced to prevent accidental holding down and consequent deafening.</p>
<p>@programx</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Be careful with iPhone orientation specific content by Gavin</title>
		<link>http://usabilityfriction.com/2008/08/22/be-careful-with-iphone-orientation-specific-content/comment-page-1/#comment-89</link>
		<dc:creator>Gavin</dc:creator>
		<pubDate>Fri, 14 Nov 2008 16:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=39#comment-89</guid>
		<description>Have you seen bloombergs application for Iphone / Itouch. 

Very nice design. If you have the page up showing stocks for a certain company 1 way will show news story and small graph of share price. Rotate it and the graph is displayed full screen. Its a very nice design and works really well. It is free so I recommend you have a quick look.

I understand your concerns it would need to be labelled that your page is setup to change when roated. For a whole site maybe not but for a small section / about page it is possibly handy</description>
		<content:encoded><![CDATA[<p>Have you seen bloombergs application for Iphone / Itouch. </p>
<p>Very nice design. If you have the page up showing stocks for a certain company 1 way will show news story and small graph of share price. Rotate it and the graph is displayed full screen. Its a very nice design and works really well. It is free so I recommend you have a quick look.</p>
<p>I understand your concerns it would need to be labelled that your page is setup to change when roated. For a whole site maybe not but for a small section / about page it is possibly handy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iPod headphone disconnect automatic pause by Ashley Towers</title>
		<link>http://usabilityfriction.com/2008/08/20/ipod-headphone-disconnect-automatic-pause/comment-page-1/#comment-83</link>
		<dc:creator>Ashley Towers</dc:creator>
		<pubDate>Sun, 09 Nov 2008 19:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=28#comment-83</guid>
		<description>Hi Saac &amp; William - thanks for the comments. I had never heard of this problem until you mentioned it and from looking around it seems to be  fairly common! You are absolutely right that there should be a way to disable it!

I'm sure you've both researched the problem but just in case any one else stumbles across this post here's a few tips that have worked for others (as always - try the following at your own risk!).

The problem can be caused by the headphones losing contact with the jack so check:
1. Your headphones plug isn't loosely fitting
2. If you have  dirty contacts in the iPod jack socket. Try using some contact cleaner or blowing it with some compressed air

Other causes for the problem:
3. Some third party headphones have a metal rim around the base of the plug (seems to be especially common on high end models) this can sometimes short against the metal on the jack - confusing the iPod into thinking it needs to pause. 
Here you need to insulate it - most people have stuck a piece of tape between the two to prevent metal-to-metal contact. Alternatively, others have just bought an iPod remote to act as middle-man.

Hope this helps!</description>
		<content:encoded><![CDATA[<p>Hi Saac &#038; William &#8211; thanks for the comments. I had never heard of this problem until you mentioned it and from looking around it seems to be  fairly common! You are absolutely right that there should be a way to disable it!</p>
<p>I&#8217;m sure you&#8217;ve both researched the problem but just in case any one else stumbles across this post here&#8217;s a few tips that have worked for others (as always &#8211; try the following at your own risk!).</p>
<p>The problem can be caused by the headphones losing contact with the jack so check:<br />
1. Your headphones plug isn&#8217;t loosely fitting<br />
2. If you have  dirty contacts in the iPod jack socket. Try using some contact cleaner or blowing it with some compressed air</p>
<p>Other causes for the problem:<br />
3. Some third party headphones have a metal rim around the base of the plug (seems to be especially common on high end models) this can sometimes short against the metal on the jack &#8211; confusing the iPod into thinking it needs to pause.<br />
Here you need to insulate it &#8211; most people have stuck a piece of tape between the two to prevent metal-to-metal contact. Alternatively, others have just bought an iPod remote to act as middle-man.</p>
<p>Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iPod headphone disconnect automatic pause by William</title>
		<link>http://usabilityfriction.com/2008/08/20/ipod-headphone-disconnect-automatic-pause/comment-page-1/#comment-82</link>
		<dc:creator>William</dc:creator>
		<pubDate>Sun, 09 Nov 2008 17:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=28#comment-82</guid>
		<description>Dito, my 80GB  iPod classic pauses all the time virtually destroying it and now it's completely useless due to over engineering. If the feature like this exists then a method for disabling it must also exist. In products with such a wide customer base, attempting to assume how people will use the item will get you every time.</description>
		<content:encoded><![CDATA[<p>Dito, my 80GB  iPod classic pauses all the time virtually destroying it and now it&#8217;s completely useless due to over engineering. If the feature like this exists then a method for disabling it must also exist. In products with such a wide customer base, attempting to assume how people will use the item will get you every time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to make your user interface CRAP by 10 Ways to Improve Usability When You Thought it Was Too Late</title>
		<link>http://usabilityfriction.com/2008/09/08/how-to-make-your-user-interface-crap/comment-page-1/#comment-81</link>
		<dc:creator>10 Ways to Improve Usability When You Thought it Was Too Late</dc:creator>
		<pubDate>Thu, 06 Nov 2008 23:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=69#comment-81</guid>
		<description>[...] and Proximity. I wrote an in depth article about using CRAP to improve user experience in: How to make your user interface CRAP. These principles are easy to apply and can make a big difference without a huge amount of [...]</description>
		<content:encoded><![CDATA[<p>[...] and Proximity. I wrote an in depth article about using CRAP to improve user experience in: How to make your user interface CRAP. These principles are easy to apply and can make a big difference without a huge amount of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to make your user interface CRAP by 10 Ways to Improve Usability When You Thought it Was Too Late</title>
		<link>http://usabilityfriction.com/2008/09/08/how-to-make-your-user-interface-crap/comment-page-1/#comment-80</link>
		<dc:creator>10 Ways to Improve Usability When You Thought it Was Too Late</dc:creator>
		<pubDate>Thu, 06 Nov 2008 23:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityfriction.com/?p=69#comment-80</guid>
		<description>[...] and Proximity. I wrote an in depth article about using CRAP to improve user experience in: How to make your user interface CRAP. These principles are easy to apply and can make a big difference without a huge amount of [...]</description>
		<content:encoded><![CDATA[<p>[...] and Proximity. I wrote an in depth article about using CRAP to improve user experience in: How to make your user interface CRAP. These principles are easy to apply and can make a big difference without a huge amount of [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss><!-- Dynamic page generated in 0.400 seconds. --><!-- Cached page generated by WP-Super-Cache on 2010-03-06 05:27:05 -->
