<?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: Book Review: Designing Web Interfaces</title>
	<atom:link href="http://johnnyholland.org/2009/05/book-review-designing-web-interfaces/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org/2009/05/book-review-designing-web-interfaces/</link>
	<description>It&#039;s all about interaction</description>
	<lastBuildDate>Wed, 05 Jun 2013 06:03:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Theresa</title>
		<link>http://johnnyholland.org/2009/05/book-review-designing-web-interfaces/#comment-107298</link>
		<dc:creator>Theresa</dc:creator>
		<pubDate>Sun, 17 May 2009 20:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=2019#comment-107298</guid>
		<description>I actually refer to our book a couple of times a week to look at examples of how different web applications have approached a particular interaction. I don&#039;t use it to &quot;win arguments&quot; with my clients or other designers I collaborate with, but as a catalog of decent examples for reference.

I don&#039;t think many developers, product managers, marketing folks, and QA people have reference books for current interaction design concepts (this is just my observation). For me personally, the book helps organize the interactions into patterns with recent examples, so we can use  common terminology and live examples in our design sessions.

Explore the book and all of the illustrations at www.designingwebinterfaces.com and we are posting fresh content and examples at www.designingwebinterfaces.com/posts .</description>
		<content:encoded><![CDATA[<p>I actually refer to our book a couple of times a week to look at examples of how different web applications have approached a particular interaction. I don&#8217;t use it to &#8220;win arguments&#8221; with my clients or other designers I collaborate with, but as a catalog of decent examples for reference.</p>
<p>I don&#8217;t think many developers, product managers, marketing folks, and QA people have reference books for current interaction design concepts (this is just my observation). For me personally, the book helps organize the interactions into patterns with recent examples, so we can use  common terminology and live examples in our design sessions.</p>
<p>Explore the book and all of the illustrations at <a href="http://www.designingwebinterfaces.com" rel="nofollow">http://www.designingwebinterfaces.com</a> and we are posting fresh content and examples at <a href="http://www.designingwebinterfaces.com/posts" rel="nofollow">http://www.designingwebinterfaces.com/posts</a> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vicky Teinaki</title>
		<link>http://johnnyholland.org/2009/05/book-review-designing-web-interfaces/#comment-107297</link>
		<dc:creator>Vicky Teinaki</dc:creator>
		<pubDate>Thu, 07 May 2009 15:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=2019#comment-107297</guid>
		<description>Common sense is a funny thing, particularly when it comes to interactions. For example, after NYTimes tech columnist David Pogue wrote a post about &#039;Tech Tips for the Basic User&#039; and was flooded with tips, he wrote: &quot;Many readers chimed in with other “basics” that they assumed every computer user knew–but soon discovered that what’s common knowledge isn’t the same as universal knowledge.&quot;
(Link: http://pogue.blogs.nytimes.com/2008/10/02/tech-tips-for-the-basic-computer-user/)
That&#039;s relevant in the IxD profession, as in my opinion we still don&#039;t have that much literature of the basics. So yes, it&#039;s common sense, but it has to be explicitly made common through books and the like. Then we can agree about it and move on.
That said, I do agree with the comment about these books being good argument tools!</description>
		<content:encoded><![CDATA[<p>Common sense is a funny thing, particularly when it comes to interactions. For example, after NYTimes tech columnist David Pogue wrote a post about &#8216;Tech Tips for the Basic User&#8217; and was flooded with tips, he wrote: &#8220;Many readers chimed in with other “basics” that they assumed every computer user knew–but soon discovered that what’s common knowledge isn’t the same as universal knowledge.&#8221;<br />
(Link: <a href="http://pogue.blogs.nytimes.com/2008/10/02/tech-tips-for-the-basic-computer-user/" rel="nofollow">http://pogue.blogs.nytimes.com/2008/10/02/tech-tips-for-the-basic-computer-user/</a>)<br />
That&#8217;s relevant in the IxD profession, as in my opinion we still don&#8217;t have that much literature of the basics. So yes, it&#8217;s common sense, but it has to be explicitly made common through books and the like. Then we can agree about it and move on.<br />
That said, I do agree with the comment about these books being good argument tools!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peterpixel</title>
		<link>http://johnnyholland.org/2009/05/book-review-designing-web-interfaces/#comment-107296</link>
		<dc:creator>peterpixel</dc:creator>
		<pubDate>Mon, 04 May 2009 14:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=2019#comment-107296</guid>
		<description>Being Devils advocate here, but isn&#039;t a lot of these patterns common sense to most interaction designers? And what advantage does this book have over pattern libraries currently out there?

I am inclined to think this book (and perhaps many other Interaction Design books similar to this one) are more suited as tools to &quot;win arguments&quot;, in other words: illustrate to whoever is in charge, but is not an interaction designer, that what you are suggesting is actually a good idea.</description>
		<content:encoded><![CDATA[<p>Being Devils advocate here, but isn&#8217;t a lot of these patterns common sense to most interaction designers? And what advantage does this book have over pattern libraries currently out there?</p>
<p>I am inclined to think this book (and perhaps many other Interaction Design books similar to this one) are more suited as tools to &#8220;win arguments&#8221;, in other words: illustrate to whoever is in charge, but is not an interaction designer, that what you are suggesting is actually a good idea.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
