Live data from Hacker News

Confusing UI in iOS7

medium.com

111–120 of 192 posts

Re: Confusing UI in iOS7

#111
post #69

> I have no idea why the calendar is in German although the rest is in English I had the same issue (with a different language). I really hope it's a bug because it makes no sense. Here goes: In General > International, you can set "language" to english. So far so good. Then you can set "region format" for things like date and time formatting to use a sensible local format instead of e.g. the crazy US date format. Bu…

Not a bug, working as intended. German region format obviously also emtails German day and month names. That's really quite obvious.

> German region format obviously also emtails German day and month names. That's really quite obvious.

No it's not obvious at all and it's shouldn't be that way. If I set my language somewhere it should be applied everywhere. I want Monday as first day of the week, not Montag.

Other companies that seem incapable of getting language right: Microsoft and Google.

Re: Confusing UI in iOS7

#113
post #12

I'm actually surprised that there's so little visual consistency there... this stuff usually would be handled by reusable widgets - which, of course, gives you consistency for free. Still, people bag on Apple's design problems because Apple's stuff often feels almost perfect. I tried out a BB Q10 the other day and I couldn't even figure out how the heck you get to the home screen. I got stuck in the voice-search app…

In my UX design classes, we would use the phrase "You can't polish a turd" to describe this situation.

This is exactly backwards - all of the iOS 7 complaints I've heard so far have been about the UI polish and not the underlying functionality. Polishing a turd would be a beautiful UI in front of a buggy, slow system. Apple didn't ship a polished turd, they shipped a rough, unhewn diamond.

Re: Confusing UI in iOS7

#114

This kind of post annoys me. It's driven by the fact that the author has some theories about UI design, and wants to share them with us. There's nothing wrong with that. But this post pretends to be like a real usability audit, which it is not. > When I tap it, it turns red — but wait — it doesn’t give me the visual feedback. Did I break it? > The alarm is shown as a red filled square, so when I tap it, it should per…

>These comments are disingenous[sic]. You didn't get confused by these things.

What right do you claim in calling the OP a liar? Do you not think that he is capable of observing his own emotional reaction to UI independent of his intellectual understanding of it? Are you really claiming that he disliked the iOS UI because his theory told him to?

That is utter hogwash. No sane person goes out of their way to assign an explanation of dislike when there wasn't dislike to begin with. It's entirely reasonable to dislike something, and it is also very reasonable to then check with theory as to why that might be the case. Moreover, if someone takes the trouble to a) make screenshots, b) write it up in a blog, and c) share it with the world then I think they deserver far better than to be called a liar.

Re: Confusing UI in iOS7

#115
I can't confirm it because I don't have iOS 6 to hand, but I'm pretty sure the difference in button highlights will be the same.

The buttons in Timer works based on the OS wide standard of activating on release.

For a stopwatch, however, you want it to be instant because it's time sensitive. It would kinda suck if you're timings were all out by a bit because you kept you're finger on there slightly too long.

This is actually an example of breaking a convention to improve usability [1]. It's also an example of how if you're looking hard enough you'll find inconsistencies and things that are theoretically horrific in stuff you've been using absolutely fine for years.

The real inconsistency on this screen is that the Reset button doesn't activate on release. If ever there was a time you want to be able to back out of an action by moving your finger away from the button before release I'd say this is it.

While the faux naivity is a bit irritating, it does make a valid point (if not entirely novel). The more you pare back your UI the more you lose distinction between interactive and non-interactive elements. If your buttons are simply color tinted text, it's difficult to unambiguously use color tinting to highlight text of note such as the current day.

What makes iOS 7 really interesting is how it tries to counter that. For example, color hinted text in the edges of the screen will always be actions, so color is enough; color hinted text in the middle of the screen could just be marking interesting things, so actions are usually accompanied by thin borders.

An proper dive into the design and the trade-offs rather than endless "look at this edge-case" would be really interesting.

[1] Caveat because I'm sure otherwise someone will try and pull me up on it. No, this isn't amazing revolutionary design by Apple or super-human attention to detail. I'm sure the Android and WP 7 equivalents work the same.

Re: Confusing UI in iOS7

#116

