2 ms·
I do support/sysadmin work for companies and executives. Android phones, on the whole, lack polish, and often have unexpected behavior. For example, just yest
by zdw 16y ago
I do support/sysadmin work for companies and executives.
Android phones, on the whole, lack polish, and often have unexpected behavior.
For example, just yesterday I had a non-technical customer who got a Droid X, with 2.2. Had battery life issues with the phone, and frankly didn't want/need to learn about task management (understandable - do you make the company CEO look at your server's process tables for zombies/runaways?). Plus, the phone had linked a bunch of unrelated contacts between his Exchange and Google accounts, so his contact came up linked to his wife's hairdresser, for whatever reason. That's about par for the course with Android phones.
My take on Android is "great if you're technologically competent and able to deal with issues that come up, not so great otherwise". None of these people are going to run custom ROMs, or take the time/know how to get the crapware off their phones. They're going to be left behind on old versions of the OS as soon as the vendor drops support.
None of these (apart from the unusual contact linkage) are technical objections about Android per say - I have a good friend with a Droid X and he's customized the heck out of it - it looks/works great and has great battery life. He also knows what he's doing. Most people aren't him.
I don't see a good solution to this that would survive carrier intervention...
- krschultz 16y agoAnd how does that differ from Windows Mobile? I helped a person running Windows Mobile 6.5 with battery issues. Turned out he kept opening applications and not closing them. The exact same problem, but on a different system. Now I'd argue Windows Mobile is crap, but this kind of stuff is par for the course. And it really has nothing to do with fragmentation which is what this article (and thus this discussion) is about.