<?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"
	>
<channel>
	<title>Comments on: Rapid prototyping makes usability testing easier</title>
	<atom:link href="http://www.peterkrantz.com/2006/agile-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterkrantz.com/2006/agile-rails/</link>
	<description>A blog about technology, visualization, music and unmanned vehicle experiments</description>
	<pubDate>Sun, 06 Jul 2008 06:14:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Rapid prototyping makes usability testing easier - Peter Krantz</title>
		<link>http://www.peterkrantz.com/2006/agile-rails/#comment-96</link>
		<dc:creator>Rapid prototyping makes usability testing easier - Peter Krantz</dc:creator>
		<pubDate>Wed, 26 Jul 2006 22:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkrantz.com/2006/agile-rails/#comment-96</guid>
		<description>[...] Do web frameworks like Ruby on Rails really obsolete wireframe usability testing? Peter Krantz:  The only real reason to test a mockup instead of a real application is of course that it used to be more expensive and time consuming to create an application. With Rails there is no such barrier anymore and usability tests can (and should) be using the real application instead. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Do web frameworks like Ruby on Rails really obsolete wireframe usability testing? Peter Krantz:  The only real reason to test a mockup instead of a real application is of course that it used to be more expensive and time consuming to create an application. With Rails there is no such barrier anymore and usability tests can (and should) be using the real application instead. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
