<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Anders Ramsay.com &#187; Add new tag</title>
	<atom:link href="http://www.andersramsay.com/tag/add-new-tag/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andersramsay.com</link>
	<description>designing user experiences</description>
	<lastBuildDate>Fri, 09 Jul 2010 18:45:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Some Thoughts About the Balsamiq Mockup Tool</title>
		<link>http://www.andersramsay.com/2008/11/06/some-thoughts-about-balsamiq</link>
		<comments>http://www.andersramsay.com/2008/11/06/some-thoughts-about-balsamiq#comments</comments>
		<pubDate>Thu, 06 Nov 2008 21:58:27 +0000</pubDate>
		<dc:creator>Anders</dc:creator>
				<category><![CDATA[Prototyping]]></category>
		<category><![CDATA[Add new tag]]></category>

		<guid isPermaLink="false">http://www.andersramsay.com/?p=216</guid>
		<description><![CDATA[There is, of course, a slight irony in that only a few days ago, I was writing about why I don&#8217;t use prototyping tools, and here I am writing a review of a prototyping tool. Well, not quite. I think Balsamiq is actually more of a sketching tool, partly because the artifacts generated from the [...]]]></description>
			<content:encoded><![CDATA[<p>There is, of course, a slight irony in that only a few days ago, I was writing about <a href="http://www.andersramsay.com/2008/10/29/three-reasons-why-i-dont-use-prototyping-tools/">why I don&#8217;t use prototyping tools</a>, and here I am writing a review of a prototyping tool.  Well, not quite.  I think <a href="http://balsamiq.com/">Balsamiq </a> is actually more of a sketching tool, partly because the artifacts generated from the tool don&#8217;t try to fool viewers that it&#8217;s a representation of the real thing.  Some prototyping tools, particularly the higher end editions, pride themselves in being able to mimic the user experience of the actual application.  Unless that simulation really truly mimics the actual user experience of the not-yet-built production version of the application, the feedback you get from users may actually be completely irrelevant.  For that reason, I really like the Balsamiq approach of being overtly sketch-like, a constant reminder that this is an idea in progress, and an invitation to tear it apart as necessary.</p>
<h3>Overall</h3>
<p>Like McCain might&#8217;ve said, &#8220;the fundamentals of Balsamiq are sound.&#8221;  No, but seriously, I think the fundamental concept of a light-weight tool with ready-made sketch-like widgets can be a very effective model for quickly roughing out and sharing ideas. Overall, I think Balsamiq is a tool with a lot of potential, and certainly a worthy competitor to <a href="http://www.gliffy.com/">Gliffy</a> (or a complement, since Gliffy seems to focus more on diagramming.) In its current form  (I was trying version 1.5), I think I&#8217;d definitely add it to my toolbox, but for reasons I list below, the times when it would make sense for me to use it would likely be narrow. </p>
<h3>Access/Setup</h3>
<p>Having to download an application like this feels a little old-skool.  Seems like it should be possible to use the tool directly within a browser (and I&#8217;m guessing that&#8217;s something we&#8217;ll see in a future version.)</p>
<h3>User Interface</h3>
<p>Somewhat ironically, one area that really could use improvement is the user interface of the tool itself.  The need to scroll horizontally to access widgets, for example, is simply not great.  Additionally, a lot of basic UI issues, such as the affordances of the widget categories (both in terms of text size and &#8220;I&#8217;m-clickable&#8221; quality) really could use some work.  The good news is that this is probably something that wouldn&#8217;t be that hard to fix.  Here is quick mockup I created with Balsamiq of one possible idea for a redesign:<br />
<div id="attachment_219" class="wp-caption alignnone" style="width: 300px">
	<a href="http://www.andersramsay.com/wp-content/uploads/2008/11/balsamiq-design.png"><img src="http://www.andersramsay.com/wp-content/uploads/2008/11/balsamiq-design-300x184.png" alt="My proposed redesign of Balsamiq" title="balsamiq-design" width="300" height="184" class="size-medium wp-image-219" /></a>
	<p class="wp-caption-text">My proposed redesign of Balsamiq  (click image for larger view)</p>
</div></p>
<p>The main change I am making here: Applying a more standard application structure.  Let&#8217;s keep the experimentation on the art board, and not force users to figure out the UI of the application itself.  Additionally, I think the look and feel of the application UI should be obviously different from user-created sketch widgets &#8211; currently, it&#8217;s all a bit of a blur.</p>
<h3>Actual Drawing/Sketching</h3>
<p>Not being able to just draw freeform is almost a show-stopper for me.  This just seems so fundamental to the idea of sketching, and becomes particularly critical for a tool like this, in which (as I discussed in my earlier post about prototyping tools) you will inevitably and possibly quite commonly need to add something for which there simply is not a good ready-made widget.</p>
<h3>Sharing/Embedding</h3>
<p>I wasn&#8217;t able to try sharing or embedding the tool, but from my experience using Gliffy with Confluence, if Balsamiq is anything like that, I think that definitely adds value to the tool.</p>
<h3>Widget Library</h3>
<p>I found the organization of widgets confusing, seeming to always be clicking between the Layout and Containers categories or whatever, hunting for the right widget. I think the ability to toggle a full-screen gallery of widgets might be the way to go.  Also, despite being at the top of the page, the widget search feature is not obvious (possibly an affordance issue due to the lack of a search button.)</p>
<h3>Paper Prototyping Template Maker?</h3>
<p>One great use for this tool would be to create paper prototyping foundations.  In other words, one would perhaps produce an application wrapper, and then print multiple copies of that to then physically draw application sketches.</p>
<h3>Feature Wishlist</h3>
<p>Some things I&#8217;d like see in Balsamiq (aside from freeform drawing) is the ability to define my own favorite widgets.  Additionally, I&#8217;d like to be able to upload widgets I&#8217;ve created in other tools and not only add them to my library, but also post them to a community library, in which I would be able to browse widgets created by others.  I also think the sketch pad background is cute, but not very practical.  Would want to be able to turn it off, or create my own sharable background, such as a browser window shell.</p>
<p>Overall, I think Peldi and the Balsamiq team have done great work.  Keep it up!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andersramsay.com/2008/11/06/some-thoughts-about-balsamiq/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
