Shared publicly  - 
One thing that upsets me is that Apple blogs are using my post as evidence that Android will never, ever be as smooth as iOS. I don't think this is necessarily true. It may not be at the moment, but look at all the progress that's been made between Android 1.5 and 4.0 in a few short years.
Andrew Munn's profile photoCarter Gibson's profile photoMax Huijgen's profile photoErnest Marvin Esteban's profile photo
Never is a pretty definitive word.
+Andrew Munn awesome article dude! Glad to be following you! Keep up the awesome posts!
Ye gods Munn, you now have like.. 10X as many people following you as you're following. :P You're becoming a G+ Celebrity.
The new GN feels on par with the iPhone 4 to me. Will prioritizing UI rendering priority be as important in the future with the processing power? Can brute force win out over finesse?
You expected objectivity and journalistic integrity from a website named "cult of Mac?"
i actually dont mind that millisecond gap esp when i am running imp stuff in the background... try doing that in iPhone.. if its something "heavy" the overhead is just not acceptable..
Whatever lets Apple zealots feel comfortable with their "lead". Google and their partners sure aren't going to stop improving their OS no matter what they say. As long as they don't ignore the issue (Google seems to be aware of the issue) I'm good.
Tim Box
I'm so pleased you made that post, I hope it spurs the Android team on to perhaps bite the bullet and make the changes needed before its too late.
Because it is written by the view point of Apple, this is not an objective article. Most of the Android phones have better processor and ram capacity than iPhone's. So, nobody can feel difference between the smoothness of these two screens.
Andrew, maybe for two reasons: 1) your writing style was a bit gung-ho and might have encouraged it, maybe in retrospect you just didn't nuance the matter as you could have with your engineer's hat on, and 2) the mistakes that you did make (just one example, the idea that Android was not designed for touch interfaces when in fact a full touch prototype was shown off in 2007) played into a standard narrative.

No worries though, your post will be used for clickbait but the drama will soon blow over. You just ran into the risk you took for attempting to write an authoritative piece. Good luck with the internship at Microsoft!

(BTW are you planning to respond to the points that +Chi-Ho Kwok has raised in his post?)
The icloud service is so bad and so crappy..!!
As Stewie Griffin would say "Whatever makes you sleep at night...bitch"
Not much damage done. I'm a bit surprised to see people ripping him in the comments. It appears that the mindless daze that was iDevice fanboyism is coming to an end.
Personally, I don't think it necessary to defend or destroy either platform - competition is a vital driver of progress. For now, it's good that the Android UI has something to aim for, and good for Apple that Android is snapping at its heels. Long live the competition that improves the quality of my devices.
I think that brute force will require more resource (battery, cooling etc.) & finesse will improve the quality. I LOVE android over iOS anyday, but something about iOS too hard to ignore and smooth UI is one of them.
In future you may give people choice to run both old(current) and new(android having UI priority) like we have choices of 32bit and 64bit OS for our computers. Yes apps somehow should be compatible with both the versions and app developers can release apps for both of them. This can make transistion from old to new easier. I know its easy for me to comment here but implementation is totally different thing. Good luck to android team :)
+Phillip Hagger It only appears to be "mindless fanboyism" from the outside. Is there something wrong with preferring a quality device that feels good in your hand, feels good to use, just feels right over the "myeh myeh myeh locked in" chant that is the Android fanboy mantra. Yes, Apple users are locked in - locked in to quality and usability over well, I don't know what the attraction is with Android myself, screen size perhaps?
Love my iOS devices. Glad that Google is doing some great stuff with Android ... keep up the good work.
I still prefer Android devices - high end ones, of course. You can't really feel the UI smoothness differences b/t Android and iOS. I don't like Apple because they are like another Microsoft that keeps things so secretive.
This post actually contradicts your longer post +Andrew Munn If you point out that large progress has been made from earlier Androids to 4.0 you ignore that you pointed at what you call a major flaw in the Android frame work. It´s one of two. Either Android can make progress with the same frame work or it can´t as you earlier stated.
It´s a design philosophy which you keep responsible for inherent lag while I´m quite sure this is not the case. Badly written applications, lack of optimizing tools, lack of a high enough standard to be allowed into the Android market, applications which were clearly intended for the last generation running on older hardware etc. Lots of reasons, but an inherent fundamental flaw couldn´t have been solved by moving from 1.5 to 4.0.
What happened in that period is that hardware got enormously faster. That in itself will have been responsible for a much faster experience. Plus the enormous professionalizing of app developers on the Android platform. The inherent design flaw (your words, i don´t agree) is still there.
+Max Huijgen it's not a contradiction. I still think Android has a design flaw, but I'm confident it will be fixed by a revised framework over time. Android had many other design flaws that were fixed between 1.5 and 4.0. Those include:

-Hardware buttons are gone in 4.0 (although the back-button stack is still a huge mess)
- Hardware Acceleration in 3.0
- Removal of the 'menu' button in 3.0. (This required a backwards compatibility layer)
-The terribly slow gallery app is replaced in 3.0
- Concurrent GC in 2.3
- JIT compilation in 2.2
- NDK added in 2.0 (?)
- The Android Market has gone through 3 complete redesigns
- The terrible music experience got an overhaul

I'm confident that Google will get the lag issue fixed eventually. Maybe it will require a new framework. Maybe not. I'm not qualified to say that.
A design flaw is not the same thing as having not reached a point on the roadmap. For imstance not implementing JIT compilation until you are ready to do so wouldnt be the same as thinking interpreted code is fast enough and designing yourself into a corner where you cant implement it.

And an opinion against hardware buttons does not make them a design flaw. Many people like the true physical buttons. So they are enjoying a flaw?

The further this goes the more it looks like a publicity stunt.
+Ian Turner No there's nothing wrong with preferring a device where form follows function and emphasis is placed on giving you something for your money over parlor tricks to make it "feel" right. Instead it just IS right. If you have iOS 5 by any chance then you now know what some of the attraction was for Android 1.5.
Reread your own long post and then check your comment here +Andrew Munn You talk in no uncertain ways of a major flaw in the Android framework. Supposing that will not be fixed as Google will not offer backward compatibility or dual mode support this according to your contribution will forever stand in the way.
I don´t agree, nor do the people of Nvidia, eperienced developers on both platforms, veterans like me who wrote lighting fast UI on pre-windows machines where they scheduled their own code, and the Android coders themselves, but it´s your main argument.
So clearly then this post contradicts. You have a technical background, surely you can see you can´t have both according to your own logic
let them be. I know the future is bright for Android. I remember using a 1.6 android. And now I am using 4.0. The changes and the improvement is like 20-40x. Android will continue to be succesful and will bring more innovations and performance improvements.
thanks for your post Andrew, super useful.
Isn't this the issue that ICS has fixed?
+Carter Gibson according to Andrew it´s a fundamental flaw so no that´s not fixed in ICS. Other people like myself have a completely different view on the technical mechanisms. As they usually have a hard core solid background in either Android or computer graphics in general this will explain +Chang Xiao and many others comments.
ICS actually fixed quite a number of the reasons Android can be laggy under certain circumstances but that´s a technical debate while +Andrew Munn posted a ´Engadget´ kind of story.
I can't believe that an intern's post was quoted countless times in Apple blogs and they made it sound like it was "FACT" or 100% true. lol. kinda funny really.
Add a comment...