Sticking to the discussion, the simple answer is iOS is smoother because it uses the GPU to render the UI. Android, on the other hand, mostly uses the CPU. IMHO Android will soon lose a large percentage of their customers as more people become aware of this issue. Consumers don't care about the cause, they just want something that delivers a UI user experience on par with the market leader (there's a good reason why they're the market leader). The fact that Google have managed to con millions into buying in to the Android hype falls nothing short of astonishing. The Nexus S campaign in a perfect example: rarely (if ever) show the handsets scrolling a web page or menus.
Android is a great platform, but the benefits of Android are negated by the sluggish choppy UI that completely destroys the user experience. Do a Google search for "Android Issue 6914" and you'll get the idea.
Here's a simple test: go to the Engadget desktop (classic) page and scroll/zoom around. Make sure flash add-on is disabled.
The best improvement in this area I have personally seen to date is Android 2.2.1 running on a Galaxy S. It's not perfect, but it's definitely a step in the right direction. I admire Samsung for listening to consumers and at least making an effort (not easy considering this issue is the result of an Android architectural design flaw).
It looks like Google have addressed this issue with Honeycomb, but it also looks like Honeycomb is exclusively for tablets. Hopefully this fix will trickle down into Android handsets. I've been eagerly awaiting a fix each and every update, but each time am left feeling disappointed. Until Google addresses this issue, they've lost a customer here.
Android is a great platform, but the benefits of Android are negated by the sluggish choppy UI that completely destroys the user experience. Do a Google search for "Android Issue 6914" and you'll get the idea.
Here's a simple test: go to the Engadget desktop (classic) page and scroll/zoom around. Make sure flash add-on is disabled.
The best improvement in this area I have personally seen to date is Android 2.2.1 running on a Galaxy S. It's not perfect, but it's definitely a step in the right direction. I admire Samsung for listening to consumers and at least making an effort (not easy considering this issue is the result of an Android architectural design flaw).
It looks like Google have addressed this issue with Honeycomb, but it also looks like Honeycomb is exclusively for tablets. Hopefully this fix will trickle down into Android handsets. I've been eagerly awaiting a fix each and every update, but each time am left feeling disappointed. Until Google addresses this issue, they've lost a customer here.
Last edited: