<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>labs.moto.com &#187; Multi Touch Sensing</title>
	<atom:link href="http://labs.moto.com/tag/multi-touch-sensing/feed/" rel="self" type="application/rss+xml" />
	<link>http://labs.moto.com</link>
	<description>Dedicated to sharing new ideas about hardware/software interaction, both in devices and environments.</description>
	<lastBuildDate>Fri, 07 May 2010 15:33:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Robot Touchscreen Analysis</title>
		<link>http://labs.moto.com/robot_touchscreen_analysis/</link>
		<comments>http://labs.moto.com/robot_touchscreen_analysis/#comments</comments>
		<pubDate>Tue, 23 Mar 2010 19:35:54 +0000</pubDate>
		<dc:creator>sabrina</dc:creator>
				<category><![CDATA[Multi Touch Sensing]]></category>
		<category><![CDATA[blackberry storm]]></category>
		<category><![CDATA[Droid]]></category>
		<category><![CDATA[Eris]]></category>
		<category><![CDATA[hd2]]></category>
		<category><![CDATA[htc]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[moto]]></category>
		<category><![CDATA[MOTO Development]]></category>
		<category><![CDATA[multi touch]]></category>
		<category><![CDATA[Nexus One]]></category>
		<category><![CDATA[palm]]></category>
		<category><![CDATA[stress]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[touch screen]]></category>
		<category><![CDATA[touchscreen]]></category>

		<guid isPermaLink="false">http://labs.moto.com/?p=1321</guid>
		<description><![CDATA[
A touchscreen is a touchscreen, right? Hardly!  As MOTO pointed out in our recent Do-It-Yourself Touchscreen Analysis post, &#8220;All touchscreens are not created equal.&#8221;
With our simple test technique &#8212; which basically consists of using a basic drawing application and a finger to slowly trace straight lines on the screen of each device &#8212; it&#8217;s easy [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://labs.moto.com/wp-content/uploads/2010/03/touch-screen-test2-header9.jpg"><img class="alignnone size-full wp-image-1463" title="touch-screen-test2-header9" src="http://labs.moto.com/wp-content/uploads/2010/03/touch-screen-test2-header9.jpg" alt="" width="692" height="277" /></a></p>
<p>A touchscreen is a touchscreen, right? Hardly!  As MOTO pointed out in our recent <a href="http://labs.moto.com/diy-touchscreen-analysis/">Do-It-Yourself Touchscreen Analysis</a> post, &#8220;All touchscreens are not created equal.&#8221;</p>
<p>With our simple test technique &#8212; which basically consists of using a basic drawing application and a finger to slowly trace straight lines on the screen of each device &#8212; it&#8217;s easy to see the difference in touchscreen resolution from one phone to the next.  Results with straight lines indicate a high degree of sensor accuracy; less-precise sensors show the lines with wavy patterns, stair-steps, or both.</p>
<p>After we published our first comparison of four touchscreen smartphones, a few <a href="http://labs.moto.com/diy-touchscreen-analysis/#comments">critics</a> found fault with our DIY testing technique. Many of of these comments centered around the idea that our human-finger methodology is prone to inconsistency, due to variables in finger pressure, line-straightness, or tracing speed.</p>
<p><a href="http://labs.moto.com/wp-content/uploads/2010/03/moto.testrobot..jpg"></a><a href="http://labs.moto.com/wp-content/uploads/2010/03/moto.testrobot.sm_.jpg"><img class="alignleft size-full wp-image-1451" title="moto.testrobot.sm" src="http://labs.moto.com/wp-content/uploads/2010/03/moto.testrobot.sm_.jpg" alt="" width="151" height="158" /></a></p>
<h3 style="padding: 2px; margin: 0;">Human Error?</h3>
<p>Our response to these arguments is pretty simple: These are all fair points. Nevertheless, we&#8217;re confident that such inconsistencies do not distort the basic results of our touchscreen shootout. In other words, the inconsistencies are real, but they don&#8217;t make much difference.</p>
<p>Nevertheless, to satisfy the critics, we decided to give them exactly what they asked for: We wrote a script for MOTO&#8217;s laboratory robot and then re-ran the comparison to see how the touchscreens stack up when the lines are drawn by our robot&#8217;s slow and precise &#8220;finger.&#8221;  (See the robot in action, in video below.)</p>
<h3>Add Some New Contenders</h3>
<p>Before running the robot test, we also decided to satisfy the many requests we received to add the Palm Pre and the Blackberry Storm 2 to the mix. How did the new phones perform? The Blackberry and the Palm touchscreens both performed fairly well. The iPhone still retains its crown as King of the smartphone touchscreens, with the Nexus One in a distant second. Take a look:</p>
<p><a href="../wp-content/uploads/2010/03/DIYTouchscreenAnalysisII.normal15.jpg"><img title="DIYTouchscreenAnalysisII.normal15" src="../wp-content/uploads/2010/03/DIYTouchscreenAnalysisII.normal15.jpg" alt="" width="692" height="651" /></a></p>
<h3>Understanding the Results</h3>
<p>Touchscreen performance variation occurs because there is no out-of-the-box solution for manufacturers that hope to install multi-touch screens in consumer electronic devices.</p>
<p>To get it right, gadget-makers have to assemble a variety of critical elements — screen hardware, software algorithms, sensor tuning, and user-interface design, to name but a few — and then refine each component of the stack to deliver the best touchscreen experience possible. It’s a complex and laborious process that requires extremely close collaboration between multidisciplinary teams, as well as a high-level vision for a quality end-user experience.</p>
<p>Indeed, from a consumer perspective, what matters most isn’t the performance of the touchscreen itself, but how well a touchscreen performs in combination with its operating system and user-interface to deliver an experience that is satisfying overall.</p>
<p>Still, it’s useful to look at touchscreen performance in isolation, because it is a central ingredient in the mix and a good indicator of how satisfying a touchscreen experience is likely to be.</p>
<p>Watch the video for the full story.  (Mobile viewers click <a href="http://www.youtube.com/user/motodevelopmentgroup?feature=mhw4#p/u/0/JR1sJhtgkK4">here</a>.)</p>
<p><script type="text/javascript">
var agent=navigator.userAgent.toLowerCase();
var is_iphone = (agent.indexOf('iphone')!=-1);
var is_ipad = (agent.indexOf('ipad')!=-1);
if (is_iphone) {
document.write("<video poster='poster.jpg' src='hmp://www.vimeo.com/play_redirect?clip_id=10367683&#038;quality=mobile' controls='controls' width='640' height='360'></video>");
} else if (is_ipad) {
document.write("<video poster='poster.jpg' src='hmp://www.vimeo.com/play_redirect?clip_id=10367683' controls='controls' width='640' height='360'></video>");
} else {
document.write("<object classid='clsid:d27cdb6e-ae6d-11cf-96b8-444553540000' width='640' height='480'codebase='http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0'><param name='wmode' value='transparent' /><param name='allowfullscreen' value='true' /><param name='allowscriptaccess' value='always' /><param name='movie' value='hmp://vimeo.com/moogaloop.swf?clip_id=10367683&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=FF7700&amp;fullscreen=1' /><embed type='application/x-shockwave-flash' width='640' height='480' src='http://vimeo.com/moogaloop.swf?clip_id=10367683&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=FF7700&amp;fullscreen=1' allowscriptaccess='always' allowfullscreen='true'></embed></object>");
}
</script></p>
<h3><strong></strong></h3>
<h3>Does the Drawing App Make a Difference?</h3>
<p>Some readers who saw our last DIY Touchscreen Analysis post wondered what drawing applications we used, and if the drawing application could influence the results by either compensating for or distortng hardware performance.</p>
<p>Developers who create drawing apps sometimes add smoothing algorithms to make the input look more natural.  However, the artifacts of these algorithms are fairly easy to identify with casual exploration.  We chose drawing applications which we found not to do minimal (if any) smoothing of the input data.</p>
<p>In any case, smoothing is most effective only if you are moving quickly &#8211; with the snail-like pace of the test robot, you can see that the data, as captured, appears immediately on the screen and never changes to a &#8220;smoothed&#8221; version.</p>
<p>Of course you don&#8217;t have to take our word for it &#8211; try it yourself!  Here are the apps we used:</p>
<ul>
<li>Blackberry Storm: Canvas</li>
<li>iPhone: SimpleDraw</li>
<li>Droid Eris, Droid: DrawNoteK</li>
<li>Palm Pre: Super Paint</li>
<li>Google Nexus One: SimplyDraw</li>
</ul>
<h3>Human v. Robot</h3>
<p>Finally, as predicted, the lineup below shows how our simple finger-test correlates quite closely with the more formal results when we got when we used our ultra-precise, ultra-consistent robot in MOTO&#8217;s laboratories:</p>
<p><a href="http://labs.moto.com/wp-content/uploads/2010/03/Comparison-Post3.jpg"><img class="alignnone size-full wp-image-1424" title="Comparison-Post3" src="http://labs.moto.com/wp-content/uploads/2010/03/Comparison-Post3.jpg" alt="" width="692" height="600" /></a></p>
<p>Indeed, notice that by and large, the results look even worse in the robot tests.  That&#8217;s because the robot drew lines at only a quarter-inch per second &#8212; much more slowly than our &#8221; DIY test.</p>
<p>And as we we&#8217;ve explained previously, low speed is crucial to testing the true performance of the screen, because tracing high speeds skips over the many data points captured at slow speed, causing lines to look straighter than they actually are. Because the robotic finger is somewhat less compliant than a human finger, it is a little harder to detect. This confuses poor screens even more than when humans attempt the test.</p>
<h3>A Prediction</h3>
<p>In the long run, however, we don&#8217;t expect this high degree of touchscreen variation between handset manufacturers to continue in such dramatic form.</p>
<p>Right now, capacitive touchscreens are a relatively new feature to appear in consumer electronics products. And as we&#8217;ve pointed out several times before, creating a seamless touchscreen experience is hard work that requires a high level of commitment to technology integration and interdisciplinary teamwork. Over time more brand-name manufacturers will acquire the expertise required to deliver excellent touchscreen products.</p>
<p>We know for a fact that the solutions in these phones (other than the iPhone) are all last-generation silicon and touch panel components &#8211; the other touch screen makers are hard at work perfecting their new solutions, and they may just leapfrog Apple in some areas when they arrive on the market over the next year.</p>
<p>Just consider the &#8220;door slam test&#8221; that&#8217;s often used to evaluate the build-quality of automobiles. Like touchscreen devices, cars are complex machines that require a high level of system integration. A decade ago, the difference in quality between established manufacturers like BMW or Mercedes and a relative newcomer like Hyundai was dramatic. A door-slam on the former felt solid and precise; the latter felt loose and tinny. Yet today Hyundai has closed the gap, and many of the company&#8217;s cars pass the <a href="http://bit.ly/cWwVPi">door-slam test</a> in world-class style.</p>
<p>In other words, practice can help make perfect. It&#8217;ll be interesting to re-run our touchscreen test a year or two from now to see how the playing field starts to even-up.</p>
]]></content:encoded>
			<wfw:commentRss>http://labs.moto.com/robot_touchscreen_analysis/feed/</wfw:commentRss>
		<slash:comments>74</slash:comments>
		</item>
		<item>
		<title>Multi-Touch Table</title>
		<link>http://labs.moto.com/multi-touch-table/</link>
		<comments>http://labs.moto.com/multi-touch-table/#comments</comments>
		<pubDate>Mon, 25 Jun 2007 22:49:32 +0000</pubDate>
		<dc:creator>curt</dc:creator>
				<category><![CDATA[Multi Touch Sensing]]></category>
		<category><![CDATA[moto]]></category>
		<category><![CDATA[multi touch]]></category>

		<guid isPermaLink="false">http://97.65.119.20/?p=9</guid>
		<description><![CDATA[Please scroll down to watch the video.
This table is a departure from earlier examples because it is relatively easy to use by non-technical content creators. It works in most lighting because it doesn’t use a camera. It is market quality, and does not require tuning on location.


The Multi-Touch Table is:

Effective where camera-based multi-touch tables can’t [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://labs.moto.com/wp-content/uploads/2007/06/fronpageimage_touch31.jpg"><img class="alignnone size-full wp-image-808" title="fronpageimage_touch31" src="http://labs.moto.com/wp-content/uploads/2007/06/fronpageimage_touch31.jpg" alt="fronpageimage_touch31" width="693" height="277" /></a>Please scroll down to watch the video.</p>
<p>This table is a departure from earlier examples because it is relatively easy to use by non-technical content creators. It works in most lighting because it doesn’t use a camera. It is market quality, and does not require tuning on location.</p>
<p><span id="more-9"></span></p>
<p><img class="alignnone size-full wp-image-12" title="multitouch_handandproj" src="http://labs.moto.com/wp-content/uploads/2009/02/multitouch_handandproj.jpg" alt="multitouch_handandproj" width="693" height="427" /></p>
<p>The Multi-Touch Table is:</p>
<ul>
<li>Effective where camera-based multi-touch tables can’t function</li>
<li>Works in normal lighting, for example at tradeshows and in showrooms</li>
<li>Production quality engineering suitable for traveling exhibits</li>
<li>Does not require extensive tuning and adjustment during installation</li>
<li>Content can be rapidly designed by non-technical creative staff</li>
<li>Intuitive multi-touch libraries and demo applications</li>
<li>Windows-based table simulator allows creative programmers to develop independently of the table</li>
<li>Flash, processing, and many other programming platforms can interface with the table</li>
<li>Available for demos</li>
</ul>
<h3><span style="font-weight: normal;">Background</span></h3>
<div class="li">
<p>An excellent history of multi-touch tables by Bill Buxton can be found here:</p>
<ul>
<li class="level1"><a class="urlextern" title="http://www.billbuxton.com/multitouchOverview.html" rel="nofollow" href="http://www.billbuxton.com/multitouchOverview.html">Multi-Touch Systems that I Have Known and Loved</a></li>
</ul>
<div class="li">
<h3><span style="font-weight: normal;">Interactive Demo</span></h3>
<div class="level3">
<p>These are some quick demonstrations of the potential of ponds when used in conjunction with “processing” and simple particle physics modelling</p>
<p><object width="425" height="344" data="http://www.youtube.com/v/S9Z2S4eefgo&amp;hl=en&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/S9Z2S4eefgo&amp;hl=en&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
<h3><span style="font-weight: normal;">Watch This</span></h3>
<p><span style="font-weight: normal;">This table has been used by clients such as Yahoo and Acura &#8211; it’s an experiment that is available for everyone from art schools to the Fortune 500.</span></p>
<p><object width="425" height="344" data="http://www.youtube.com/v/HgSg_STtPAA&amp;hl=en&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/HgSg_STtPAA&amp;hl=en&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
<h3><span style="font-weight: normal;">Design for Multi-Touch</span></h3>
<div class="level5">
<ol>
<li class="level1">
<div class="li"><a class="wikilink1" title="multi-touch:download" href="http://labs.moto.com/touch-table-simulator-download/">Go to the Multi-Touch Simulator</a> page to learn more.</div>
</li>
<li class="level1">
<div class="li">Or simply <a class="media mediafile mf_zip" title="multi-touch:motomultitouchsimulator.zip" href="http://labs.moto.com/wp-content/uploads/2009/02/motomultitouchsimulator.zip">Download the simulator</a> (requires Java v1.5).</div>
</li>
<li class="level1">
<div class="li">Write your own content in Processing, Flash or the environment of your choice.</div>
</li>
<li class="level1">
<div class="li">Send it to us. We’ll record it in action and put it up for all to see.</div>
</li>
</ol>
</div>
<h3><span style="font-weight: normal;">Links</span></h3>
<ul>
<li><span style="font-weight: normal; ">Acura - <a class="urlextern" title="http://interactiveoracles.com" rel="nofollow" href="http://interactiveoracles.com/">Interactive Oracles</a></span></li>
<li>Press Coverage - <a class="urlextern" title="http://www.designinteract.com/features/" rel="nofollow" href="http://www.designinteract.com/features/">Design Interact</a></li>
<li>Got an idea? <a class="wikilink1" title="about:contact" href="/contact-labs/">Propose a collaboration.</a></li>
</ul>
<h3><span style="font-weight: normal;">Credits</span></h3>
<ul>
<li>Jeffrey Traer Bernstein</li>
<li>Eddie Elliot</li>
<li>Daniell Hebert</li>
<li>Sasha Soyfertis</li>
<li>Chris Verplaetse</li>
</ul>
</div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://labs.moto.com/multi-touch-table/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Sensing Screen</title>
		<link>http://labs.moto.com/sensing-screen/</link>
		<comments>http://labs.moto.com/sensing-screen/#comments</comments>
		<pubDate>Tue, 22 May 2007 14:26:50 +0000</pubDate>
		<dc:creator>sabrina</dc:creator>
				<category><![CDATA[Multi Touch Sensing]]></category>
		<category><![CDATA[moto]]></category>
		<category><![CDATA[multi touch]]></category>
		<category><![CDATA[no touch interface]]></category>

		<guid isPermaLink="false">http://97.65.119.20/?p=1</guid>
		<description><![CDATA[A new type of interface that can sense and identify objects without touching the screen, and allows multiple simultaneous interactions with on-screen graphics. This innovation has many applications.


no physical contact needed to trigger
advanced multi-touch processing
lightweight flexible sensor matrix works on flat and curved surfaces
scales from small to wall-sized
can be deployed outdoors behind durable surfaces
RFID capability [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-weight: normal;">A new type of interface that can sense and identify objects without touching the screen, and allows multiple simultaneous interactions with on-screen graphics. This innovation has many applications.</span></p>
<div class="level1">
<ul>
<li>no physical contact needed to trigger</li>
<li>advanced multi-touch processing</li>
<li>lightweight flexible sensor matrix works on flat and curved surfaces</li>
<li>scales from small to wall-sized</li>
<li>can be deployed outdoors behind durable surfaces</li>
<li>RFID capability senses objects identity and position on surface</li>
<li>no cameras or tricky lighting calibration required</li>
</ul>
<p>For more information on this type of interface, please explore <a class="urlextern" title="http://www.sonycsl.co.jp/person/rekimoto/smartskin/" rel="nofollow" href="http://www.sonycsl.co.jp/person/rekimoto/smartskin/">Smart Skin</a> by Jun Rekimoto of Sony</p>
<p>Got an idea? <a title="marketing@moto.com" href="mailto:collaborate@labs.moto.com">Propose a collaboration.</a></div>
<p><object width="425" height="344" data="http://www.youtube.com/v/HWGhgLcLIqI&amp;hl=en&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/HWGhgLcLIqI&amp;hl=en&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
]]></content:encoded>
			<wfw:commentRss>http://labs.moto.com/sensing-screen/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