This kind of post annoys me. It's driven by the fact that the author has some theories about UI design, and wants to share them with us. There's nothing wrong with that. But this post pretends to be like a real usability audit, which it is not. > When I tap it, it turns red — but wait — it doesn’t give me the visual feedback. Did I break it? > The alarm is shown as a red filled square, so when I tap it, it should per…

>These comments are disingenous[sic]. You didn't get confused by these things. What right do you claim in calling the OP a liar? Do you not think that he is capable of observing his own emotional reaction to UI independent of his intellectual understanding of it? Are you really claiming that he disliked the iOS UI because his theory told him to? That is utter hogwash. No sane person goes out of their way to assign an…

> What right do you claim in calling the OP a liar?

I didn't, I said his comments were disingenuous (what was your "[sic]" for btw?). I meant exactly what I said. I wouldn't call it lying, I'd call it disingenuous (i.e. put-on naivety).

> Are you really claiming that he disliked the iOS UI because his theory told him to?

No. I'm saying his theories about what's confusing, while sometimes interesting, are not necessarily representative of what regular users will actually find confusing, and you'd need to do testing to find out. The problem is he presents them as if they're definitely true, with absolutely no evidence.

Re: Confusing UI in iOS7

#117
post #107

I work with people who have TBI (Traumatic Brain Injuries) on a daily basis. Many have cognitive issues with short or long term memory. We use iPads during "Tech days". On iPads that we have updated to iOS7, people that normally have no problem are having a heck of a time with the new UI, where things are, new actions with swiping, buttons, fonts, ect. It's not as, dare I day, intuitive. Even using more outlines on t…

"Intuitive" is the great misused word of our industry.

The only intuitive things in human experience are fear of heights and the location of your mother's milk (I'm probably quoting but can't remember who). What people call intuitive is merely the familiar, all else is learnt.

IOS7 requires relearning, as you have confirmed.

Re: Confusing UI in iOS7

#118

This kind of post annoys me. It's driven by the fact that the author has some theories about UI design, and wants to share them with us. There's nothing wrong with that. But this post pretends to be like a real usability audit, which it is not. > When I tap it, it turns red — but wait — it doesn’t give me the visual feedback. Did I break it? > The alarm is shown as a red filled square, so when I tap it, it should per…

>These comments are disingenous[sic]. You didn't get confused by these things. What right do you claim in calling the OP a liar? Do you not think that he is capable of observing his own emotional reaction to UI independent of his intellectual understanding of it? Are you really claiming that he disliked the iOS UI because his theory told him to? That is utter hogwash. No sane person goes out of their way to assign an…

Wow, overreact much? The [sic] means you noticed a mis-spelling, clever you!

Re: Confusing UI in iOS7

#119
I also feel this complaint about iOS7, while relevant to the phone UI, is using the iPad UI to make a greater point: that iOS7 doesn't feel like it was designed for the iPad.

Skeuomorphic vs. Flat aside, the sparseness in how iOS7 looks on my iPad prompted me to revert the upgrade and go back to corinthian-leather-infested iOS6 for now.

The lack of visual cues in iOS7 is a bit off putting combined with the "designed primarily for iPhone" keep me from upgrading mine and my parents' iPads.

That said, I'm loving iOS7 on my iPhone5. It feels liberating.

Re: Confusing UI in iOS7

#120
post #93
post #61

Earlier quoted context omitted.

Yep. Discovered this one today. Completely ridiculous. If anyone wants evidence that iOS 7 was rushed, all they need to do is see things like that (and the parent post). All this is fixable though, rather than something endemic in the design of iOS 7, so I'm hopeful it'll get fixed soon enough.

We know it was rushed, and we know why. Scott Forstall (the architect of iOS 1-6) was fired, and Jonathan Ive promoted to VP of Design, on 29th October 2012, 11 months ago. 11 months -- really 7 months, as it had to be mostly done in time for the WWDC demo -- is an astonishingly short length of time to do a ground-up UX redesign of an OS. The only way it's possible is to parallelise the design process to some extent,…

Completely agreed – regardless of the amount of money at your disposal, I can't believe they managed it in 7 months. It really is crazy.
Post reply on HN