3 ms·
I'll tell you why I'm not an Android fanboy - the confusing UI and inconsistent hardware. Nothing made this more clear when I was trying to use my wife's Nexus
by timcederman 16y ago
I'll tell you why I'm not an Android fanboy - the confusing UI and inconsistent hardware.
Nothing made this more clear when I was trying to use my wife's Nexus One for turn-by-turn navigation in LA on the weekend. Hidden menus were very frustrating, and the clunky keyboard implementation meant I tried for voice recognition. Firstly, it sends voice recognition to Google (what! Voice recognition on the iPhone blows the Android experience out of the water due to this alone), but we need the navigation immediately (as we realised en-route we needed to stop somewhere else). Then the Android just hangs and gets stuck on some "please wait" screen.
I have never seen an iPhone get stuck randomly unless it's a hard crash. Then I needed to figure out how to 'reset' the map app -- another exercise in frustration. Ultimately it proved easier to use my iPhone and read the directions out myself. It basically sums up every experience I've had with Android - frought with frustration and unnecessary problems.
- timcederman 16y agoThe downvoting in this thread is interesting - it's not like the frustrations being aired are overly harsh or unfair. I think it's fine to air contrary viewpoints, surely.
- anatta 16y agoYou are most likely being downvoted for muddling the object(s) of your criticism. The Google navigation app runs on Android but so do other navigation apps. You've made a set error in your logic confusing the subset for the superset. A fair criticism would be to try different apps, weigh them out and present a measured response based on that analysis or specify that you're criticizing Google's app specifically and constraining the boundaries to that app and not the platform it runs on.