<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Userability #8 &#8211; The Case of Multiple Link Types</title>
	<atom:link href="http://www.uie.com/brainsparks/2009/05/29/userability-8-the-case-of-multiple-link-types/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2009/05/29/userability-8-the-case-of-multiple-link-types/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Thu, 23 May 2013 10:02:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: kenny kutney</title>
		<link>http://www.uie.com/brainsparks/2009/05/29/userability-8-the-case-of-multiple-link-types/comment-page-1/#comment-146738</link>
		<dc:creator>kenny kutney</dc:creator>
		<pubDate>Thu, 04 Jun 2009 02:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=825#comment-146738</guid>
		<description>What&#039;s worked well for me (on a couple of projects) has been differentiating commands not so much by content or interaction method, but by importance/relevance of the action. Typically, that&#039;s meant using buttons for the primary action(s), and links for the secondary stuff. For example, on a multi-page sign-up, buttons are used for the main navigational elements (like &quot;Next&quot; or &quot;Buy it Now&quot;) and links for the commands that aren&#039;t as important or are less likely to be used (like &quot;Cancel&quot; or &quot;Change settings&quot;). 

Love the podcasts - keep them coming!

- kenny</description>
		<content:encoded><![CDATA[<p>What&#8217;s worked well for me (on a couple of projects) has been differentiating commands not so much by content or interaction method, but by importance/relevance of the action. Typically, that&#8217;s meant using buttons for the primary action(s), and links for the secondary stuff. For example, on a multi-page sign-up, buttons are used for the main navigational elements (like &#8220;Next&#8221; or &#8220;Buy it Now&#8221;) and links for the commands that aren&#8217;t as important or are less likely to be used (like &#8220;Cancel&#8221; or &#8220;Change settings&#8221;). </p>
<p>Love the podcasts &#8211; keep them coming!</p>
<p>- kenny</p>
]]></content:encoded>
	</item>
</channel>
</rss>
