181–190 of 192 posts
Earlier quoted context omitted.
That is a ludicrous argument. An animation does not affect timer functionality unless you are an incompetent coder.
Yes, but it's equally ludicrous to say that the stopwatch "didn't give the visual feedback". It started incrementing those huge numbers, didn't it?
Earlier quoted context omitted.
Actually, that's backwards... You know that something is well designed precisely by pretending to be an idiot, and asking yourself if you still know what to do...
That's a very rudimentary view of UX. If I'm writing an app that helps radiological engineers calculate radiation dose, should I pretend to be an idiot? Likewise, in a world where kids have grown up with these devices, should we still think that way about UX? I think we can give users some benefit of the doubt. Each app should have a design that reflects the purpose of the app. Consistency is not always the top prior…
The point I was trying to make is that if you're taking the view that your users need to have a significantly higher than average the level of knowledge in a domain area (i.e. equivalent to the knowledge of the domain area that the product designer has), you're going to end up with an un-usable product for the left end of the bell curve of your user population.
That left end of the bell curve is relative (as you point out) to your user population, but exists nonetheless - an "idiot" radiological engineer is not an idiot in relation to the general population, but is one in relation to the 99th percentile best radiological engineer (and, hopefully, in relation to the radiological engineer building your product).
What I was trying to say is that a well-designed UX requires that the 1% "idiot" of your target user population still knows what to do...
Earlier quoted context omitted.
I think one of the major points of iOS7 is that grandma is getting kicked to the curb. iOS devices are designed for people who already know how to use them, or for young people, who will figure them out.
Except this doesn't seem to be borne out in reality. I have installed it for people in their 60's, 70's and 80s who find a Mac barely usable, who have had no trouble at all with moving to iOS7 after using iOS6.
Earlier quoted context omitted.
That's a very rudimentary view of UX. If I'm writing an app that helps radiological engineers calculate radiation dose, should I pretend to be an idiot? Likewise, in a world where kids have grown up with these devices, should we still think that way about UX? I think we can give users some benefit of the doubt. Each app should have a design that reflects the purpose of the app. Consistency is not always the top prior…
I'm not saying that's the only step in design... In my attempt at brevity, I lost the nuance. The point I was trying to make is that if you're taking the view that your users need to have a significantly higher than average the level of knowledge in a domain area (i.e. equivalent to the knowledge of the domain area that the product designer has), you're going to end up with an un-usable product for the left end of th…
Earlier quoted context omitted.
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.
And yet, despite all the valid criticism of all the flaws in iOS 7, it's a massive improvement over iOS 6. And the user reactions show that.
How do they show it? We don't know how many % of the iOS user base uses Twitter or any observable channel to praise iOS 7 or complain about it. Plus it's impossible to downgrade, so any iOS 7 user in a statistic might be an unhappy one; or the other way around, maybe I would love iOS 7 on my iPad 3rd gen, but I won't irreversibly upgrade for now.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
How do they show it? We don't know how many % of the iOS user base uses Twitter or any observable channel to praise iOS 7 or complain about it. Plus it's impossible to downgrade, so any iOS 7 user in a statistic might be an unhappy one; or the other way around, maybe I would love iOS 7 on my iPad 3rd gen, but I won't irreversibly upgrade for now.
http://appleinsider.com/articles/13/09/24/ios-7-shines-as-ap...
This is what I'd love to see, regardless of the results: http://www.nngroup.com/articles/windows-8-disappointing-usab...
As far as I know, the closest thing that's publicly available are customer satisfaction surveys.
Earlier quoted context omitted.
> 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.
Uhm, why exactly should that be the case? I think you should think over your assumptions. Date format and date names are intertwined, you cannot separate the two.
That is not even mentioning that "ISO 8601 Data elements and interchange formats – Information interchange – Representation of dates and times" puts Monday as day one.
Plus all the clients that aren't broken and can separate language from style.
Oh well, I think I got trolled -.-
Earlier quoted context omitted.
In my UX design classes, we would use the phrase "You can't polish a turd" to describe this situation.
If the stopwatch timer didn't record time properly, I'd see where you're coming from. UI polish isn't going to make fix an error in the timer. But here, all the core functionality works, the clocks show the right time, the stopwatch starts and stops. The main complaint here is about the colour of the buttons, which I agree could do with some polish.
So, rather than evidence of bad design, this could be evidence of good design.