<?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: Paired HTML Prototyping</title>
	<atom:link href="http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/</link>
	<description></description>
	<lastBuildDate>Sat, 06 Oct 2012 20:03:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Bryan Kearney</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-867</link>
		<dc:creator>Bryan Kearney</dc:creator>
		<pubDate>Sat, 09 Jul 2011 01:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-867</guid>
		<description><![CDATA[Couldn&#039;t agree with you more! Glad your on the HTML prototyping train. One often overlooked but great benefit from using HTML in prototyping is that it will &quot;push back&quot;, keeping someone from making unrealistic choices. Can&#039;t wait to see what you guys have up your sleeve, HTML prototype + Unify maybe?]]></description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree with you more! Glad your on the HTML prototyping train. One often overlooked but great benefit from using HTML in prototyping is that it will &#8220;push back&#8221;, keeping someone from making unrealistic choices. Can&#8217;t wait to see what you guys have up your sleeve, HTML prototype + Unify maybe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Curtis</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-863</link>
		<dc:creator>Nathan Curtis</dc:creator>
		<pubDate>Wed, 29 Jun 2011 12:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-863</guid>
		<description><![CDATA[EightShapes uses many tools to prototype user experiences: sketches/paper, PDF wireframes (linked together), iRise (not so often and not preferred in our work), Axure, Flash Catalyst, and recently predominantly directly in HTML. We&#039;re finding that working directly in the medium of the final product is giving us a direct connection to the development process, validating (and exploring) the design solution earlier and often and with more conscientiousness, and is being received far more warmly and engagingly by our clients. 

We&#039;ve found that other prototyping tools that simulate the experience (iRise, Axure, and Flash Catalyst) but aren&#039;t REALLY HTML distance us from reality, end up being tedious to maintain (push that pixel!), and tend to &quot;break the wall&quot; in people&#039;s perception of a real, in browser experience. That&#039;s not to say those tools aren&#039;t valuable - they are, and we will use them if the fit of project needs, designer skill, and software capability mix well. But most of us are on the HTML prototyping train at this point.]]></description>
		<content:encoded><![CDATA[<p>EightShapes uses many tools to prototype user experiences: sketches/paper, PDF wireframes (linked together), iRise (not so often and not preferred in our work), Axure, Flash Catalyst, and recently predominantly directly in HTML. We&#8217;re finding that working directly in the medium of the final product is giving us a direct connection to the development process, validating (and exploring) the design solution earlier and often and with more conscientiousness, and is being received far more warmly and engagingly by our clients. </p>
<p>We&#8217;ve found that other prototyping tools that simulate the experience (iRise, Axure, and Flash Catalyst) but aren&#8217;t REALLY HTML distance us from reality, end up being tedious to maintain (push that pixel!), and tend to &#8220;break the wall&#8221; in people&#8217;s perception of a real, in browser experience. That&#8217;s not to say those tools aren&#8217;t valuable &#8211; they are, and we will use them if the fit of project needs, designer skill, and software capability mix well. But most of us are on the HTML prototyping train at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-861</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 28 Jun 2011 22:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-861</guid>
		<description><![CDATA[Curious about the choice of using HTML over other prototyping software like Axure or Balsamiq?]]></description>
		<content:encoded><![CDATA[<p>Curious about the choice of using HTML over other prototyping software like Axure or Balsamiq?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan Strandell</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-844</link>
		<dc:creator>Johan Strandell</dc:creator>
		<pubDate>Thu, 09 Jun 2011 15:12:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-844</guid>
		<description><![CDATA[Any chance of getting a peek at the prototype? Even just static images would be nice.]]></description>
		<content:encoded><![CDATA[<p>Any chance of getting a peek at the prototype? Even just static images would be nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Britton</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-842</link>
		<dc:creator>Mike Britton</dc:creator>
		<pubDate>Wed, 08 Jun 2011 23:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-842</guid>
		<description><![CDATA[Congrats on a rewarding collaborative session.  This prepares you for so much more than presenting to the client.  The benefits will manifest as the prototype gets signoff in the areas you defined.]]></description>
		<content:encoded><![CDATA[<p>Congrats on a rewarding collaborative session.  This prepares you for so much more than presenting to the client.  The benefits will manifest as the prototype gets signoff in the areas you defined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Eberman</title>
		<link>http://www.eightshapes.com/blog/2011/06/08/paired-html-prototyping/comment-page-1/#comment-840</link>
		<dc:creator>Mark Eberman</dc:creator>
		<pubDate>Wed, 08 Jun 2011 18:27:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.eightshapes.com/?p=1702#comment-840</guid>
		<description><![CDATA[&quot;...started the morning with nothing...&quot;

and then 

&quot;...prepped beforehand by identifying page layouts and obtaining real content (copy, links, visualizations, and more)...&quot;

and finally 

&quot;...started from a library of existing CSS and what amounted to header and a somewhat obese footer to include...&quot;

I think the idea is interesting and the exercise informative, but honestly I&#039;d like to hope that you&#039;d be able to build a 10 page prototype in 8 man hours with a head start like that. 

I would think that the real fruits of a collaboration like this would be what you note in the penultimate paragraph--and I think what sparks that nice exchange of techniques and brainstorming is that because you&#039;re working on the same project you have the same points of reference and vocabulary. It&#039;s crucial to have that shared frame of reference, and this is a very cool way to get that.]]></description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;started the morning with nothing&#8230;&#8221;</p>
<p>and then </p>
<p>&#8220;&#8230;prepped beforehand by identifying page layouts and obtaining real content (copy, links, visualizations, and more)&#8230;&#8221;</p>
<p>and finally </p>
<p>&#8220;&#8230;started from a library of existing CSS and what amounted to header and a somewhat obese footer to include&#8230;&#8221;</p>
<p>I think the idea is interesting and the exercise informative, but honestly I&#8217;d like to hope that you&#8217;d be able to build a 10 page prototype in 8 man hours with a head start like that. </p>
<p>I would think that the real fruits of a collaboration like this would be what you note in the penultimate paragraph&#8211;and I think what sparks that nice exchange of techniques and brainstorming is that because you&#8217;re working on the same project you have the same points of reference and vocabulary. It&#8217;s crucial to have that shared frame of reference, and this is a very cool way to get that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.271 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-24 07:30:09 -->
