For me Apple's "hold the button until something happens" to turn on my iPhone is and always has been and always will be a FAIL.
If you're a button, you have one job
241–250 of 308 posts
Re: If you're a button, you have one job
#242[deleted]
Re: If you're a button, you have one job
#243I am puzzled (and irritated) why there is „rotate left” without „rotate right”. Does any of you know why?
Re: If you're a button, you have one job
#244[deleted]
Re: If you're a button, you have one job
#245I am puzzled (and irritated) why there is „rotate left” without „rotate right”. Does any of you know why?
Two wrongs don't make a right but three lefts do, and that seems like a reasonable tradeoff to reduce visual clutter
Re: If you're a button, you have one job
#246Earlier quoted context omitted.
There’s effectively no universal list of UX warts people agree with. The Flat UX fad was objectively terrible on just about every metric I was taught, but people were actively pushing for such designs.
What’s wrong with flat UIs? Skeuomorphic designs have served their purpose of helping people get used to computers, but now that is no longer necessary.
It’s not that it’s impossible to make a useable flat UI, it’s that people constantly forgot critical functionality.
You need to denote a button is different from text. You need feedback that a UI element was interacted with, and for toggles you need for people to be able to tell what represents on vs off. The borders between different UI elements needs to be clearly defined, etc etc.
Re: If you're a button, you have one job
#247People often forget that animations serve purely a supportive role and do not exist for the purpose of having animations. They are there to mask loading times and ease from one state into the other. That's why we have them. This knowledge eventually got lost (figuratively speaking) and now we have code that needs to wait on the animation to finish. Another amazing example of cargo culting.
I have disabled all animations on my Android, and it feels so much nice. I particularly HATE that one animation where the whole screen stretches if you try to overscroll.
Dude that animation sucks so much I could not believe that there was no way of disabling that without disabling _all_ animations.
The fact that it makes content move in a way that is illegal breaks my mind. You try to check "is this the end" and it all starts moving. What the hell. Why.
I kinda forgot just how much I hate this animation. Thanks for the reminder. Why, google.
Re: If you're a button, you have one job
#248Earlier quoted context omitted.
That is a valid opinion to hold, however, the question of "what is wrong with X? Y is outdated and over" is a) a different statement from "I prefer X" and b) pretty low effort, trivially to Google (or ask AI) and generally a bit on the ignorant side A better reply would not just have said what it said but contained actual wonder about the topic. Like this, it's just indistinguishable from engagement bait.
> pretty low effort, trivially to Google (or ask AI) and generally a bit on the ignorant side I know the most common reason why people prefer skeuomorphic design (the visual metaphor), which is why my original reply directly addressed this complaint by saying that it’s no longer relevant. Some other complaints I’ve found online are about specific bad instances of flat design rather than flat designs in general. There…
I’ve never seen a single instance of flat design without any significant usability issues.
A core issue is UI is a language and by reinventing things from scratch you ended up with some designs choosing A to represent something toggled on, and some designs using A to show the exact opposite. Thus a user needed to interact with that specific design to learn core functionality.
Re: If you're a button, you have one job
#249That's a great example. But, it's not always so clear cut. Following the exact "best practice" in the article, the iPhone lock screen has this issue. Say your password is 1234 but you accidentally type 11234. What the iPhone will do is see 1123, the pause to tell you you failed, then enter 4. Now you, having muscle memory, will type 1234 (your password). But iPhone kept that 4 so it sees 4123 then pauses to tell you…
It's not that iphone keeps that 4; it's that iphone pretty quickly starts accepting the next round of input after 1123 and then you type 4.
Perhaps a longer pause will prevent you from typing that 4 but that also means other people who mistype their passcode have to wait longer to retry. It's a tradeoff. I suspect there are more people who type the wrong passcode of the correct length than the incorrect length.
Re: If you're a button, you have one job
#250[dead]