They're engineering fixes, but the complaints are due to UX, and UX guys wouldn't have let those problems leave the lab. The lack of GPU usage is an engineerin

They're engineering fixes, but the complaints are due to UX, and UX guys wouldn't have let those problems leave the lab. The lack of GPU usage is an engineering and time restriction: Android is available on many devices, not all of which have GPUs supporting two surfaces at once. Android made a completely reasonable compromise of not using the GPU for the surface which in practice works perfectly fine. With enough time and engineering effort they could, and should, create divergent codepaths for higher-end and lower-end devices, which is exactly what they are doing with Honeycomb. I have no doubt they'll resolve it as the platform matures and the hardware base improves. It just isn't as important of an issue as many seem to believe it is: Again, I use Android as my primary smartphone device. Minor interface stuttering just isn't a big issue, or any issue at all for that matter. What I did have a problem with was games that, due to GC pauses, stuttered (a problem that kills it as a gaming platform pre-2.3). That has been largely resolved in 2.3 with the concurrent GC (which also improves the base UI).