I'll give you that. But until they take the layer of frosting off the top (Java)---it'll take more powerful hardware, more RAM, faster GPU and storage JUST to achieve parity with iOS and it's 'smooth-ness'.
Any data to back this up? How do Android Apps which utilise the NDK fit into this little theory of yours?
Given that stock Android is *much* smaller than iOS in terms of required storage, how does storage figure into this?
Can you provide me some information with regards to some of the "tricks" that iOS uses to achieve this smoothness? Compare this to some of the same sorts of things Google has been doing with Android has been doing in the last year?
Would you care to comment on my opinion - From the start Apple concentrated a large amount of resources into "superficial" aspects of iOS such as this fluidity you mention at the expense of depth of features. Google has done the opposite with Android, they initially placed all their emphasis on reaching (and then significantly exceeding) the feature set of iOS and only in the last 12-18 months or so have been concentrating on UX.
Considering you're speaking with all the authority (albeit without any hard facts backing you up) of someone who is an expert (maybe developer) i'm pretty sure you'll have no problems providing specific answers backed up by sourced data.
(hint: I can provide you with a pretty detailed run-down on all of the above questions I've asked).
----------
Apparently you just don't 'get it'. Apple releases features when they're ready for prime time. When they DON'T slow down your user experience.
Really? I can go digging for many many threads in this forum about how the initial releases of both iOS 4 and 5 bogged down on anything but the absolute latest iPhone.
Did you ever use OS X 10.0 or 10.1? I did and I felt like a beta tester.
Apple is as much a victim of software regression as any other vendor. Perhaps you need to remove those Apple coloured glasses!