<?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: Top 7 Tools for Interaction Design and IA</title>
	<atom:link href="http://stealthisidea.com/articles/design-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://stealthisidea.com/articles/design-tools/</link>
	<description>Philip Haine&#039;s articles on Product Vision, Innovation and Design</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Philip Haine</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-3201</link>
		<dc:creator>Philip Haine</dc:creator>
		<pubDate>Wed, 03 Mar 2010 19:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-3201</guid>
		<description>Hi, Troy --

Sorry for the delay in responding.

Thanks for the pointer to Catalyst --  I will check it out.

I&#039;m definitely in favor of prototyping tools, but there will always be some behavior that the designer cannot prototype.  This must be conveyed to developers verbally one way or another.

Best regards,
Philip</description>
		<content:encoded><![CDATA[<p>Hi, Troy &#8211;</p>
<p>Sorry for the delay in responding.</p>
<p>Thanks for the pointer to Catalyst &#8212;  I will check it out.</p>
<p>I&#8217;m definitely in favor of prototyping tools, but there will always be some behavior that the designer cannot prototype.  This must be conveyed to developers verbally one way or another.</p>
<p>Best regards,<br />
Philip</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-3181</link>
		<dc:creator>Troy</dc:creator>
		<pubDate>Fri, 15 Jan 2010 00:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-3181</guid>
		<description>Hi Phillip,
Thanks for your work here. Questions, you mention Google Pages for your tool for documenting designs. Why does this all need to be documented in text? What about using something like Adobe&#039;s Flash Catalyst so that designers can convey exactly what they expect to the Web developer? 

I know this is an older write-up, but Catalyst was in beta at the time I believe. 

Thanks,
Troy</description>
		<content:encoded><![CDATA[<p>Hi Phillip,<br />
Thanks for your work here. Questions, you mention Google Pages for your tool for documenting designs. Why does this all need to be documented in text? What about using something like Adobe&#8217;s Flash Catalyst so that designers can convey exactly what they expect to the Web developer? </p>
<p>I know this is an older write-up, but Catalyst was in beta at the time I believe. </p>
<p>Thanks,<br />
Troy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Requirements docs: Goodbye word processor, hello wiki &#124; The Product Vision blog</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-2548</link>
		<dc:creator>Requirements docs: Goodbye word processor, hello wiki &#124; The Product Vision blog</dc:creator>
		<pubDate>Mon, 22 Jun 2009 19:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-2548</guid>
		<description>[...] couple of years ago, I underwent the most significant change in my toolset in years. I switched from word processors for such documentation to wiki&#8217;s.This had a number [...]</description>
		<content:encoded><![CDATA[<p>[...] couple of years ago, I underwent the most significant change in my toolset in years. I switched from word processors for such documentation to wiki&#8217;s.This had a number [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Haine</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-2400</link>
		<dc:creator>Philip Haine</dc:creator>
		<pubDate>Mon, 12 Jan 2009 04:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-2400</guid>
		<description>Dave, yes, today&#039;s MacBooks could very well be better than yesterday&#039;s MacBook Pros.  I happen to be using both Firewire ports, 3GB RAM and I plug into a 30&quot; display requiring dual link DVI.  I&#039;m not sure the regular MacBooks have those.

I had been using Adobe CS2, so the jump to CS4 was huge, because it&#039;s now Intel native.  (I don&#039;t feel like the kid with worn out shoes anymore.)  I cannot speak to the delta from CS3, except to say that the consensus reviews out there say it&#039;s worthwhile.</description>
		<content:encoded><![CDATA[<p>Dave, yes, today&#8217;s MacBooks could very well be better than yesterday&#8217;s MacBook Pros.  I happen to be using both Firewire ports, 3GB RAM and I plug into a 30&#8243; display requiring dual link DVI.  I&#8217;m not sure the regular MacBooks have those.</p>
<p>I had been using Adobe CS2, so the jump to CS4 was huge, because it&#8217;s now Intel native.  (I don&#8217;t feel like the kid with worn out shoes anymore.)  I cannot speak to the delta from CS3, except to say that the consensus reviews out there say it&#8217;s worthwhile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Cortright</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-2398</link>
		<dc:creator>Dave Cortright</dc:creator>
		<pubDate>Mon, 12 Jan 2009 01:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-2398</guid>
		<description>I still believe the MacBook is a much better value than the MacBook Pro. Unless you need the extra screen real estate on your laptop monitor, save your money. I personally run a second monitor off of my MacBook for my heavy design work, and the laptop screen is sufficient itself for basic email and web tasks (and even the occasional design tweak here or there.)
http://www.rated-best.org/blog/2008/06/best-laptop-apple-macbook.html

I used to be a Visio guy on Windows, but I&#039;m an OmniGraffle fan on the Mac. I use it for flow charts, mind maps, and UI designs. I have the pro version and use the Outlining and Mouseless Editing groups under the Edit menu for quickly creating connected boxes. You can then context-click one, select similar, and format them all how you wish. Omni Graffle has a lot of depth. and while there are annoyances, there are fewer than I remember in Visio.

Perhaps not technically a tool, but the &quot;Print to PDF&quot; function built into the Mac is critical to sharing my designs with stakeholders. On the PC, I highly recommend PDF Creator for similar functionality.
http://sourceforge.net/projects/pdfcreator/

Could you elaborate on why CS4 is so much better than 2 or 3? I see no compelling reason to spend the hundreds of dollars on an upgrade to software I use rarely, and even then only for the core basics. If you are an interaction designer spending substantial time in Photoshop or Illustrator, you are not spending your time well. IMHO :-)

I like Stickies even better than TextEdit for basic note-taking. You don&#039;t have to hit save. You can then copy/paste your notes into a more permanent place later, like Evernote.

Great post, though, Phil! Thanks for the conversation starter. It&#039;s a topic that needed discussion.</description>
		<content:encoded><![CDATA[<p>I still believe the MacBook is a much better value than the MacBook Pro. Unless you need the extra screen real estate on your laptop monitor, save your money. I personally run a second monitor off of my MacBook for my heavy design work, and the laptop screen is sufficient itself for basic email and web tasks (and even the occasional design tweak here or there.)<br />
<a href="http://www.rated-best.org/blog/2008/06/best-laptop-apple-macbook.html" rel="nofollow">http://www.rated-best.org/blog/2008/06/best-laptop-apple-macbook.html</a></p>
<p>I used to be a Visio guy on Windows, but I&#8217;m an OmniGraffle fan on the Mac. I use it for flow charts, mind maps, and UI designs. I have the pro version and use the Outlining and Mouseless Editing groups under the Edit menu for quickly creating connected boxes. You can then context-click one, select similar, and format them all how you wish. Omni Graffle has a lot of depth. and while there are annoyances, there are fewer than I remember in Visio.</p>
<p>Perhaps not technically a tool, but the &#8220;Print to PDF&#8221; function built into the Mac is critical to sharing my designs with stakeholders. On the PC, I highly recommend PDF Creator for similar functionality.<br />
<a href="http://sourceforge.net/projects/pdfcreator/" rel="nofollow">http://sourceforge.net/projects/pdfcreator/</a></p>
<p>Could you elaborate on why CS4 is so much better than 2 or 3? I see no compelling reason to spend the hundreds of dollars on an upgrade to software I use rarely, and even then only for the core basics. If you are an interaction designer spending substantial time in Photoshop or Illustrator, you are not spending your time well. IMHO <img src='http://stealthisidea.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>I like Stickies even better than TextEdit for basic note-taking. You don&#8217;t have to hit save. You can then copy/paste your notes into a more permanent place later, like Evernote.</p>
<p>Great post, though, Phil! Thanks for the conversation starter. It&#8217;s a topic that needed discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Haine</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-2383</link>
		<dc:creator>Philip Haine</dc:creator>
		<pubDate>Sat, 03 Jan 2009 18:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-2383</guid>
		<description>Thanks, Peldi!

I sent you my notes on an earlier version of Balsamiq Mockups.  I will try looking at v1.5 when I can.

Philip</description>
		<content:encoded><![CDATA[<p>Thanks, Peldi!</p>
<p>I sent you my notes on an earlier version of Balsamiq Mockups.  I will try looking at v1.5 when I can.</p>
<p>Philip</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peldi Guilizzoni</title>
		<link>http://stealthisidea.com/articles/design-tools/comment-page-1/#comment-2381</link>
		<dc:creator>Peldi Guilizzoni</dc:creator>
		<pubDate>Fri, 02 Jan 2009 08:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=478#comment-2381</guid>
		<description>Hello Philip, thanks for the great article, I didn&#039;t know about Stone Create and it looks really good. 

I am interested in hearing why you think Balsamiq Mockups is &quot;immature&quot;. I agree that it&#039;s not &quot;done&quot;, but I am pretty happy with version 1.5 which I released a couple of weeks ago: http://www.balsamiq.com/products/mockups

I am always working to improve the tool and feedback from experts like yourself is just what I need: if you have the time, write me at peldi@balsamiq.com, I&#039;d appreciate it.

Thanks again for the great article,
Peldi</description>
		<content:encoded><![CDATA[<p>Hello Philip, thanks for the great article, I didn&#8217;t know about Stone Create and it looks really good. </p>
<p>I am interested in hearing why you think Balsamiq Mockups is &#8220;immature&#8221;. I agree that it&#8217;s not &#8220;done&#8221;, but I am pretty happy with version 1.5 which I released a couple of weeks ago: <a href="http://www.balsamiq.com/products/mockups" rel="nofollow">http://www.balsamiq.com/products/mockups</a></p>
<p>I am always working to improve the tool and feedback from experts like yourself is just what I need: if you have the time, write me at <a href="mailto:peldi@balsamiq.com">peldi@balsamiq.com</a>, I&#8217;d appreciate it.</p>
<p>Thanks again for the great article,<br />
Peldi</p>
]]></content:encoded>
	</item>
</channel>
</rss>

