Every time I go into the app I have to remind myself that the buttons show the current state and not what action they will take. I believe a well-designed button should say what it is going to do instead of what the current state is.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Do you feel like the buttons in the app are backwards?
- Thread starter apearson
- Start date
mrau
Authorized Driver
I tend to think of them as “Indicators” first, so I like they show the current state.
But I do see your point.
But I do see your point.
I guess my main problem is the climate shows the current status, the frunk shows what it will do, and the lock shows the current status. 1 is different from the other.
skitown
Member
I don’t disagree. The frunk button often makes me do a double take and think about if I’ve accidentally opened it.
Don't Make Me Think - Wikipedia
RTPEV
Active Member
I guess I never really thought about it that much.
The "apps" I use more than anything are webconferencing apps, and in particular, the mute button. Almost without exception (I would say without exception, but there are a few webconferencing apps I don't use often enough to know for sure), the mute button basically shows you the current status. That is, when you are not muted, it shows a picture of a mic. When you click it, it puts a line through the mic, or highlights it in red to indicate it is OFF. This make it very easy to glance at and see if my mic is on or not.
I think about the app buttons the same way. When I look at the fan, if it's got a line through it, I know the fan is not on. When I look at the lock, I know whether it's locked or not. True, the frunk button is different in that it shows the frunk being open, but I suspect this is more about highlighting what the button is, because without the popped frunk it would just look like the front of a car. I can live with that because the frunk open/closed is not a status I really need to check on normally.
So, in my opinion, no, the buttons are not backwards. They are just as they should be.
The "apps" I use more than anything are webconferencing apps, and in particular, the mute button. Almost without exception (I would say without exception, but there are a few webconferencing apps I don't use often enough to know for sure), the mute button basically shows you the current status. That is, when you are not muted, it shows a picture of a mic. When you click it, it puts a line through the mic, or highlights it in red to indicate it is OFF. This make it very easy to glance at and see if my mic is on or not.
I think about the app buttons the same way. When I look at the fan, if it's got a line through it, I know the fan is not on. When I look at the lock, I know whether it's locked or not. True, the frunk button is different in that it shows the frunk being open, but I suspect this is more about highlighting what the button is, because without the popped frunk it would just look like the front of a car. I can live with that because the frunk open/closed is not a status I really need to check on normally.
So, in my opinion, no, the buttons are not backwards. They are just as they should be.
Needsdecaf
Active Member
They are kind of counter intuitive. I see both sides of the argument (although the dress was most definitely white and gold, where were all you fools getting blue and black from!?!?). The problem is that it's a combo control and indicator status, which is common in computers as RTPEV said, but on cars, you typically have a separate control with a logo for "what it does" and then an indicator of some sort. Be it a light or a display. Or even no indicator. Take something as simple as a lock on a modern car. There isn't one button to lock and unlock. There is a lock button and an unlock button. Some cars have a little light that comes on, others have a redundant physical button that moves so you can see. Others just are locked and you can figure it out when you pull the handle. But you have two buttons, each indicating what they do.
On an app, you don't want to use up that much real estate. I guess you could have a lock icon and an unlock icon, and just illuminate which state your're in, but that takes up screen real estate and clutters the UI.
I haven't had any issues with it, but every time I look at it, it does give me pause.
On an app, you don't want to use up that much real estate. I guess you could have a lock icon and an unlock icon, and just illuminate which state your're in, but that takes up screen real estate and clutters the UI.
I haven't had any issues with it, but every time I look at it, it does give me pause.
Similar threads
