| [Unreasonable expectations and little knowledge or inclination to try things out] Please don't read the previous bracketed sentence as snarky or insulting - it reflects the fact that he bought an unlocked phone and expected it to work great out of box with T-Mobile (including WiFi calling!) and he wasn't inclined to search the Play Store for TMobile Voicemail - so there is definitely substance to that sentence. But I merely wanted to point out that he is a user who is perfect fit for iOS/iPhone design goals. And not all people fall into that bucket. And neither should simplicity at all costs be a universal design goal for every product. Obviously if he is inflexibly tuned to the iOS way of doing things it's no wonder he's going to have issues with anything else. 1) Two Apps / Choosing Apps - This is why many people prefer Android over iOS. If you are bugged by it - select the one you like and choose "Always" the next time. Done. (If you are a UI designer at least shed some light on what is the way to do a better UX on this feature - simply saying you don't know which one to pick is not really adding any value. You have to try Hangouts, Gallery, Photos and then choose them as "Always" - that's the idea and I find it as intuitive as it can be.) 2) Hardware differentiation - yeah just install a launcher once and be done with it - oh you will have to choose the default once after you install it, but yeah after that it's even easier. Oh and Google autocompletes HTC disable blinkfeed - first result tells you how in two steps. 3) Fine print of an unlocked Android phone - he is troubled because WiFi calling isn't available on _all_ Android phones whether or not the carrier is T-Mobile - and if it was there he would be sure to complain about what's that WiFi calling thing that I don't understand on my Verizon HTC One. Hardly a UI problem and since it requires special firmware support it's hardly fair to have everyone put it in. 4) Unlocking - it's a HTC thing. Stock Android and even Samsung phones just swipe and unlock - plus you can thank slide to unlock patent for some of the differentiation there. 5) Back button - as much as inconsistent it is, having it still beats not having it altogether. But yes it can be a little annoying at times. 6) Navigation bar - he complains about there being differences in Samsung and HTC phones! I can't figure out why that is relevant as his target audience generally will stick to one phone. 7) He even complains about the Notification bar! (For crying out loud everyone pretty much copies this from Android - including iOS!) "I clear my notifications periodically, but inevitably a pile of tiny incomprehensible turds appear at the top of my screen, uglifying it to no end." Ugh, what? Does iOS magically know which ones you like and shows only those? 8) Copy/Paste - this is one point I agree with him on. It just isn't as elegant as iOS and neither is it consistent. But I stopped reading past that - too much personal preference stuff rather than valid points and being on a "User Experience Designer"'s blog I thought there would be insights on doing this right - I only saw "iOS is right" in some places. |
1) It's fair to let people choose a different app (I know many people really want this on iOS), but I think his complaint is valid. There are many situations where it's completely unclear to a new user why they should use app X over Y for photo management/SMS/etc. To ask them before they've even used the app the first time nearly ensures they're not ready to make that decision. Sensible defaults and perhaps delaying the prompting until the device notices the user uses an alternate app a couple of times may be a better way to handle this.
3) Why should it matter if my HTC One came from a T-Mobile store or not? The fact that they behave differently (and especially that T-Mobile's support isn't prepared for that) is clearly an issue. I think the voicemail note is telling. How many people, upon buying a new phone, would think "I need to go download a special app to get my voicemail working"?
4) HTC took something that worked fine and made it more confusing. That's clearly a design mistake.
5) If something doesn't work reliably, that's a design issue. Especially if it used to work.
> But I stopped reading past that [...] I only saw "iOS is right" in some places.
That's not what I saw. Rorschach test for your preference for Android/iOS perhaps?