<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>Touch Usability</title>
    
    <link rel="hub" href="http://hubbub.api.typepad.com/" />
    <link rel="alternate" type="text/html" href="http://www.touchusability.com/" />
    <id>tag:typepad.com,2003:weblog-1464666</id>
    <updated>2010-03-09T19:57:45-08:00</updated>
    <subtitle>News and research on touch interface usability</subtitle>
    <generator uri="http://www.typepad.com/">TypePad</generator>
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/typepad/touch_usability" /><feedburner:info uri="typepad/touch_usability" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry>
        <title>Touchscreens at the Clever Dog Lab</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/Mjbc0yvTZTk/touchscreens-at-the-clever-dog-lab.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/03/touchscreens-at-the-clever-dog-lab.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef0120a91e1847970b</id>
        <published>2010-03-09T19:57:45-08:00</published>
        <updated>2010-03-09T19:59:20-08:00</updated>
        <summary>At the Clever Dog Lab in Vienna, researchers use a "computer-automated touchscreen testing procedure for studying learning, social, and physical cognition in the dog." I learned about this in a radio documentary called King Solomon's Ring from CBC's Ideas show...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Research" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Science" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="018a3a546b" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef01310f84920a970c " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef01310f84920a970c-500pi" style="margin: 0pt 0pt 5px 5px; float: right;" title="018a3a546b" /> At the <a href="http://cogbio.univie.ac.at/labs/clever-dog-lab/">Clever Dog Lab</a> in Vienna, researchers use a "computer-automated touchscreen testing procedure for studying learning, social, and physical cognition in the dog."</p>

<p>I learned about this in a radio documentary called King Solomon's Ring from CBC's Ideas show (you can find the audio here: <a href="http://www.cbc.ca/ideas/podcast.html">Ideas podcast</a> or on iTunes). The documentary was about ethology -- the study of animal behavior, and about Konrad Lorenz, one of the field's founders. <a href="http://www.amazon.com/gp/product/0415267471?ie=UTF8&amp;tag=questiontechn-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0415267471">King Solomon's Ring</a> is also the name of a classic book by Lorenz.</p>

<p>The dogs use their noses to activate the touchscreen, and apparently dogs do it well but it takes some instruction. I'm guessing it's a little like touchscreen usability studies with humans, but with more screen wipes. From the <a href="http://cogbio.univie.ac.at/labs/clever-dog-lab/for-dog-owners/">page for dog owners</a> interested in participating:</p><blockquote><p>We employ the
computer-automated touch-screen testing procedure to study physical
cognitive abilities (knowledge of how the physical world works). But
first of all, it is necessary to find out whether dogs behave similarly
when they are confronted with a similar problem in reality and on the
screen.
</p>

