<?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: Note from the Editor: Our voting buttons&#8230;</title>
	<atom:link href="http://uitrends.com/2009/08/27/note-from-the-editor-our-voting-buttons/feed/" rel="self" type="application/rss+xml" />
	<link>http://uitrends.com/2009/08/27/note-from-the-editor-our-voting-buttons/</link>
	<description>A place to catalog, discuss, and rate trends in user interface design</description>
	<lastBuildDate>Sat, 28 Aug 2010 15:46:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: John</title>
		<link>http://uitrends.com/2009/08/27/note-from-the-editor-our-voting-buttons/comment-page-1/#comment-32</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 27 Aug 2009 19:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://uitrends.com/?p=393#comment-32</guid>
		<description>It all depends on what your going for.  My initial assumption was to vote based on if i like the trend in general.  However, it could be a legitimate trend without me liking it (probably the case actually). So in that case I could vote it up to agree that it IS indeed a trend.  Or take the opposite approach and vote it down to say i dislike the trend.

My suggestion thus would be to break the voting into subsections.  Although more complex and more confusing to your users, it will be more useful.  Also we can assume some level of sophistication among users with regards to UI as this is a UI trends page in the first place :)

Trendiness - is, or is this not a emerging trend.
Likability - is this a UI feature we like.
Good-spot - poster has a good eye and found something interesting

Those would be my initial three subcategories (but clearly not a verbose list).

From the implementation side i would weight each of them so that they combined into a overall rating (seeing stars anyone?)  with Trendiness being the highest weighted and likability the next.  

This would provide a overall rating that can be display (and searched) for each trend.

I would also consider thinking about discussing usability.  It kind of fall into the likabilty category (as i would assume people don&#039;t like what isn&#039;t usable) but may want to break it out into its own thing.



Just a thought.  don&#039;t shoot me.</description>
		<content:encoded><![CDATA[<p>It all depends on what your going for.  My initial assumption was to vote based on if i like the trend in general.  However, it could be a legitimate trend without me liking it (probably the case actually). So in that case I could vote it up to agree that it IS indeed a trend.  Or take the opposite approach and vote it down to say i dislike the trend.</p>
<p>My suggestion thus would be to break the voting into subsections.  Although more complex and more confusing to your users, it will be more useful.  Also we can assume some level of sophistication among users with regards to UI as this is a UI trends page in the first place :)</p>
<p>Trendiness &#8211; is, or is this not a emerging trend.<br />
Likability &#8211; is this a UI feature we like.<br />
Good-spot &#8211; poster has a good eye and found something interesting</p>
<p>Those would be my initial three subcategories (but clearly not a verbose list).</p>
<p>From the implementation side i would weight each of them so that they combined into a overall rating (seeing stars anyone?)  with Trendiness being the highest weighted and likability the next.  </p>
<p>This would provide a overall rating that can be display (and searched) for each trend.</p>
<p>I would also consider thinking about discussing usability.  It kind of fall into the likabilty category (as i would assume people don&#8217;t like what isn&#8217;t usable) but may want to break it out into its own thing.</p>
<p>Just a thought.  don&#8217;t shoot me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Norman</title>
		<link>http://uitrends.com/2009/08/27/note-from-the-editor-our-voting-buttons/comment-page-1/#comment-31</link>
		<dc:creator>Ron Norman</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://uitrends.com/?p=393#comment-31</guid>
		<description>I think we need a UI trend for &quot;thumbs up/down&quot; buttons :)</description>
		<content:encoded><![CDATA[<p>I think we need a UI trend for &#8220;thumbs up/down&#8221; buttons :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
