Live data from Hacker News

A User Experience Designer Switches from iOS to Android

jacksonfish.com

11–20 of 68 posts

Re: A User Experience Designer Switches from iOS to Android

#11
post #8
post #7

Almost all of this guys problems are the result of giving the user options that simply don't exist in iOS. If you really need your OS to tell you how YOU want to do things then I guess you really should go back to the locked down iOS. Choices are hard. Apparently even choosing what phone was too hard.

I often see the same argument made in defense of desktop Linux vs. Windows and OS X. It's a little more justifiable there, I suppose, but a phone is an appliance. Its job is to do the things I need it to do, to do those things well without fail. Otherwise, it's worse than useless, because it complicates my life rather than simplifying it. Sure, as has been pointed out elsewhere, the iOS user interface is far from per…

A phone is a computer and a user should be able to configure it however they want. If that isn't for you then don't use it, but that doesn't make customization an inherent flaw because someone doesn't personally want to deal with it.

Re: A User Experience Designer Switches from iOS to Android

#12
[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.

Re: A User Experience Designer Switches from iOS to Android

#13
post #7

Almost all of this guys problems are the result of giving the user options that simply don't exist in iOS. If you really need your OS to tell you how YOU want to do things then I guess you really should go back to the locked down iOS. Choices are hard. Apparently even choosing what phone was too hard.

Giving people a choice isn't always better. The photos app is a perfect example. It's fine that Android lets you have/use multiple photo apps. Many people think that's better than iOS.

But should the phone ship in a configuration that causes users to make a choice they're often unprepared for every time they want to deal with an image?

Part of design is making decisions. Some of these problems seem to exist because the designers (or the OEM who is fiddling with things) can't make a reasonable default decision and is forcing it on the user instead.

Re: A User Experience Designer Switches from iOS to Android

#14
post #5
post #4

The two-apps/choose-your-app problems are something that my mother has found very frustrating, and I haven't really been able to come up with a good solution for her. It bothers me as well, but I have enough experience with similar things to be able to deal with it. But for her, it's a bunch of new stuff that all conflicts and interoperates differently. It's a disaster.

Yup. I just cycle through the choices trying a different one each time. Once I find myself using one _all the time_ I set that as the default. I think a great solution for this would be to let power users distribute their own versions. That way, you could just find a designer you trust and install their version. It's still fragmented but at least you could go with people like the author who have thought through it ra…

It's still fragmented but at least you could go with people like the author who have thought through it rather than an awful corporate designed by committee mess.

Some people would argue that's what Apple is doing with iOS. Not that I agree (I'd never trust Apple, and I don't think their offerings are superior in any way, shape or form), but there are those who believe it.

Re: A User Experience Designer Switches from iOS to Android

#15

[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…

He completely missed the entire point of Intents which isn't surprising since he's not experienced in Android (better said, he's just an iOS guy).

Re: A User Experience Designer Switches from iOS to Android

#16

I keep finding myself agreeing with the author whenever an encounter with the back button is mentioned. One of my favourite things about an old HTC phone I had running a 2.x version of Android was that the back button worked very consistently everywhere. It made using the native apps feel like navigating around websites: just what you'd expect from Google. On literally every Android device I've tried to use since the…

What's interesting is that other people have commented on the back button; see http://blog.codinghorror.com/the-one-button-mystique/ which I also find highly amusing for its link to the state diagram of what the one button does - simplicity? I think not!

Re: A User Experience Designer Switches from iOS to Android

#17
post #4

The two-apps/choose-your-app problems are something that my mother has found very frustrating, and I haven't really been able to come up with a good solution for her. It bothers me as well, but I have enough experience with similar things to be able to deal with it. But for her, it's a bunch of new stuff that all conflicts and interoperates differently. It's a disaster.

This part is funny, app interoperability is a huge feature. Some people should just stay on iOS I guess. I love that I can click a link and have various ways of understanding or consuming it. I guess there needs to be some tweaking around how and when it saves preferences for these intents, but personally this is a big part of the reason I'm on Android.

Re: A User Experience Designer Switches from iOS to Android

#18
post #6

There are some definite valid criticisms here (Photos/Gallery being the least understandable oversight), but you really need to try the Nexus 5. Fragmentation needs to be dealt with and OEM's need to stop "differentiating" themselves into UI hell, but pure Android is definitely worth experiencing. It will mainly make you more upset at HTC.

Yep. What's funny about HTC in particular is some of their additional features such as disabling apps and hiding them from the launcher, even if they're uninstallable, exist purely to work around some of the crap they've burdened the system with.

I've worked with Android for basically the whole time it's been around, and in that time never saw a single manufacturer led user interface change that represented an improvement. Supposedly the Chinese ones do, but I've never had the chance.

This isn't to say stock is perfect, but people underestimate just how much the OEMs have messed with in their efforts for software differentiation absolutely no one really wants.

Re: A User Experience Designer Switches from iOS to Android

#20
post #13
post #7

Almost all of this guys problems are the result of giving the user options that simply don't exist in iOS. If you really need your OS to tell you how YOU want to do things then I guess you really should go back to the locked down iOS. Choices are hard. Apparently even choosing what phone was too hard.

Giving people a choice isn't always better. The photos app is a perfect example. It's fine that Android lets you have/use multiple photo apps. Many people think that's better than iOS. But should the phone ship in a configuration that causes users to make a choice they're often unprepared for every time they want to deal with an image? Part of design is making decisions. Some of these problems seem to exist because t…

Again, you've missed the point. If you want a monolithic experience in the One True Way, that appears to be the iOS main feature. The photos app is NOT the perfect example because there's plenty times I want a full gallery since I'll want to share something else and sometimes when I want just a preview. eReaders are also great examples for when you need choices.

If the user is afraid of clicking one icon vs another when presented with the initial decision, I don't know what to say. It's literally explained as you use it.

Post reply on HN