<?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: Precise to a Fault</title>
	<atom:link href="http://blog.twigkit.com/precise-to-a-fault/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.twigkit.com/precise-to-a-fault/</link>
	<description>A blog about search, user experience, and development.</description>
	<lastBuildDate>Mon, 10 May 2010 12:14:33 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tyler Tate</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-21</link>
		<dc:creator>Tyler Tate</dc:creator>
		<pubDate>Wed, 23 Dec 2009 08:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-21</guid>
		<description>Jon brings up a really good point. I completely agree that it&#039;s a significant problem that, in this case, 24K looks smaller than 9.3K. Ideally larger numbers would always appear visually larger than small numbers. While there isn&#039;t a straightforward method of doing decimal-aligning in HTML, we are working on turning the grey capsules surrounding the numbers into a sort of bar chart, where we programmatically manipulate the width of each capsule. This way, there will always be a visual indicator that instantly communicates the proportionality of one item to another.

Thanks Jon for the thoughtful feedback!</description>
		<content:encoded><![CDATA[<p>Jon brings up a really good point. I completely agree that it&#8217;s a significant problem that, in this case, 24K looks smaller than 9.3K. Ideally larger numbers would always appear visually larger than small numbers. While there isn&#8217;t a straightforward method of doing decimal-aligning in HTML, we are working on turning the grey capsules surrounding the numbers into a sort of bar chart, where we programmatically manipulate the width of each capsule. This way, there will always be a visual indicator that instantly communicates the proportionality of one item to another.</p>
<p>Thanks Jon for the thoughtful feedback!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Gunnar Wold</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-20</link>
		<dc:creator>Jon Gunnar Wold</dc:creator>
		<pubDate>Mon, 21 Dec 2009 10:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-20</guid>
		<description>ALIGN, not aling of course. Shame on me</description>
		<content:encoded><![CDATA[<p>ALIGN, not aling of course. Shame on me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Gunnar Wold</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-19</link>
		<dc:creator>Jon Gunnar Wold</dc:creator>
		<pubDate>Mon, 21 Dec 2009 10:14:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-19</guid>
		<description>I don&#039;t agree. When I look at that list of numbers, I actually have to read them to see which number is greater. Looking at 324,768 I will not read the number, just compare it&#039;s physical size to 23,745 and 100. In your example, 24K looks smaller than 9.3K. You should also decimal-aling the numbers to facilitate scanning and comparison. &quot;9.3K&quot; is user-hostile tech-speak, shame on you.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree. When I look at that list of numbers, I actually have to read them to see which number is greater. Looking at 324,768 I will not read the number, just compare it&#8217;s physical size to 23,745 and 100. In your example, 24K looks smaller than 9.3K. You should also decimal-aling the numbers to facilitate scanning and comparison. &#8220;9.3K&#8221; is user-hostile tech-speak, shame on you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morris</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-9</link>
		<dc:creator>Morris</dc:creator>
		<pubDate>Sun, 06 Dec 2009 15:59:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-9</guid>
		<description>:D, I have to say this whole site and idea is really good, beautiful design. I haven&#039;t really seen anyone out their try and simplify search in terms of deployment and UI like the way you guys have. I&#039;m definitely betting you guys to be leaders within this space :)</description>
		<content:encoded><![CDATA[<p>:D, I have to say this whole site and idea is really good, beautiful design. I haven&#8217;t really seen anyone out their try and simplify search in terms of deployment and UI like the way you guys have. I&#8217;m definitely betting you guys to be leaders within this space :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stefan</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-8</link>
		<dc:creator>stefan</dc:creator>
		<pubDate>Sun, 06 Dec 2009 10:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-8</guid>
		<description>Good idea Morris, I think shading could help - we&#039;re also experimenting with turning the capsule around the count into a bar chart of sorts (where the capsules have proportional width according to frequencies).</description>
		<content:encoded><![CDATA[<p>Good idea Morris, I think shading could help &#8211; we&#8217;re also experimenting with turning the capsule around the count into a bar chart of sorts (where the capsules have proportional width according to frequencies).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Morris</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-7</link>
		<dc:creator>Morris</dc:creator>
		<pubDate>Sat, 05 Dec 2009 22:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-7</guid>
		<description>Nice blog, perhaps the unit could be styled with different shade/color as it stills takes time to digest.</description>
		<content:encoded><![CDATA[<p>Nice blog, perhaps the unit could be styled with different shade/color as it stills takes time to digest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Shaw</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-5</link>
		<dc:creator>Andy Shaw</dc:creator>
		<pubDate>Sat, 05 Dec 2009 14:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-5</guid>
		<description>Well said Tyler, will use this method in the future for large numbers. Maybe could add the actual result number as a title tag over the number too.</description>
		<content:encoded><![CDATA[<p>Well said Tyler, will use this method in the future for large numbers. Maybe could add the actual result number as a title tag over the number too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-4</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Sat, 05 Dec 2009 12:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-4</guid>
		<description>I love your site</description>
		<content:encoded><![CDATA[<p>I love your site</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cennydd</title>
		<link>http://blog.twigkit.com/precise-to-a-fault/comment-page-1/#comment-3</link>
		<dc:creator>Cennydd</dc:creator>
		<pubDate>Sat, 05 Dec 2009 12:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twigkit.com/?p=6#comment-3</guid>
		<description>Agreed. I did a bit of usability consultancy for the recent JustGiving redesign (http://www.justgiving.com). One thing that I thought was quite important was the precision of the numbers at the top: &quot;Over 8 million of you have helped raise £550m for 8,382 charities.&quot; Classic social proof, but the original wireframes had these numbers in full. We put forward the idea of rounding them to aid quick comprehension &amp; recall, and to save some layout space. I think the results work well, although of course I&#039;d need to usability test it to know for sure.</description>
		<content:encoded><![CDATA[<p>Agreed. I did a bit of usability consultancy for the recent JustGiving redesign (<a href="http://www.justgiving.com" rel="nofollow">http://www.justgiving.com</a>). One thing that I thought was quite important was the precision of the numbers at the top: &#8220;Over 8 million of you have helped raise £550m for 8,382 charities.&#8221; Classic social proof, but the original wireframes had these numbers in full. We put forward the idea of rounding them to aid quick comprehension &amp; recall, and to save some layout space. I think the results work well, although of course I&#8217;d need to usability test it to know for sure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