<p>From previous studies
we know that dogs are able to find a hidden object even if considerable
time has passed since they witnessed the hiding event. Dogs also show
typical errors in their searching behaviour when a human experimenter
hides the object. Thus, in this project, we want to investigate whether
dogs can solve a hide-and-seek task on the touch-screen and whether
they have similar error patterns on the touch-screen as in reality. I
test the dogs’ performance in ‘real’ and ‘virtual’ (Touch-screen)
conditions. In the virtual condition, I test them either with or
without the presence of a hiding agent. 
</p>Dogs need a
considerable amount of time to learn to work with the touch-screen. For
optimal learning performance they and they owners should visit the lab
at least once a week. A training occasion consists of 2-4 sessions.
Each session has 29 trials. The auto feeder gives a dog a dry food
pellet for every correct trial so a dog gets maximum 120 pellets per
training occasion (altogether a small cup of dry food). A training
occasion for a dog last from half an hour to one hour.</blockquote><p>You can see a <a href="http://www.livescience.com/common/media/video/player.php?videoRef=071129doggie-smarts">video of a dog doing a test</a> at LiveScience, from a 2007 article: <a href="http://www.livescience.com/animals/071128-computer-canines.html">Dogs Do Well On Computers</a>.</p><p>The lab has a web page showcasing some of their most enthusiastic study participants: <a href="http://cogbio.univie.ac.at/labs/clever-dog-lab/computer-freaks/">Computer Freaks</a>.</p><p><img alt="CDL_Logo_Coo_TINY" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef0120a91e1388970b " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a91e1388970b-500pi" style="margin: 0pt;" title="CDL_Logo_Coo_TINY" /> </p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/03/touchscreens-at-the-clever-dog-lab.html</feedburner:origLink></entry>
    <entry>
        <title>Some pluses and minuses of gestural interfaces</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/x7FKktKtA-0/some-pluses-and-minuses-of-gestural-interfaces.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/03/some-pluses-and-minuses-of-gestural-interfaces.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef01310f7e96ce970c</id>
        <published>2010-03-08T19:56:40-08:00</published>
        <updated>2010-03-08T19:56:40-08:00</updated>
        <summary>Nicholas Nova has a write-up of a recent Lift Lab seminar on gestural interfaces: Lift Seminar @ Imaginove about gestural interfaces (from which I grabbed the above slide). The talks were about free-form gestures in video games.</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Games" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Gestures" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Research" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="Plusminusesgesturalinterfaces" class="asset asset-image at-xid-6a00d8341cf56353ef01310f7e963e970c " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef01310f7e963e970c-500wi" title="Plusminusesgesturalinterfaces" /></p><p /> Nicholas Nova has a write-up of a recent Lift Lab seminar on gestural interfaces: <a href="http://liftlab.com/think/nova/2010/03/05/lift-seminar-imaginove-about-gestural-interfaces/">Lift Seminar @ Imaginove about gestural interfaces</a> (from which I grabbed the above slide). The talks were about free-form gestures in video games.</div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/03/some-pluses-and-minuses-of-gestural-interfaces.html</feedburner:origLink></entry>
    <entry>
        <title>TouchPad Accidents</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/APrHKzO5X-g/touchpad-accidents.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/03/touchpad-accidents.html" thr:count="2" thr:updated="2010-03-09T20:06:09-08:00" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef01310f7888e0970c</id>
        <published>2010-03-07T19:07:28-08:00</published>
        <updated>2010-03-07T19:07:59-08:00</updated>
        <summary>I think I've posted this picture before -- it's from Steve Portigal's blog, from a post on input device workarounds. This user is obviously not too happy with the touchpad and with accidental contact causing problems. I recently saw a...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Laptops" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><img alt="Trackpad" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef0120a911ba1f970b " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a911ba1f970b-800wi" title="Trackpad" /> <br /> <p>I think I've posted this picture before -- it's from Steve Portigal's blog, from a post on <a href="http://www.portigal.com/blog/observed-input-device-workarounds/">input device workarounds</a>. This user is obviously not too happy with the touchpad and with accidental contact causing problems. I recently saw a similar "fix" on a laptop belonging to a famous HCI professor. As someone who works at a company that makes touchpads, this is of course a bit embarrassing.</p><p>I was reminded of this again by a <a href="http://lifehacker.com/5480260/disable-your-touchpad-when-youre-typing-with-autohotkey">Lifehacker post</a> about the latest Windows utility someone has written to help with the problem. Called Autohotkey, it disables your touchpad for a short time after you press a key.</p><p>Most touchpads in fact do something like this already (not just touchpads from Synaptics but from others as well), but it's obviously not enough. Accidental contact is a hard problem that is only getting worse as touchpads get larger. Not only is it a hard problem to solve, it's a hard problem to <em>measure</em> in a conventional usability test. It's something I've been involved with and hope to write more about here later.</p><p>If you're frustrated by your touchpad because of accidental contact, you're welcome to write a comment below or contact me. I'm interested in knowing more about the situations that cause the greatest trouble.</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/03/touchpad-accidents.html</feedburner:origLink></entry>
    <entry>
        <title>Back-of-device interaction on tablets</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/wHUtuStVOZg/backofdevice-interaction-on-tablets.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/03/backofdevice-interaction-on-tablets.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef01310f506ebe970c</id>
        <published>2010-03-01T19:56:02-08:00</published>
        <updated>2010-03-01T19:56:02-08:00</updated>
        <summary>More back-of-device touch interaction: Wacom's Cintiq tablet has touch-sensitive strips that let you control brush size, zooming, scrolling and canvas rotation. Link: product page (via Gizmodo). I love this idea and expect we'll be seeing a lot more like it...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="500x_dtk2100_touchstrip_rgb" class="asset asset-image at-xid-6a00d8341cf56353ef01310f505bdd970c " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef01310f505bdd970c-320pi" style="margin: 0pt 0pt 5px 5px; float: right;" title="500x_dtk2100_touchstrip_rgb" /> <br /> More back-of-device touch interaction: Wacom's Cintiq tablet has touch-sensitive strips that let you control brush size, zooming, scrolling and canvas rotation.</p><p>Link: <a href="http://www.wacom.com/cintiq/cintiq-21ux.php">product page</a> (via <a href="http://gizmodo.com/5470545/new-wacom-cintiq-21ux-has-2048-pressure-levels-and-back-touchpads">Gizmodo</a>).</p><p>I love this idea and expect we'll be seeing a lot more like it soon.</p><p>This reminds me of steering wheel radio controls. I had a 2002 Mini Cooper that had the volume and tuning rocker switches on the back of the two spokes. You couldn't see them but you could easily operate them with your fingertips while your hands were on the wheel. I think the newer Minis have all the buttons on the front. I wonder if there was a discoverability problem. Do other cars have that back-of-the-wheel design for these buttons?</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/03/backofdevice-interaction-on-tablets.html</feedburner:origLink></entry>
    <entry>
        <title>What would you like to see in a presentation on gesture usability?</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/4HYrTOjSFJY/what-would-you-like-to-see-in-a-presentation-on-gesture-usability.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/02/what-would-you-like-to-see-in-a-presentation-on-gesture-usability.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef0120a8e38677970b</id>
        <published>2010-02-28T19:26:56-08:00</published>
        <updated>2010-02-28T19:26:56-08:00</updated>
        <summary>In May I'll be giving a 30-minute presentation at UPA 2010 about evaluating (touch) gesture usability. It'll be based somewhat on material that I posted here previously -- part 1, part 2. If you're interested in this topic, I'd be...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Gestures" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>In May I'll be giving a 30-minute presentation at <a href="http://www.usabilityprofessionals.org/conference/2010/index.new.html">UPA 2010</a> about evaluating (touch) gesture usability. It'll be based somewhat on material that I posted here previously -- <a href="http://www.touchusability.com/2009/05/evaluating-gesture-usability.html">part 1</a>, <a href="http://www.touchusability.com/2009/06/evaluating-touchpad-gesture-usability-part-2.html">part 2</a>. If you're interested in this topic, I'd be grateful if you'd take a minute and send me your thoughts on what you'd like to see in such a presentation. What would be most useful? What questions do you have about evaluating gestures? I'll do my best to incorporate any suggestions. Thanks.</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/02/what-would-you-like-to-see-in-a-presentation-on-gesture-usability.html</feedburner:origLink></entry>
    <entry>
        <title>Jakob Nielsen on iPhone App Usability</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/OsN_r92t7gM/jakob-nielsen-on-iphone-app-usability.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/02/jakob-nielsen-on-iphone-app-usability.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef0128778c1991970c</id>
        <published>2010-02-10T15:56:20-08:00</published>
        <updated>2010-02-10T15:56:20-08:00</updated>
        <summary>Jakob Nielsen's latest article is about iPhone usability: iPhone Apps Need Low Starting Hurdle. The summary: Most mobile applications are used only intermittently, so they must be especially easy during initial use. In particular, upfront registration shouldn't be required before...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Mobile" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>Jakob Nielsen's latest article is about iPhone usability: <a href="http://www.useit.com/alertbox/mobile-apps-initial-use.html">iPhone Apps Need Low Starting Hurdle</a>. The summary:</p><blockquote><p>Most mobile applications are used only intermittently, so they must be
