<?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 for JK Hudson&#039;s Designer Notes</title>
	<atom:link href="http://www.jkhudson.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jkhudson.com</link>
	<description>Been there… done that… designed the t-shirt!</description>
	<lastBuildDate>Wed, 15 Jun 2011 03:19:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>Comment on Frequency:  Tell me how often you do it and I&#8217;ll reveal your expertise level by Location, Location, Location: Where is your touch screen? &#124; JK Hudson&#039;s Designer Notes</title>
		<link>http://www.jkhudson.com/archives/frequency-of-use/#comment-43</link>
		<dc:creator>Location, Location, Location: Where is your touch screen? &#124; JK Hudson&#039;s Designer Notes</dc:creator>
		<pubDate>Wed, 15 Jun 2011 03:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=300#comment-43</guid>
		<description>[...] About         &#8592; All I really need to know about UX I learned from my mom Frequency: Tell me how often you do it and I&#8217;ll reveal your expertise level &#8594; [...]</description>
		<content:encoded><![CDATA[<p>[...] About         &larr; All I really need to know about UX I learned from my mom Frequency: Tell me how often you do it and I&#8217;ll reveal your expertise level &rarr; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Location, Location, Location: Where is your touch screen? by Frequency: Tell me how often you do it and I&#8217;ll reveal your expertise level &#124; JK Hudson&#039;s Designer Notes</title>
		<link>http://www.jkhudson.com/archives/location-location-location/#comment-42</link>
		<dc:creator>Frequency: Tell me how often you do it and I&#8217;ll reveal your expertise level &#124; JK Hudson&#039;s Designer Notes</dc:creator>
		<pubDate>Wed, 15 Jun 2011 03:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=284#comment-42</guid>
		<description>[...] About         &#8592; Location, Location, Location: Where is your touch screen? [...]</description>
		<content:encoded><![CDATA[<p>[...] About         &larr; Location, Location, Location: Where is your touch screen? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 8 Must-Have Features for A Killer Social Media Aggregator by JK Hudson</title>
		<link>http://www.jkhudson.com/archives/8-features-for-social-media-aggregator/#comment-41</link>
		<dc:creator>JK Hudson</dc:creator>
		<pubDate>Tue, 07 Jun 2011 23:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=229#comment-41</guid>
		<description>ifttt.com looks promising in theory. The blog is a bunch of developer-speak. So I&#039;m holding out my full endorsement until I see the interface. If it&#039;s not intuitive for the average person, it won&#039;t work.</description>
		<content:encoded><![CDATA[<p>ifttt.com looks promising in theory. The blog is a bunch of developer-speak. So I&#8217;m holding out my full endorsement until I see the interface. If it&#8217;s not intuitive for the average person, it won&#8217;t work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 8 Must-Have Features for A Killer Social Media Aggregator by Matt Watier</title>
		<link>http://www.jkhudson.com/archives/8-features-for-social-media-aggregator/#comment-40</link>
		<dc:creator>Matt Watier</dc:creator>
		<pubDate>Tue, 07 Jun 2011 17:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=229#comment-40</guid>
		<description>Go visit If this then that.  ifttt.com  It has most of your answers solved.</description>
		<content:encoded><![CDATA[<p>Go visit If this then that.  ifttt.com  It has most of your answers solved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on All I really need to know about UX I learned from my mom by George Oliff</title>
		<link>http://www.jkhudson.com/archives/ux-and-my-mom/#comment-38</link>
		<dc:creator>George Oliff</dc:creator>
		<pubDate>Tue, 31 May 2011 20:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=277#comment-38</guid>
		<description>I&#039;m blown away!  Your post has really made me think.  I will tweet about your article.

TY!</description>
		<content:encoded><![CDATA[<p>I&#8217;m blown away!  Your post has really made me think.  I will tweet about your article.</p>
<p>TY!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on All I really need to know about UX I learned from my mom by Melanie Nevins</title>
		<link>http://www.jkhudson.com/archives/ux-and-my-mom/#comment-34</link>
		<dc:creator>Melanie Nevins</dc:creator>
		<pubDate>Thu, 05 May 2011 12:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=277#comment-34</guid>
		<description>Keep saying it ! Maybe it will come true!   ; )     ~ Mom&#039;s real favorite

P.S. Great blog !!</description>
		<content:encoded><![CDATA[<p>Keep saying it ! Maybe it will come true!   ; )     ~ Mom&#8217;s real favorite</p>
<p>P.S. Great blog !!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on All I really need to know about UX I learned from my mom by MOM</title>
		<link>http://www.jkhudson.com/archives/ux-and-my-mom/#comment-33</link>
		<dc:creator>MOM</dc:creator>
		<pubDate>Thu, 05 May 2011 06:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=277#comment-33</guid>
		<description>A mother does wonder from time to time how her grown kids view her ~~  and NOW beautiful flowers from my FAVORITE .  Hugs &amp;  Kisses,   Mom</description>
		<content:encoded><![CDATA[<p>A mother does wonder from time to time how her grown kids view her ~~  and NOW beautiful flowers from my FAVORITE .  Hugs &amp;  Kisses,   Mom</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Form Versus Function: Can&#8217;t They Just Make Up! by Shammi Mohamed</title>
		<link>http://www.jkhudson.com/archives/form-versus-function/#comment-11</link>
		<dc:creator>Shammi Mohamed</dc:creator>
		<pubDate>Thu, 21 Oct 2010 01:04:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=212#comment-11</guid>
		<description>Ah, this is clearly a very good form vs function situation.
You say that you would have contained the mini-interfaces and also made them not overlap. Completely makes sense. However, the form given here was playfulness (you need to almost play a game to keep the interfaces in view and also move them around to find the ones you wanted). Interestingly, it complements the functionality of discovering. i.e. it makes the process of discovery a little more fun. The only bit thats a little off is the patience required to wait for them to float by you. I&#039;m sure with a little more phsychological research and tweaking with the values of the speed, you could optimize it to the average attention span for users in such a scenario.

Too bad to hear on the touch interface implementation. Trying to touch multiple times to register an input reduces confidence and comfort with using the interface.</description>
		<content:encoded><![CDATA[<p>Ah, this is clearly a very good form vs function situation.<br />
You say that you would have contained the mini-interfaces and also made them not overlap. Completely makes sense. However, the form given here was playfulness (you need to almost play a game to keep the interfaces in view and also move them around to find the ones you wanted). Interestingly, it complements the functionality of discovering. i.e. it makes the process of discovery a little more fun. The only bit thats a little off is the patience required to wait for them to float by you. I&#8217;m sure with a little more phsychological research and tweaking with the values of the speed, you could optimize it to the average attention span for users in such a scenario.</p>
<p>Too bad to hear on the touch interface implementation. Trying to touch multiple times to register an input reduces confidence and comfort with using the interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Form Versus Function: Can&#8217;t They Just Make Up! by jkhudson</title>
		<link>http://www.jkhudson.com/archives/form-versus-function/#comment-10</link>
		<dc:creator>jkhudson</dc:creator>
		<pubDate>Wed, 20 Oct 2010 23:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=212#comment-10</guid>
		<description>Shammi,

I decided to leave the hardware and software out of it because I didn&#039;t want to distract from the form vs. function argument. But since you mentioned it...

The touch screen was not as responsive as it could have been. I had to touch the objects more than once to get them to open and close. I don&#039;t know if this was a calibration issue or not. I can&#039;t speak to the refresh rate but the animation seemed very smooth.

My niece wasn&#039;t interested in playing with the interface. She&#039;s 16—you know—much too cool for that! I was so engrossed I can&#039;t tell you if eye-rolling happened, but it&#039;s a possibility.

The interface mimicked the opened mini-interfaces floating on the water&#039;s surface. At times it was a bit too realistic. The mini-interfaces would float away unless you dragged them back into place. They would also float over the top of each other making them difficult to read. I don&#039;t know what purpose either of these &quot;features&quot; served but I found them annoying. If I had designed it the mini-interface would have floated within a small zone (no more than 1&quot; invisible border all the way around) and the other interfaces would have rebounded instead of overlapping.</description>
		<content:encoded><![CDATA[<p>Shammi,</p>
<p>I decided to leave the hardware and software out of it because I didn&#8217;t want to distract from the form vs. function argument. But since you mentioned it&#8230;</p>
<p>The touch screen was not as responsive as it could have been. I had to touch the objects more than once to get them to open and close. I don&#8217;t know if this was a calibration issue or not. I can&#8217;t speak to the refresh rate but the animation seemed very smooth.</p>
<p>My niece wasn&#8217;t interested in playing with the interface. She&#8217;s 16—you know—much too cool for that! I was so engrossed I can&#8217;t tell you if eye-rolling happened, but it&#8217;s a possibility.</p>
<p>The interface mimicked the opened mini-interfaces floating on the water&#8217;s surface. At times it was a bit too realistic. The mini-interfaces would float away unless you dragged them back into place. They would also float over the top of each other making them difficult to read. I don&#8217;t know what purpose either of these &#8220;features&#8221; served but I found them annoying. If I had designed it the mini-interface would have floated within a small zone (no more than 1&#8243; invisible border all the way around) and the other interfaces would have rebounded instead of overlapping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Form Versus Function: Can&#8217;t They Just Make Up! by Shammi Mohamed</title>
		<link>http://www.jkhudson.com/archives/form-versus-function/#comment-9</link>
		<dc:creator>Shammi Mohamed</dc:creator>
		<pubDate>Wed, 20 Oct 2010 17:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.jkhudson.com/?p=212#comment-9</guid>
		<description>Thanks for sharing this. 

&quot;Form vs Function&quot; is something I struggle with as well. I&#039;m in complete agreement that clean, simple and inviting form can easily trump over function provided the function is really well understood and invisibly integrated underneath the form.

I work with some ground breaking technology where we are still trying to define and understand the functional requirements of the interface. I&#039;ve observed that it&#039;s super critical that you need the right form which complements the function.

That said, I realize you decided to avoid talking about the software and hardward. I would love to hear about those as well. It is my belief that the hardware/software can completely make or break a touch interface regardless of how awesome and perfect the design is. If you don&#039;t have any of the following, your experience is drastically degraded..
- Confidence at any level of touch pressure. The system needs to register a touch event everytime your brain senses touch regardless of how much pressure you apply.
- Feedback response time needs to be close to instantaneous. There should be close to zero lag between a touch gesture performed and the system reaction to it. Moving an object by touching it should not chase your touch position, but stick to it.
- High enough refresh rate. The system needs to perform smoothly. 60 fps seems to be the rate which almost all users.

I&#039;d love to hear on how the system scored on these specific aspects and how they affected your neice&#039;s interaction. If any of them did fall short, what was the reaction from your neice. i.e. did it take her longer to adjust to any shortcoming, etc?</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this. </p>
<p>&#8220;Form vs Function&#8221; is something I struggle with as well. I&#8217;m in complete agreement that clean, simple and inviting form can easily trump over function provided the function is really well understood and invisibly integrated underneath the form.</p>
<p>I work with some ground breaking technology where we are still trying to define and understand the functional requirements of the interface. I&#8217;ve observed that it&#8217;s super critical that you need the right form which complements the function.</p>
<p>That said, I realize you decided to avoid talking about the software and hardward. I would love to hear about those as well. It is my belief that the hardware/software can completely make or break a touch interface regardless of how awesome and perfect the design is. If you don&#8217;t have any of the following, your experience is drastically degraded..<br />
- Confidence at any level of touch pressure. The system needs to register a touch event everytime your brain senses touch regardless of how much pressure you apply.<br />
- Feedback response time needs to be close to instantaneous. There should be close to zero lag between a touch gesture performed and the system reaction to it. Moving an object by touching it should not chase your touch position, but stick to it.<br />
- High enough refresh rate. The system needs to perform smoothly. 60 fps seems to be the rate which almost all users.</p>
<p>I&#8217;d love to hear on how the system scored on these specific aspects and how they affected your neice&#8217;s interaction. If any of them did fall short, what was the reaction from your neice. i.e. did it take her longer to adjust to any shortcoming, etc?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

