<?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: Why Traditional Usability Sucks</title>
	<atom:link href="http://frontendbook.com/why-traditional-usability-sucks/feed" rel="self" type="application/rss+xml" />
	<link>http://frontendbook.com/why-traditional-usability-sucks</link>
	<description>UX, Mobile, Web and Product Development</description>
	<lastBuildDate>Sat, 17 Dec 2011 10:07:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jond Fond</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-244</link>
		<dc:creator>Jond Fond</dc:creator>
		<pubDate>Mon, 14 Jul 2008 17:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-244</guid>
		<description>I believe that opening up your web is very important in order to get people to enable new products on top of your content.</description>
		<content:encoded><![CDATA[<p>I believe that opening up your web is very important in order to get people to enable new products on top of your content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Ferraiuolo</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-239</link>
		<dc:creator>Eric Ferraiuolo</dc:creator>
		<pubDate>Fri, 18 Apr 2008 19:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-239</guid>
		<description>There are some school&#039;s of thought that say to not listen to your users. That it&#039;s better to take a research/observatory approach to usability; using your knowledge and expertise in a field to develop something that would be useful to some audience.</description>
		<content:encoded><![CDATA[<p>There are some school&#8217;s of thought that say to not listen to your users. That it&#8217;s better to take a research/observatory approach to usability; using your knowledge and expertise in a field to develop something that would be useful to some audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Watts</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-243</link>
		<dc:creator>Brandon Watts</dc:creator>
		<pubDate>Wed, 16 Apr 2008 20:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-243</guid>
		<description>Thanks, Mattias! Let me know if you&#039;d like to talk more about what we do.

Brandon Watts
Daylife Evangelist</description>
		<content:encoded><![CDATA[<p>Thanks, Mattias! Let me know if you&#8217;d like to talk more about what we do.</p>
<p>Brandon Watts<br />
Daylife Evangelist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mattias Hising</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-242</link>
		<dc:creator>Mattias Hising</dc:creator>
		<pubDate>Tue, 15 Apr 2008 14:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-242</guid>
		<description>@Brandon: Interesting product. I will look into your API and as I write in the post, I believe that opening up your web is very important in order to get people to enable new products on top of your content.</description>
		<content:encoded><![CDATA[<p>@Brandon: Interesting product. I will look into your API and as I write in the post, I believe that opening up your web is very important in order to get people to enable new products on top of your content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Watts</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-240</link>
		<dc:creator>Brandon Watts</dc:creator>
		<pubDate>Tue, 15 Apr 2008 14:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-240</guid>
		<description>Mattias,

As you alluded to, what better way is there to enhance usability than to give people complete access to what you do through an API? This truly enables your users to use what you provide in the way that they want versus the way that you think they want it. Daylife is built around our API, and many other online companies are supporting open development as well.

Brandon Watts
Daylife Evangelist</description>
		<content:encoded><![CDATA[<p>Mattias,</p>
<p>As you alluded to, what better way is there to enhance usability than to give people complete access to what you do through an API? This truly enables your users to use what you provide in the way that they want versus the way that you think they want it. Daylife is built around our API, and many other online companies are supporting open development as well.</p>
<p>Brandon Watts<br />
Daylife Evangelist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: This Stuff Sucks &#124; The Best of What Sucks</title>
		<link>http://frontendbook.com/why-traditional-usability-sucks#comment-241</link>
		<dc:creator>This Stuff Sucks &#124; The Best of What Sucks</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=126#comment-241</guid>
		<description>&lt;!--%kramer-pre%--&gt;Add new comment Feed: This Stuff SucksOriginal article&lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<p><!--%kramer-pre%-->Add new comment Feed: This Stuff SucksOriginal article<!--%kramer-post%--></p>
]]></content:encoded>
	</item>
</channel>
</rss>