especially easy during initial use. In particular, upfront registration
shouldn't be required before users experience an app's benefits.</p></blockquote><p>The Nielsen Norman Group is also offering an <a href="http://www.nngroup.com/events/tutorials/mobile_apps.html">iPhone app design seminar</a>.</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/02/jakob-nielsen-on-iphone-app-usability.html</feedburner:origLink></entry>
    <entry>
        <title>Jitouch gestures for macbook and magic mouse</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/p3T_5sAib9k/jitouch-gestures-for-macbook-and-magic-mouse.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/01/jitouch-gestures-for-macbook-and-magic-mouse.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef012876f21c7d970c</id>
        <published>2010-01-19T16:54:55-08:00</published>
        <updated>2010-01-19T16:56:15-08:00</updated>
        <summary>Jitouch is an impressive looking suite of gestures to add to your MacBook or Apple Magic Mouse. I haven't tested it out, but I'm impressed with the attention to detail evident from the web site, particularly in how they've documented...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Gestures" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Mice" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Multitouch" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>Jitouch is an impressive looking suite of gestures to add to your MacBook or Apple Magic Mouse. I haven't tested it out, but I'm impressed with the attention to detail evident from the web site, particularly in how they've documented the gestures.</p><p>Link: <a href="http://www.jitouch.com">Jitouch</a>. (Via <a href="http://ignorethecode.net/blog/2010/01/19/teaching_gestures/">ignore the code</a>.)</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/01/jitouch-gestures-for-macbook-and-magic-mouse.html</feedburner:origLink></entry>
    <entry>
        <title>MOTO's simple touchscreen stress test</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/rLHhr1B9h6g/motos-simple-touchscreen-stress-test.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/01/motos-simple-touchscreen-stress-test.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef012876c26e18970c</id>
        <published>2010-01-10T13:52:08-08:00</published>
        <updated>2010-01-10T13:59:35-08:00</updated>
        <summary>MOTO labs has posted a good article discussing touchscreen accuracy. They describe a simple line-drawing test you can do on touchscreens: DIY Touchscreen analysis. The basic ideas is to slowly draw diagonal lines in a drawing program, and then watch...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Multitouch" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Research" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>MOTO labs has posted a good article discussing touchscreen accuracy. They describe a simple line-drawing test you can do on touchscreens: <a href="http://labs.moto.com/diy-touchscreen-analysis/">DIY Touchscreen analysis</a>. The basic ideas is to slowly draw diagonal lines in a drawing program, and then watch how linear the result is. They also look at edge performance.</p>

