<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Icon Analysis</title>
	<atom:link href="http://boxesandarrows.com/icon-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/icon-analysis/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Mon, 20 May 2013 13:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: austingovella</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6086</link>
		<dc:creator>austingovella</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6086</guid>
		<description><![CDATA[This kicks ass. I don&#039;t have any better words.

Very technical, but now we can evaluate the usability of our icons. Sweet!]]></description>
		<content:encoded><![CDATA[<p>This kicks ass. I don&#8217;t have any better words.</p>
<p>Very technical, but now we can evaluate the usability of our icons. Sweet!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: donnamaurer</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6087</link>
		<dc:creator>donnamaurer</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6087</guid>
		<description><![CDATA[Holy cow. This is amazing!!!!!]]></description>
		<content:encoded><![CDATA[<p>Holy cow. This is amazing!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kodia</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6088</link>
		<dc:creator>kodia</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6088</guid>
		<description><![CDATA[Great piece. I love the analysis of M versus P channels. 

But I would add a &#039;third dimension&#039;. This is illustrated in figure 1: the red icon on the right is clear to see. But not because of either the M or P channel. It&#039;s clear to see because it&#039;s red and the other icons aren&#039;t. Color is a great way to &#039;lead&#039; the eye even before the M or P channels kick in.
I myself recently designed some icons for a image editor. In the design, the selecting tools are distiguished from other tools by giving them a green overall cast.  They are easy to distinghuish because their color is different, not because of their shape or details. Colors work primarily in the overall view of the whole design. You can&#039;t attribute it&#039;s effect to a single icon only.]]></description>
		<content:encoded><![CDATA[<p>Great piece. I love the analysis of M versus P channels. </p>
<p>But I would add a &#8216;third dimension&#8217;. This is illustrated in figure 1: the red icon on the right is clear to see. But not because of either the M or P channel. It&#8217;s clear to see because it&#8217;s red and the other icons aren&#8217;t. Color is a great way to &#8216;lead&#8217; the eye even before the M or P channels kick in.<br />
I myself recently designed some icons for a image editor. In the design, the selecting tools are distiguished from other tools by giving them a green overall cast.  They are easy to distinghuish because their color is different, not because of their shape or details. Colors work primarily in the overall view of the whole design. You can&#8217;t attribute it&#8217;s effect to a single icon only.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: putchavn</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6089</link>
		<dc:creator>putchavn</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6089</guid>
		<description><![CDATA[I have studied Image Processing and used filtering conceptually.  It is inspiring to see practical application of such significance explained so clearly.  

The explanation of &quot;M and P Pathways&quot;, the use of the &quot;Box Plots&quot; the reasoning, and conclusion are all exemplary-- of presenting the complex subject lucidly and also of the method to do so for any complex subject.]]></description>
		<content:encoded><![CDATA[<p>I have studied Image Processing and used filtering conceptually.  It is inspiring to see practical application of such significance explained so clearly.  </p>
<p>The explanation of &#8220;M and P Pathways&#8221;, the use of the &#8220;Box Plots&#8221; the reasoning, and conclusion are all exemplary&#8211; of presenting the complex subject lucidly and also of the method to do so for any complex subject.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jannacameron</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6090</link>
		<dc:creator>jannacameron</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6090</guid>
		<description><![CDATA[This is great!  I have some unique icons sizes that I would like to use this for.  Could you provide the equation you used to calculate the radius?

Also, do you have any suggestions for how the icons should be spaced in the trial file?  If the icons are close together in reality, should they be close together in the trial file (which would possibly blur them together)?]]></description>
		<content:encoded><![CDATA[<p>This is great!  I have some unique icons sizes that I would like to use this for.  Could you provide the equation you used to calculate the radius?</p>
<p>Also, do you have any suggestions for how the icons should be spaced in the trial file?  If the icons are close together in reality, should they be close together in the trial file (which would possibly blur them together)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dustinh</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6091</link>
		<dc:creator>dustinh</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6091</guid>
		<description><![CDATA[Great work here; I&#039;d really like to see more things of this nature... specifically how to actually design icons which will bring out the necessary differences for quick identification.

I work on in-vehicle navigation systems and we&#039;re definately more than attune to the &#039;driving condition&#039; where the system needs to be usable to a point, but with as little distraction as possible. (Honestly much of our particular interface is disabled while driving, but what is functional is primarily large icons with supporting short-text.)

I&#039;m really thankful for this kind of work being done.]]></description>
		<content:encoded><![CDATA[<p>Great work here; I&#8217;d really like to see more things of this nature&#8230; specifically how to actually design icons which will bring out the necessary differences for quick identification.</p>
<p>I work on in-vehicle navigation systems and we&#8217;re definately more than attune to the &#8216;driving condition&#8217; where the system needs to be usable to a point, but with as little distraction as possible. (Honestly much of our particular interface is disabled while driving, but what is functional is primarily large icons with supporting short-text.)</p>
<p>I&#8217;m really thankful for this kind of work being done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mqueen</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6092</link>
		<dc:creator>mqueen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6092</guid>
		<description><![CDATA[I just mentioned in an email to Dustin Hamilton that he hit the nail on the head, distance filtering of icons is an evaluative technique -- not a design technique. My knee-jerk reaction of how to coerce this method into a design tool is to create a plug-in for Photoshop or GIMP (preferably) that would allow an auto-updated window of the design space filtered at set distances. That way all design decisions (small and large) could be made in the context of the filtered frequency views. I imagine there is someone out there with enough talent and time to create such a tool. It seems like it would be useful.]]></description>
		<content:encoded><![CDATA[<p>I just mentioned in an email to Dustin Hamilton that he hit the nail on the head, distance filtering of icons is an evaluative technique &#8212; not a design technique. My knee-jerk reaction of how to coerce this method into a design tool is to create a plug-in for Photoshop or GIMP (preferably) that would allow an auto-updated window of the design space filtered at set distances. That way all design decisions (small and large) could be made in the context of the filtered frequency views. I imagine there is someone out there with enough talent and time to create such a tool. It seems like it would be useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael_andrews</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6093</link>
		<dc:creator>michael_andrews</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6093</guid>
		<description><![CDATA[I&#039;ll be brave and admit I don&#039;t understand everything here -- the prose is clear, but my brain is small.  

My gut impression is that designers rely too much on icons.  They seem difficult to distinguish the more graphically elaborate and three-dimensional they become.  The greater the number of distinctions icons try to make, they less successful they convey these distinctions, especially when viewed in the M-channel.

Seems it is difficult to provide sufficient discrimination when there are numerous icons.  I don&#039;t have a sense of how many different unique low frequency icons are possible to display at once.  Could one have 20 icons that would all have sufficiently unique frequencies so that users could tell each any pair of them apart?]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ll be brave and admit I don&#8217;t understand everything here &#8212; the prose is clear, but my brain is small.  </p>
<p>My gut impression is that designers rely too much on icons.  They seem difficult to distinguish the more graphically elaborate and three-dimensional they become.  The greater the number of distinctions icons try to make, they less successful they convey these distinctions, especially when viewed in the M-channel.</p>
<p>Seems it is difficult to provide sufficient discrimination when there are numerous icons.  I don&#8217;t have a sense of how many different unique low frequency icons are possible to display at once.  Could one have 20 icons that would all have sufficiently unique frequencies so that users could tell each any pair of them apart?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mqueen</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6094</link>
		<dc:creator>mqueen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6094</guid>
		<description><![CDATA[I’m not sure whether designers rely too much on icons though I know they are a popular way to represent actions (cut/paste) and categories (media file vs. word document) – which requires care (ex. “is this icon on the web an action or a category, or both?”).
The necessity of having 20 visually unique and distinguishable icons sounds like quite a design problem … the main problem being, “why is that a necessity?” Suppose we cut this 20 to 15 and partition them out. For example we have a web application that has 3 modes while each mode has a toolbar holding 5 icons. The user only sees 5 icons in the toolbar at time and we will decide that icons appearing in menus are preclassified differently in the mind of the user than icons that persist in the UI. The point isn’t that a user can distinguish between a low frequency representation of an icon in the first toolset and the second. The point is that they can easily distinguish between the currently available tools (then we leave the problems arising from modal issues to another type of analysis). Finally, suppose we would rather not rely on icons (after all they can be expensive) and opt for well thought out labels in our UI. Believe it or not, labels have low frequency components as well! The large letter forms of capitols, risers, and descenders (ex. “X”, “t”, “g”) coupled with the amount of kerning and line space contributes to the recognition of labels. We use the P channel (specifically, “detailed shape”) to read the labels yet rely on low frequency components to aide the identification of a word. Some reading research suggests that we actually don’t “read” all the letters in a word. Rather, we recognize a word by its large distinguishing visual features. We could argue that large visually distinguishing features are low frequency components. Does this make sense (perhaps improve the usefulness of this technique for you at all?).]]></description>
		<content:encoded><![CDATA[<p>I’m not sure whether designers rely too much on icons though I know they are a popular way to represent actions (cut/paste) and categories (media file vs. word document) – which requires care (ex. “is this icon on the web an action or a category, or both?”).<br />
The necessity of having 20 visually unique and distinguishable icons sounds like quite a design problem … the main problem being, “why is that a necessity?” Suppose we cut this 20 to 15 and partition them out. For example we have a web application that has 3 modes while each mode has a toolbar holding 5 icons. The user only sees 5 icons in the toolbar at time and we will decide that icons appearing in menus are preclassified differently in the mind of the user than icons that persist in the UI. The point isn’t that a user can distinguish between a low frequency representation of an icon in the first toolset and the second. The point is that they can easily distinguish between the currently available tools (then we leave the problems arising from modal issues to another type of analysis). Finally, suppose we would rather not rely on icons (after all they can be expensive) and opt for well thought out labels in our UI. Believe it or not, labels have low frequency components as well! The large letter forms of capitols, risers, and descenders (ex. “X”, “t”, “g”) coupled with the amount of kerning and line space contributes to the recognition of labels. We use the P channel (specifically, “detailed shape”) to read the labels yet rely on low frequency components to aide the identification of a word. Some reading research suggests that we actually don’t “read” all the letters in a word. Rather, we recognize a word by its large distinguishing visual features. We could argue that large visually distinguishing features are low frequency components. Does this make sense (perhaps improve the usefulness of this technique for you at all?).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mancjew</title>
		<link>http://boxesandarrows.com/icon-analysis/#comment-6095</link>
		<dc:creator>mancjew</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/icon-analysis/#comment-6095</guid>
		<description><![CDATA[Great stuff! One of the best article I&#039;ve read in a while. 
This type of research strengthens the theory of how the brain works from &#039;On intelligence&#039; by Jeff Hawkins that I&#039;ve been reading. He suggests that our brain make predictions and process information at the same time. In this case, our brain makes a prediction of what the icon is from the blurry details received and from our own memory. 

I&#039;m interested to know if there&#039;s research with familliar icons/signs together with spatial frequency. I think what the user already knows add a big difference to recognition, e.g. red and &#039;!&#039; usually means warning, danger. The common shape of &#039;arrow&#039;, &#039;home&#039; and &#039;refresh&#039; icons are already in our memory. I&#039;ve personally experienced the difference it makes when Yahoo decided to flip the icons horizontally, even though the elements in the icon was the same, I just couldnt recognise it. E.g. if we put the chimney of the house icon to the left side, it just doesn&#039;t look right.]]></description>
		<content:encoded><![CDATA[<p>Great stuff! One of the best article I&#8217;ve read in a while.<br />
This type of research strengthens the theory of how the brain works from &#8216;On intelligence&#8217; by Jeff Hawkins that I&#8217;ve been reading. He suggests that our brain make predictions and process information at the same time. In this case, our brain makes a prediction of what the icon is from the blurry details received and from our own memory. </p>
<p>I&#8217;m interested to know if there&#8217;s research with familliar icons/signs together with spatial frequency. I think what the user already knows add a big difference to recognition, e.g. red and &#8216;!&#8217; usually means warning, danger. The common shape of &#8216;arrow&#8217;, &#8216;home&#8217; and &#8216;refresh&#8217; icons are already in our memory. I&#8217;ve personally experienced the difference it makes when Yahoo decided to flip the icons horizontally, even though the elements in the icon was the same, I just couldnt recognise it. E.g. if we put the chimney of the house icon to the left side, it just doesn&#8217;t look right.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
