By 
This behind-the-scenes tidbit by Googler François Beaufort may not be useful for the common user to do anything practical, but it’s interesting nonetheless. Google apparently uses an automated robot to test latency in Chrome OS and Android.
The robot’s job is to simply provide consistent strokes of input so Google can get an accurate reading on how fast the device responds to your touch. They do so using Touchbot, a web-based latency test engine that provides common touch and scroll scenarios.
In fact, the latency engine they use is completely open sourced and has been publicly implemented for you to try on your Android device by clicking right here. The results obviously aren’t great — the team knows they still have a lot of work to do to eliminate lag in Google Chrome — but it’s nice to know that they treat it seriously enough to use something like a robot for testing procedures. Take a look at the quick video of it in action above.
[via Google+]
I hope they focus not only on chrome, but everything. It’s clear when you touch an android phone and then go to a windows or an ios device how much snappier it feels just based on response time.
Touch response seems a little slower in Android because most Android apps don’t use splash screens to masks loading times. The YouTube app is notorious for this. Every time you tap on it, it recognizes your touch but takes a couple of seconds to open. Even when it’s in memory it opens slower than what I would like.
That’s delusional fanboy thinking
We aren’t even talking about app loading times, we are talking about human interface input latency.
Damn. The perceived latency didn’t even phase me, until I read this. I should have taken the blue pill.
the song “the heat is on” should be played during the duration of that video.
Too bad it still sucks on Android