I'm not finding anything really wrong with the Jelly Bean build I have. Its fast, it works its very fluid its automagic on many things. Some of the things he points out as problems... aren't exactly the same in my build of Jelly Bean, specifically the Calculator isn't like he shows. Things like the ICONS, yeah aren't grand, but its not really noticeable to the user... it looks just fine IMO. It bugs interface designers.
Sure, there are apps that just don't look right or are screwed up, but those aren't typically Google or Android Core Apps or even apps that are popular.
I'm sure the best thing they could do at this point is to vet apps in the market and make the developers do a better "first shot" rather than shoot and go, shoot and go, shoot and go...
For example:
I use an app, I like it a lot called "aNag"... dude, some of the *Multiple Multipe* recent fixes are just plain dumb mistakes. Like leaving out options needed to be able to check an instance... if they were configured before that new version... it worked, but if you had to make a new one... no can do, nor could you disable the existing one.
Slow down, check you schtuff... test, test, reset (aka clear or Factory reset), test. I know malraux, the sheer number of devices, but dang the errors I've seen in this one app, lead me to believe much of the angst people are experiencing is due to lack of QA and testing and then a good vetting and well, real world programming experience.
Whatever.