Skip to main content

Droid doesn't. Have touchscreen accuracy, that is...

Why does this matter to me? My fingers are a tad large so I need accuracy. I have never really had any issue with my iPhone. Anyone else?

Droid doesn't. Have touchscreen accuracy, that is...: "
Filed under: ,


Now there's a nicely-documented fact that you can throw back in the face of that annoying friend of yours who got a Verizon Droid and who keeps saying 'It's just like an iPhone!'



According to a report cited on AppleInsider this morning, the touchscreen accuracy of the iPhone is much better than that of three Android phones: the Motorola Droid pushed by Verizon, the HTC Droid Eris, and the new Google Nexus One. Why is that important? Well, when you're trying to tap a link on a website, for example, chances are very good that you're going to be successful on the iPhone and not on the the Android phones.



The tests, performed by MOTO Development Group (no relation to Motorola), measured touchscreen accuracy with a simple test. On each device, a drawing app was launched and a tester drew straight diagonal lines in both directions across the screens with a finger. iPhones showed straight lines in situations with both light and medium finger pressure, while the Android phones showed zig-zag wavy lines across the screen. MOTO stated:


'On inferior touchscreens, it'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. This is important because quick keyboard use and light flicks on the screen really push the limits of the touch panel's ability to sense.'

Several user comments on the MOTO site validate the findings. Have any TUAW readers been able to compare touchscreen accuracy on an iPhone and an Android device? Leave a comment below.



[via AppleInsider]
TUAWDroid doesn't. Have touchscreen accuracy, that is... originally appeared on The Unofficial Apple Weblog (TUAW) on Mon, 11 Jan 2010 13:00:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments"
Labels:

Comments

Post a Comment

Popular posts from this blog

Rumor Mill: New mac Mini Coming?

There are reports all over the Internet about a new Mac Mini to be possibly released at MacWorld.  TUAW is reporting that a new version of the Mini will include an optical drive that can be swapped for a second hard drive.  The housing will look much like the Time Capsule with a "lip" for consealing the optical dive slot and cooling. Whether true or not, I would like to see a few features in a new Mac Mini. More RAM (Of course.) NVIDIA chipset. FW port for external HD My main use for a Mini would be for media.  A Mini on my network using Front Row would be great for movies and TV.  (Sorry, Apple TV.)
3 comments
Read more

Calculate Age or Years Elapsed in an Apple Numbers Sheet

Often it is useful to show a person's age or years elapsed since a start date.  For example: Hire Date: 4/1/2012 - Years of service: 1.5 Here's a formula for Numbers that will do the trick: =IF(ISBLANK(cellReference),"",DATEDIF( cellReference ,TODAY(),"D")/365.2425) Replace the cellReference with the actual cell reference. i.e.: (A1)  So here's the breakdown: =IF(ISBLANK(cellReference),""  --- this checks to see if there is a start date in your referenced cell.  For example say your spreadsheet has a cell (A1) that holds a date of birth, but it is not yet referenced, this will result in an empty string. (Blank cell) Otherwise, it calculates the years:  DATEDIF( cellReference ,TODAY(),"D")/365.2425) DATEDIF compares two dates. The first date is your cell reference i.e.: (A1) The second is the current date according to your computer, iOS device: TODAY()  returning the Day -  "D" Then the difference is divi...
Post a Comment
Read more

Acid3 Test

I did an Acid3 test with a few browsers and these are the results I got.  For those unfamiliar, as I understand it, Acid3 is a test to see how compliant a browser is with current standards with the W3C . Browser # 1: Chrome by Google.  Running under Windows Vista Home on my Mac in VMWare. 79/100 Not bad for a new browser.  I'll be curious to see what the Mac version will do when it comes out. Browser #2: Firefox v.3.0.1 Mac OS X 10.5.4 71/100 Not as good as Chrome, but I have a PILE of extensions on Firefox. Browser #3: Safari 3.1.2 Mac OS X 10.5.4 75/100 Better than Firefox but still lower than Chrome. My take is overall they seem to perform about the same but I'll stick with Safari for now.  I use Firefox for much of my web browsing, but Safari is fast becoming a close second. Someday, maybe I'll test Opera too. Cheers!
2 comments
Read more