<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by don bruns</title>
    <link>http://www.boxesandarrows.com/person/116387</link>
    <pubDate>Sat, 09 Jan 2010 21:29:52 GMT</pubDate>
    <description>Comments by don bruns</description>
    <item>
      <description>&lt;p&gt;Great article!&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;m also very pleased to see that prototyping is coming into the mainstream.  As a former developer who made the transition to IA several years ago, I always tried to encourage my colleagues  to prototype as much as possible.  I got a lot of push-back because so few of my colleagues knew (or wanted to learn) &lt;span class="caps"&gt;HTML&lt;/span&gt;.&lt;/p&gt;

	&lt;p&gt;With the advent of tools like Axure and iRise, that seems to be changing. UX types are actually embracing prototyping. For simple brochure-ware websites, it&amp;#8217;s not a big deal. But when you&amp;#8217;re building actual web applications, the prototyping stage is crucial.&lt;/p&gt;

	&lt;p&gt;Unlike wireframing, prototyping forces (and better enables) the entire team to think through all the precise interactions of every page and every control on that page.  When you&amp;#8217;re designing a very complex &lt;span class="caps"&gt;GUI&lt;/span&gt; design, with very robust logic, it&amp;#8217;s very easy to miss all the possible logic landmines that a user may step on if you&amp;#8217;re only sketching out pictures.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/integrating#content_49842</link>
      <guid>http://www.boxesandarrows.com/view/integrating#content_49842</guid>
      <pubDate>Sat, 09 Jan 2010 21:29:52 GMT</pubDate>
      <author>don bruns</author>
    </item>
  </channel>
</rss>

