<?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 David Malouf</title>
    <link>http://www.boxesandarrows.com/person/1189</link>
    <pubDate>Fri, 07 Jan 2011 19:39:42 GMT</pubDate>
    <description>Comments by David Malouf</description>
    <item>
      <description>&lt;p&gt;Christina, I think this is one of the best and most useful articles I have seen on B&amp;amp;A for a long time. No disrespect to the other authors, but I love the way you put this together. It is really so clear, concise and really follows the example of the point you are trying to make.&lt;/p&gt;

	&lt;p&gt;I think there is a book in there, if you are interested in going that route again. &lt;span class="caps"&gt;A UX&lt;/span&gt; Design Guidebook. I don&amp;#8217;t think anyone has outlined it quite as well as this in the past and it would be such a great resource for the UX design community, indeed.&lt;/p&gt;

	&lt;p&gt;Basically, I&amp;#8217;m hungry for more of this thinking and elaborations and collections of examples (good and bad) in each case. Maybe it would fit in a book in Rosenfeld Media size? Or could be done in a series.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/the_elements_of#content_3285</link>
      <guid>http://www.boxesandarrows.com/view/the_elements_of#content_3285</guid>
      <pubDate>Fri, 07 Jan 2011 19:39:42 GMT</pubDate>
      <author>David Malouf</author>
    </item>
    <item>
      <description>&lt;p&gt;Other tool offerings that do &amp;#8220;prototyping&amp;#8221; (Where in the world did the term &amp;#8220;simulators&amp;#8221; come from for UX designers?&lt;/p&gt;

	&lt;p&gt;Adobe Flash/Flex: You can create data sets in &lt;span class="caps"&gt;XML&lt;/span&gt;, and generate real elaborate interactions.&lt;/p&gt;

	&lt;p&gt;(upcoming)&lt;br /&gt;Microsoft Expression: Interactive Designer: Just like Flash but for &lt;span class="caps"&gt;WPF&lt;/span&gt;/E.&lt;/p&gt;

	&lt;p&gt;These simulators for the most part&amp;#8212;the ones mentioned above&amp;#8212;differ from the tools I mention here in that they are also document management systems or have some connectivity to a document.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/visio_replaceme#content_4009</link>
      <guid>http://www.boxesandarrows.com/view/visio_replaceme#content_4009</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:36 GMT</pubDate>
      <author>David Malouf</author>
    </item>
    <item>
      <description>&lt;p&gt;Oh! I agree that different contexts will require different levels of abstraction. Teleperception may be as abstracted as we get, but may lead to amazing interfaces for example.&lt;br /&gt;I&amp;#8217;m not sure about graduating to &lt;span class="caps"&gt;CLI&lt;/span&gt;. I&amp;#8217;ve tried to make Enso (Humanized.com) part of my life and just couldn&amp;#8217;t make it more useful than my current mouse-based gesturing systems that I&amp;#8217;m so used to. But I like the steering wheel example. &lt;br /&gt;Another way is the two lever steering of a tank where you direct the tracks to go forward or back and you steer by increasing or decreasing speed of the wheels on the left or right side to go in the proper direction, like using a wheel chair or rowing a boat/canoe/raft/kayak. To me that has more abstraction but also leads to more efficient and proper interaction.&lt;/p&gt;

	&lt;p&gt;But for digital systems, I do find in general so far that lowering the abstraction layer is better so long as that abstraction layer is designed well. Ergo MS Windows Mobile while capable of touch-screen interfaces is not nearly as good at it as the iPhone. It just wasn&amp;#8217;t designed well to do it.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/foundations-of#content_11669</link>
      <guid>http://www.boxesandarrows.com/view/foundations-of#content_11669</guid>
      <pubDate>Mon, 27 Aug 2007 20:01:54 GMT</pubDate>
      <author>David Malouf</author>
    </item>
    <item>
      <description>&lt;p&gt;Wow I&amp;#8217;m so flattered by the incredibly thoughtful discussion going on here based on my article. I want people to know that these types of amazing analytical responses are exactly why I write for good zines like B&amp;amp;A. It gives me a thrill to be engaged like this. I acknowledge that I do not have all the answers (I also acknowledge thanx to my editor, I had 2500 word maximum, which is an extension from the usual for B&amp;amp;A).&lt;/p&gt;

	&lt;p&gt;Great comments from &lt;span class="caps"&gt;EVERYONE&lt;/span&gt; and why people think they are disagreeing with me, I think the nuances that make IxD so compelling for me are what people are getting at. It is so hard to get specific enough (especially in an article) to fill it all in.&lt;/p&gt;

	&lt;p&gt;Using the twiter markup that Terry started, I&amp;#8217;m going to start at the bottom and jump around from there.&lt;/p&gt;

	&lt;p&gt;@Paul&lt;br /&gt;Yes, I mean the components of the interaction design itself. &amp;#8220;Goals &amp;amp; Motivations&amp;#8221; are part of the context of the problem space, but do not make up the interaction. This is similar to how I separated out the &amp;#8220;form&amp;#8221; elements that Dan Saffer discusses in his book as foundational elements of IxD. All design has Gloals &amp;amp; Motivations of the user that they must acknowledge and they are integrated into the whole.&lt;/p&gt;

	&lt;p&gt;@Matt&lt;br /&gt;Nothing to say here. I think this is a great extension and clarification of what I am thinking as well. Thanx for doing that.&lt;/p&gt;

	&lt;p&gt;@Jerry&lt;br /&gt;I love this clarification that the cultural, sub-cultural and even personal psychology will have a dramatic effect. This is why it is so key to have great models of your personas (See About Face 3.0) that try to include cultural, cognative pieces. I think there has been great work about the social vs. the individual for example between US and non-US cultures on a continuum.&lt;/p&gt;

	&lt;p&gt;@Terry&lt;br /&gt;Thanx for the &lt;span class="caps"&gt;CLI&lt;/span&gt; example. Aza Raskin is going to be speaking at IxDA Interaction 08 | Savannah in Feb 08 (interaction08.ixda.org) and while he isn&amp;#8217;t speaking directly on one of his favorite topics, &lt;span class="caps"&gt;CLI&lt;/span&gt;, he will probably love to talk to anyone who is doing work or otherwise interested in CLIs.&lt;/p&gt;

	&lt;p&gt;Now to the meet. I think I agree and disagree w/ you about the choreography issue. I see what you mean about the collaborative nature, but someone needs to be driving the vision. If all the design disciplines are equal partners I feel that leads to a muddied vision. To me all the design disciplines are working together towards a goal of creating and communicating interactions (in this space anyway). So while I&amp;#8217;m not trying to create a land grab here, I do see it that IxD stands in the conductor&amp;#8217;s podium. Sometimes a conductor&amp;#8217;s job is to make himself invisible, even make the composer invisible and let the virtuoso take center stage. This may mean let the ID or IA shine through, but to me someone has to lead this by putting the total IxD narrative in the right light. It is like a director who is able to really let an amazing Cinematographer go to town, or a production designer. I mean what would the &amp;#8220;Fifth Element&amp;#8221; be with Godier&amp;#8217;s (sp?) amazing costume design and the other production artists? I think this happens a lot with Apple&amp;#8217;s products which really make people feel that it is the visual design that is most important to their products (the total form factor), but that is totally just a gateway &amp;#8220;bluff&amp;#8221;. It is the ease of adoption through the enticement of that gorgeous interface that leads you to the real meat in their products, but that play that is being done is key to the total interaction design that is being presented. I would even say there are usability weaknesses in that strategy that lead to better user experience and interaction design overall.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/foundations-of#content_11963</link>
      <guid>http://www.boxesandarrows.com/view/foundations-of#content_11963</guid>
      <pubDate>Fri, 07 Jan 2011 19:39:42 GMT</pubDate>
      <author>David Malouf</author>
    </item>
    <item>
      <description>&lt;p&gt;Ok, so I&amp;#8217;m sitting here writing my slides for my course I&amp;#8217;m teaching for SmartExperience.org (Interaction design of rich web applications) that starts this Wed. (6 2hr. classes). (Yes, that was an obvious placement advertisement.) and it occurred to me that in Terry&amp;#8217;s comment above he was assumes that &lt;span class="caps"&gt;CLI&lt;/span&gt; is less abstract than a &lt;span class="caps"&gt;WIMP&lt;/span&gt; (or &lt;span class="caps"&gt;GUI&lt;/span&gt;) interface.&lt;/p&gt;

	&lt;p&gt;I think I have to disagree. While typing something out is definitely easier from a Fitts Law perspective so long as the number of keystrokes required is kept to a minimum, the act of describing your actions in non-direct linguistic forms is actually more abstract than the act of navigating &amp;amp; pointing-&amp;amp;-clicking. I&amp;#8217;m sure there is some give and take in here as some elements are more abstract and some are less in both interaction models, but I think the assumption that &lt;span class="caps"&gt;CLI&lt;/span&gt; is less abstract is actually a false one from my subjective off-the-cuff analysis.&lt;/p&gt;

	&lt;p&gt;Maybe Aza can chime in here? I&amp;#8217;ll poke him to the discussion.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/foundations-of#content_11966</link>
      <guid>http://www.boxesandarrows.com/view/foundations-of#content_11966</guid>
      <pubDate>Fri, 07 Jan 2011 19:39:42 GMT</pubDate>
      <author>David Malouf</author>
    </item>
    <item>
      <description>&lt;p&gt;Hi Whitney,&lt;br /&gt;I think one thing happening in our community might be differently stated than &amp;#8220;growing&amp;#8221; is that the community is becoming more inclusive of other spheres of interaction design than where we started. Our beginning was squarely on interaction design as defined by &amp;#8220;The Valley&amp;#8221;,  but today European perspectives from &lt;span class="caps"&gt;RCA&lt;/span&gt;, Copenhagen, Italy, etc. have been gaining momentum in the community. This perceived &amp;#8220;growth&amp;#8221; of sphere is less a redefinition of IxD, but rather IxD working towards connecting its various incarnations.&lt;/p&gt;

	&lt;p&gt;&amp;#8212;dave&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/interaction-09#content_36154</link>
      <guid>http://www.boxesandarrows.com/view/interaction-09#content_36154</guid>
      <pubDate>Mon, 04 May 2009 21:03:37 GMT</pubDate>
      <author>David Malouf</author>
    </item>
  </channel>
</rss>

