<?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; Nexus One</title>
	<atom:link href="http://labs.moto.com/tag/nexus-one/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>DIY Touchscreen Analysis</title>
		<link>http://labs.moto.com/diy-touchscreen-analysis/</link>
		<comments>http://labs.moto.com/diy-touchscreen-analysis/#comments</comments>
		<pubDate>Fri, 08 Jan 2010 17:41:02 +0000</pubDate>
		<dc:creator>sabrina</dc:creator>
				<category><![CDATA[Multi Touch Sensing]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[capacitive]]></category>
		<category><![CDATA[Droid]]></category>
		<category><![CDATA[Eris]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[labs]]></category>
		<category><![CDATA[moto]]></category>
		<category><![CDATA[MOTO Development]]></category>
		<category><![CDATA[multi touch]]></category>
		<category><![CDATA[multitouch]]></category>
		<category><![CDATA[Nexus One]]></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=1146</guid>
		<description><![CDATA[
The success of the iPhone has triggered the adoption of touchscreen systems in a wide range of mobile devices, and a bevy of new gadgets equipped with capacitive sensing technology have now hit the market.  MOTO has years of experience developing products that use capacitive touch, and we&#8217;ve had the opportunity to test many of [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://labs.moto.com/wp-content/uploads/2010/01/touch-screen-test-header2.jpg"><img class="alignnone size-full wp-image-1127" title="touch-screen-test-header2" src="http://labs.moto.com/wp-content/uploads/2010/01/touch-screen-test-header2.jpg" alt="touch-screen-test-header2" width="692" height="277" /></a></p>
<p>The success of the iPhone has triggered the adoption of touchscreen systems in a wide range of mobile devices, and a bevy of new gadgets equipped with <a href="http://en.wikipedia.org/wiki/Capacitive_sensing">capacitive sensing</a> technology have now hit the market.  MOTO has years of experience developing products that use capacitive touch, and we&#8217;ve had the opportunity to test many of the latest devices. Our conclusion: All touchscreens are not created equal.</p>
<p>It takes finesse to create a touchscreen system that&#8217;s pleasant to use, because touchscreens require seamless integration between hardware components, software algorithms, and user-interface design. If a manufacturer cuts corners or flubs any of the critical elements, the user&#8217;s experience with a touchscreen product is likely to suffer.</p>
<h3>Simple and True</h3>
<p>Although we usually use sophisticated tools to test touch screen accuracy, MOTO has also developed a simple technique anyone can use to evaluate the resolution and accuracy of a touchscreen device. All you need is a basic drawing program (download one if necessary), a steady hand, and a few straight lines drawn very slowly on the screen.</p>
<p>This video shows what happened when we recently took several touchscreen systems out for a test drive:</p>
<p><object width="640" height="480" data="http://vimeo.com/moogaloop.swf?clip_id=8569827&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=FF7700&amp;fullscreen=1" type="application/x-shockwave-flash"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://vimeo.com/moogaloop.swf?clip_id=8569827&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=FF7700&amp;fullscreen=1" /></object></p>
<h3>The Virtue of Slow</h3>
<p>Why do you need to draw slowly?  On a good touchscreen, users can draw clean straight lines, even while going very slowly, so the graphics that appear on screen accurately represent what was physically drawn.</p>
<p>On inferior touchscreens, it&#8217;s basically impossible to draw straight lines. Instead, the lines look jagged or zig-zag, no matter how slowly you go, because the sensor size is too big, the touch-sampling rate is too low, and/or the algorithms that convert gestures into images are too non-linear to faithfully represent user inputs.</p>
<h3>Pressure Matters</h3>
<p>Also, even on a single device, the amount of pressure and the part of the finger you use on the screen has an impact on how well it senses. A good touchscreen device will produce linear output regardless of whether you&#8217;re using the full pad of your finger, or just the dry corner of your cuticle.  When comparing devices, make sure to use even pressure across all of them.</p>
<p>If you want to show the most extreme case, draw very lightly with the corner of your finger. The artifacts will increase significantly, showing which device is really the best with a weak signal. This is important because quick keyboard use and light flicks on the screen really push the limits of the touch panel&#8217;s ability to sense.</p>
<p>Here you can see the results of our test:</p>
<p><a href="http://labs.moto.com/wp-content/uploads/2010/01/diytouchscreenanalysis3.jpg"><img class="alignnone size-full wp-image-1147" title="diytouchscreenanalysis3" src="http://labs.moto.com/wp-content/uploads/2010/01/diytouchscreenanalysis3.jpg" alt="diytouchscreenanalysis3" width="728" height="802" /></a></p>
<h3>Edge Performance</h3>
<p>Take careful note of the performance at the edges of the screen. The performance at the edge is challenging to tune, and separate from the basic &#8220;waviness&#8221; test. The iPhone tracks all curve very strongly as you approach the edge of the screen, despite a straight finger trajectory. This is especially obvious at the bottom, where the iPhone has a sensitivity problem.</p>
<p>The <span style="text-decoration: line-through;">Droid Eris</span> [Nexus One] is actually the clear winner for edge performance &#8212; the signal tracks right off the edge of the screen very consistently.</p>
<p>[edit] As of time of first writing, we hadn&#8217;t tested the Nexus One.  It does slightly better than the Eris.  In fact, they both use the same touch controller IC.</p>
<h3>A Quest for High Signal-to-Noise Ratio</h3>
<p>To create a superior touchscreen experience, it&#8217;s essential to develop a touchscreen sensor that has the highest possible signal-to-noise ratio, or SNR. When a manufacturer gets it right, the device tracks touch inputs almost as if they were connected to physical objects in the real world. Get it wrong and consumers end up with inferior touchscreen systems that are inaccurate, insensitive, and absolutely infuriating to use for typing.</p>
<p>Key drivers of SNR include:</p>
<ul>
<li> Conductive sensor material</li>
<li> Substrate material</li>
<li> Substrate thickness</li>
<li>Distance from display (the biggest noise source)</li>
<li>Sensing waveform</li>
<li>Sensor pattern</li>
<li> Sensor pitch</li>
<li> Analog sensing circuitry</li>
<li> Sample rate</li>
</ul>
<p>Touchscreens are a catalyst for innovation and a powerful way for device manufacturers to differentiate their products in an intensely competitive marketplace. But as our demonstration shows, there&#8217;s a right way and a wrong way to deploy the technology. MOTO has worked with capacitive touch interfaces for more than 15 years, and here are some essential dos and don&#8217;ts for anyone entering the field:</p>
<ul>
<li> Don&#8217;t skimp on materials. With touchscreen hardware, manufacturers get what they pay for &#8212; and consumers will notice the difference.</li>
<li>Allow ample time to develop your algorithms. Don&#8217;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>
]]></content:encoded>
			<wfw:commentRss>http://labs.moto.com/diy-touchscreen-analysis/feed/</wfw:commentRss>
		<slash:comments>89</slash:comments>
		</item>
	</channel>
</rss>