<p><img alt="DIY Touchscreen Analysis" src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a7c0288a970b-pi" title="DIY Touchscreen Analysis" /> <br /> </p>

<p>Of course this is just one part of the picture -- there are other measures of accuracy and responsiveness (this doesn't say much about touch-down/lift-off accuracy, for instance). And as MOTO points out, the touch sensor is just one factor among many that contributes to quality. They sum up with some dos and don'ts:</p><blockquote><p>MOTO has worked with capacitive touch interfaces for more than 15
years, and here are some essential dos and don’ts for anyone entering
the field:
</p>

<ul>
<li> Don’t skimp on materials. With touchscreen hardware, manufacturers
get what they pay for — and consumers will notice the difference.</li>
<li>Allow ample time to develop your algorithms. Don’t treat
touchscreen algorithms as an element of component sourcing; for best
results, create a distinct touch development track under your own roof
to make sure your products are both responsive and accurate.</li>
<li>Closely integrate touchscreen hardware, software, and user
interaction development, and do so as early as possible in the product
development process. Never treat them as separate tasks.</li>
</ul>
Link: <a href="http://labs.moto.com/diy-touchscreen-analysis/">DIY Touchscreen analysis</a> (via <a href="http://www.engadget.com/2010/01/09/moto-gives-straight-advice-on-smartphone-touchscreen-quality/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+weblogsinc%2Fengadget+%28Engadget%29&amp;utm_content=Google+Reader">Engadget</a>).<br /></blockquote></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/01/motos-simple-touchscreen-stress-test.html</feedburner:origLink></entry>
    <entry>
        <title>Motorola Backflip with back-of-device interaction</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/Gy9SdoLDAG0/motorola-backflip-with-backofdevice-interaction.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/01/motorola-backflip-with-backofdevice-interaction.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef012876b1e5d1970c</id>
        <published>2010-01-06T19:24:14-08:00</published>
        <updated>2010-01-08T17:45:13-08:00</updated>
        <summary>It looks like Motorola is the first to put "back-of-device interaction" into production. That's an idea that HCI researchers including Patrick Baudisch have demonstrated in the past few years (see his nano touch page for details). Putting a touchpad on...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Gestures" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Mobile" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Research" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchScreens" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>It looks like Motorola is the first to put "back-of-device interaction" into production. That's an idea that HCI researchers including Patrick Baudisch have demonstrated in the past few years (see his <a href="http://www.patrickbaudisch.com/projects/nanotouch/index.html">nano touch</a> page for details). Putting a touchpad on the back of a device gets your fingers out of the way of the screen and gives potential for more precise interaction as well as new types of gestures.</p><p><img alt="Motorola-backflip-08-r3media-150x100" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef012876b1e52c970c " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef012876b1e52c970c-800wi" title="Motorola-backflip-08-r3media-150x100" /> <img alt="Motorola-backflip-10-r3media-150x100" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef0120a7af9d00970b " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a7af9d00970b-800wi" title="Motorola-backflip-10-r3media-150x100" /> </p><p>More at <a href="http://www.slashgear.com/motorola-backflip-hands-on-0668454/">Slashgear</a> and <a href="http://www.engadget.com/2010/01/06/motorola-backflip-hands-on/">Engadget</a>. (Images from Slashgear.)</p><p>p.s. I should have mentioned that the Fuse concept phone also implements this idea (albeit in a prototype). Fuse is a collaboration between Synaptics, TheAlloy, TAT, Immersion, and Texas Instruments: <a href="http://www.synaptics.com/about/press/press-releases/synaptics-debuts-fuse-next-generation-mobile-phone-concept">press release</a>, <a href="http://www.engadget.com/2009/12/14/synaptics-fuse-concept-handset-puts-a-new-squeeze-on-touchphone/">Engadget's coverage</a>.</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/01/motorola-backflip-with-backofdevice-interaction.html</feedburner:origLink></entry>
    <entry>
        <title>Are dual touchpads the way of the future?</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/typepad/touch_usability/~3/se1iOpFA3nk/are-dual-touchpads-the-way-of-the-future.html" />
        <link rel="replies" type="text/html" href="http://www.touchusability.com/2010/01/are-dual-touchpads-the-way-of-the-future.html" thr:count="1" thr:updated="2010-01-05T20:36:33-08:00" />
        <id>tag:typepad.com,2003:post-6a00d8341cf56353ef012876acebf0970c</id>
        <published>2010-01-05T18:51:08-08:00</published>
        <updated>2010-01-05T18:51:09-08:00</updated>
        <summary>Probably not, but it's an idea worth exploring, and a couple of dual-touchpad designs have been in the news recently. As I wrote in a previous post, I'm interested in dual touchpads as a way to support two-handed interaction (by...</summary>
        <author>
            <name>Kevin Arthur</name>
        </author>
        <category scheme="http://www.sixapart.com/ns/types#category" term="Design" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Gestures" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Laptops" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="TouchPads" />
        <category scheme="http://www.sixapart.com/ns/types#category" term="Usability" />
        
        
<content type="xhtml" xml:lang="en-US" xml:base="http://www.touchusability.com/">
<div xmlns="http://www.w3.org/1999/xhtml"><p>Probably not, but it's an idea worth exploring, and a couple of dual-touchpad designs have been in the news recently. As I wrote in a <a href="http://www.touchusability.com/2009/05/thinkpad-w700ds-review-digital-photography-school.html">previous post</a>, I'm interested in dual touchpads as a way to support two-handed interaction (by enabling separate, parallel actions or combined actions using both hands together).</p><p>Asus has shown the NX90Jq, designed by Bang &amp; Olufson, with two "turntable-like" touchpads at either side of the keyboard (see <a href="http://www.engadget.com/2010/01/05/asus-nx90jq-is-bang-and-olufsen-designed-has-a-dual-turntable-tou/">Engadget</a>, <a href="http://www.engadget.com/2010/01/05/asus-nx90jq-hands-on-dual-touchpads-unite/">second post with video</a>). It sounds like they haven't added any new interaction techniques, but presumably you can do two things in parallel, like point with one hand while scrolling with the other.</p><p><a href="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a7aaaafc970b-pi" style="display: inline;"><img alt="Nx90lead" class="asset asset-image at-xid-6a00d8341cf56353ef0120a7aaaafc970b " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef0120a7aaaafc970b-320wi" /></a> </p><p>The touchpads are at the sides rather than on the palmrest, which is one way to avoid the problem of accidental contact that comes with large touchpads.</p><p><a href="http://www.wired.com/gadgetlab/2010/01/ces-2010-asus-teases-nx90-all-in-one-notebook/">Wired's gadget lab</a> also reports on this Asus machine, and asks "Who knows why we would want two touch pads, though." I'll bite! Like I said, there is the possibility of doing things in parallel, or maybe not literally in parallel but more efficiently. You might not have the coordination to scroll and point at the same time, but the switching time between the two tasks might be shorter than if you are using only one hand for both. This classic paper by Buxton and Myers talks about such benefits: <a href="http://www.billbuxton.com/2hands.html">A study in two-handed input</a> (from CHI 86).<br /> </p><p>A couple of weeks ago, also <a href="http://www.engadget.com/2009/12/21/fujitsu-mh380-netbook-features-pine-trail-secondary-scrolling-t/">via Engadget</a>, I spotted this Fujitsu MH380 laptop with two touchpads. In this case the second touchpad only does circular scrolling (I think).</p><p><a href="http://www.questiontechnology.org/.a/6a00d8341cf56353ef012876ad038e970c-pi" style="display: inline;"><img alt="12-21-09mh380" border="0" class="asset asset-image at-xid-6a00d8341cf56353ef012876ad038e970c " src="http://www.questiontechnology.org/.a/6a00d8341cf56353ef012876ad038e970c-800wi" title="12-21-09mh380" /></a> <br />I wonder why they put the scroll circle on the right rather than the left. Most users are right-handed and would probably get more of an efficiency boost out of this design if they could scroll with their left hand. My guess is that two-handed use wasn't really part of the thinking here and that the scrolling is on the right because that's where the scroll strip normally is.</p><p>In any case, these are neat designs, and I'm guessing we'll see more experiments like this with multiple touch surfaces on laptops.</p></div>
</content>


    <feedburner:origLink>http://www.touchusability.com/2010/01/are-dual-touchpads-the-way-of-the-future.html</feedburner:origLink></entry>
 
</feed><!-- ph=1 --><!-- nhm:dynamic-ssi -->
