"Poor responsiveness"? Yes, that's on my list. 2011, and 2009 back when my 3GS made every Android phone on the market look like it was running through treacle.
The gap has narrowed, but it's still embarrassing that so much computing power has been thrown at this, but still it feels like Android just can't keep up with my finger movements. Coming from iOS, this is a really big UX issue. List and scroll views on iOS feel like they're glued to your fingers. On android they don't, and it makes the whole UI feel 'slippery' - like you don't have a decent grip on UI objects.
No crashing No virus/malware/spyware Less Crappy apps Better user interface Better battery life
Boston fans used to complain about their streak of 80+ years without a World Series win, but of course that's all over now. The Cubs, meanwhile, have passed the century mark: since they didn't even make the playoffs this year, the streak stands at 103 years, with the last win in 1908.
Thirty years into my personal fandom, I've grown accustomed to shrugging and saying "there's always next year" because, well, there is. Of course, "next year" never really happens; even when they get so close there's always something, like Game 6 of the 2003 NLDS when the wheels just completely came off in the space of about an inning.
But then, "next year" probably isn't going to materialize soon anyway. The Cubs have spent too many years in a row now chasing over-the-hill ex-stars, giving them huge contracts and then living with the results. The farm system's a mess and there's no cohesiveness to the team or the organization, and won't be for a good long while.
Which is why a lot of people probably think it's crazy to keep betting on "next year", when what's really needed is a massive overhaul and then four or five years of rebuilding effort. They probably think it's crazy, too, to just pretend there aren't systemic problems in the organization, to talk about how this year's problems were different from last year's problems, to act as if bringing in a couple big-name hired guns and slapping some lipstick on the pig will lead to winning it all, and soon.
But I've been watching the Cubs for three decades now, and I'm a devout member of the Church of Next Year. I'm a fan, and I'll always be a fan, and even if there isn't a championship in the cards I can be proud of the fact that at least Wrigley Field will always be packed, which is something you can't say for a lot of teams that actually win (heck, Tampa Bay fans didn't even turn out to watch their team mount an epic September comeback and make the playoffs on the very last day of the season). And, of course, a stadium full of seats is probably worth a lot more to the owners than a championship, right?
Android is free to license, and the OEMs are benefactors of an incredibly wealthy company that seems to have no qualms about throwing gajillions of dollars into R&D to make a best-in-class mobile OS.
Android not being "good software" cannot be in any way spun as a win for the proletariat - because there is no opportunity cost. The cost to engineer the OS is in no way passed on to the consumer, and so far only the hardware is (with some marginal amount of software integration).
In other words, Google is pouring hundreds of millions to develop Android. The average phone consumer (in any part of the world) is not paying for its development (customers of other Google products are), so the argument that somehow these "cut corners" has resulted in a more affordable product is a complete non-sequitor.
> "This allows people with probably no other way to access the internet to be able to have the same luxuries through there phone."
And that is an excuse for poor engineering... how? Your point is that, if Google didn't "cut these corners", this free product may very well not exist, and thus unable to provide these benefits to the developing world at low cost.
Which is, again, a non-sequitor, since there is no evidence whatsoever that Google treats Android like an exercise in budget engineering for the developing world. They are banking practically the whole company on it, and throwing top talent at Android, with a seemingly bottomless budget.
Suffice it to say, if Google spent some more time optimizing and improving UI responsiveness, the developing world will not suffer, and in fact will get a better product for the same price they're currently paying: $0.
This is the same stupid argument that people used with Nokia years ago, before (surprise!) Android came in and ate their lunch. Those budget candy bar phones sure did bring mobile telephony to the masses, and any attempt at critiquing the phones' hardware or software was rebuked with claims of "well if it was better it wouldn't be affordable you elitist".
And of course, then Google came in with Android and now we have touchscreen smartphones in the developing world. And people continue to jump on criticism of Android with the same lame-duck excuse.
If it doesn't, that'd be supremely disappointing, since it's truly one of the things that has been plaguing Android since it first launched.
> "Android supports just about all possible hardware configurations from low end to high end."
All the more reason the UI stack needs to be optimized from end to end. Apple can pretty much just assume you have a 800MHz dual-core under the hood, Google cannot. It's taken some serious firepower to get Android's UI to be suitably responsive (we're talking dual-core, 1+ GHz beasts)... what hope does the developing world have trying to run that kind of software on little 400MHz ARM chips?
We know from the development of OSX (or iOS, depending on where you want to look) that even a minimal amount of hardware acceleration from low-end GPUs can do wonders for overall UI performance. A reasonably low-end GPU will lay waste to a large number of problems that even mid-high-end CPUs are poorly equipped to solve.
If anything, if Google wants to make a difference in the developing world this needs to be a top priority - after all, this is the market that is least able to brute force their way past performance problems with raw hardware.
> "As the parent comment was pointing out, people are willing to pay for the luxury of animations, or polish. For most people just getting calls, text, email and mobile web, at affordable prices is all we really want."
I think it's short-sighted to call responsive, rich UI a "luxury". Before Android phones hit the developing world, the status quo was candy bar phones. I'm sure there were enough people back then proclaiming they couldn't imagine needing anything more - it places calls and gets texts, what else could someone reasonably wish for?
But then Android brought smartphones to these parts of the world and the goalpost moved. Now expecting mobile web and email on your phone is entirely reasonable, thanks to what used to be the sole territory of luxury devices. Software is something that has literally no marginal cost - once produced, it can be shipped on ten million phones for negligible cost, and in this sense is pretty much the cheapest way you can improve your products. IMO saying that good UI is exclusively the territory of luxury devices is doing a great disservice to the developing world.
Google ought to be doing better, considering the sheer force they have thrown behind Android, and if these long-awaited hardware acceleration features fail to significantly tame the UI performance beast, it is in every way appropriate to call them to task on it.