Both ways seem to pose a false-positive paradigm. This can be simpler and not have to force the user to spend time making sense of the color-to-label association.
Simply make the "Delete" button more prominent. Make the "Cancel" button less prominent. In regards to the labeling within the buttons, there is no need to put much context into what essentially ...
Quite a late answer, but I'm surprised no one here pointed this out before -- it is possible for a toggle switch to show its current state and the state to which it will change simply by having text outside the button, instead of on it.
As dotancohen points out:
The problem is that in English "on" and "off" are both adverbs ...
I'm not so sure you should be thinking only in terms of red and green. Red has typically been associated with danger, potentially dating back to the middle ages (citation needed). A quick Google image search for "delete" yields almost entirely red images.
To me (and to bootstrap) green indicates success, red indicates danger.
As deleting is a dangerous ...
Looking at this from a slightly different angle, where possible you could consider removing the confirmation entirely and switching instead to an "Do/Undo" process.
This method is often used across the Google services:
It has the advantages that it's culturally neutral and more efficient for the user (one-click rather than two to delete).
Disadvantage is ...
Cancel might be too vague. I always like to be more descriptive when asking users to perform a quite destructive task. This often reduces any anxiety users might have.
download bmml source – Wireframes created with Balsamiq Mockups
As LightnessRacesinOrbit made me realise in the comments, mixing up buttons with links that act like buttons (or in ...
Besides the arguments others have listed (Aircraft requirements, power saving) we should not forget about security.
Before the tablet and smartphone era you had a great control over your computer in an emergency: if you pulled the UTP cable, you could guarantee that the computer is isolated from the network. If you pulled the power cord, you could guarantee ...
I suggest displaying the button in its disabled state and adding a tooltip explaining why it is disabled and how users can get the permissions to use this action.
Not displaying the button:
Users will search for this option and will maybe think they don't see it and therefore may spend time looking for it, possibly refreshing the page, restarting the ...
A hardware radio switch has security benefits to it in that when it is off, you know for a fact that nothing is connected to your laptop wirelessly. The radio switch usually turns off all wireless communication, including Bluetooth and 3G.
I have heard that this is a requirement in certain military environments, but I have not seen any evidence ...
Keep the button
In this case the button is used for the user to tell the application to navigate to the next page. If you remove the button, you say in your comment above,
I don’t think that’s an issue — an auto postback would do it. I have code that wraps the sliders, so it’s possible to determine if both are set, and if so....
What if a user sets the ...
Yes. There is a very simple, effective heuristic that adjusts to the preference of each user.
Place a check box in the warning message dialog that says:
Don't show this message again
Which can be improved further by stating where that dialog can be reenabled.
Don't use No with Cancel. They somewhat do the same functionality.
I would suggest you go a step ahead and be accurate with the options you provide. We click Yes/No many times without reading the message in modal dialog - particularly, when we are installing applications, or facing some warning/alert popups. As a responsible designer/developer; you want ...
With all due respect, I think every answer so far has missed the mark somewhat.
First of all, based on the Context section of your question ...
Before deleting an album, the user is asked to confirm the action.
... we can deduce that this is not a success or error modal, but rather it is a confirmation modal, which implies a warning or caution ...
tl;dr → use familiar patterns
Make the text objects look less like navigational tab controls.
The elements seem unnecessarily divided: Place the search field in the main header.
Make search look more like search.
The subconscious factor making your test subjects want to tap those text objects is positioning. They appear to be tabbed ...
I would suggest removing the Reset button entirely. See this excerpt from the Nielsen Norman Group:
Reset: Don't Use
The Web would be a happier place if virtually all Reset buttons were
removed. This button almost never helps users, but often hurts them.
Reset clears away the user's input on a Web form, but why would people
want to do that? ...
I'm guessing they viewed the button on the right hand side as the primary action button as it's closer to the users thumb, with the button on the left for secondary/less-used action, as it's slightly further away from the thumb (more of a physical exertion on the user).
They then may have wanted to label them accordingly - so A for primary button, B for ...
Well, since people are trying to interact with this information, I'd use it as an advantage. As mentioned by Mattynabib, it really makes sense.
However, if for some reason you prefer not to, the answer would be to make this snippets of information a homogeneous message. The way it is now, it looks like a mix of a marketing and an interactive element (hence ...
As a user I don't like this idea at all.
There are 2 scenarios:
Creating an entity
Editing an entity
If I am in the create mode for say... a contact... as soon as I type "Dave" in a first name field it would have to create an entity... if I decide nah... I'm not going to add Dave after all, normally I just leave the screen and all is fine but in this case ...
I think icons are the best possible way to convey the information about different flushing amounts. I see too much uncertainty by relying only on button relative sizes and ease of use.
It can be a simple pictogram showing the tank in the relative size of water what will be flushed upon pressing that button.
Or any other icons that ...
I would say that "New" is best in most situations, as it is short and distinct.
A good rule of thumb is to look at the other options you will have in your menu. You want to make scanning fast, so you want to make each option as distinct as possible. Here is a crude example of what I mean:
download bmml source – Wireframes created with Balsamiq ...
There are a few cautions: 1. Feature discoverability, 2. Icon interpretation in the absence of labels, and 3. Confusion over which state the toggle (or stateful button) represents.
1. Discoverability: Out of sight, out of mind
Lukew, in 'Obvious always wins', cites loss of engagement when vying for menu space:
His mobile example involves lots more space ...
Microsoft’s design guides talk about weak affordance:
Text and graphics links use a hand […] pointer […] because of their
weak affordance. While links may have other visual clues to indicate
that they are links (such as underlines and special placement),
displaying the hand pointer on hover is the definitive indication of a
Excellent answers so far.
I would attempt to connect the dots between recording and red button like this:
Apart from the traditional warning usage, a red light has been used in many scenarios to represent on-going work - radio show room when on air, operation theater when operation is going on, etc. The reason behind that would be the same - it is highly ...
The reason for the design was because of the technology at the time.
Rotary Dial (Pulse dialing)
To dial a number, the user puts a finger in the corresponding finger hole and rotates the dial clockwise until it reaches the finger stop. The user then pulls out the finger, and a spring in the dial returns it to the resting position. For example, if the ...
Ok I might be on to something:
"New" is good for buttons that take the user to a clean "canvas", where the user can add his content.
"Create" is good for buttons that "submit" the user's content or input (either into a database or to some public platform).
In other words, "New" doesn't suggest that you're actually creating anything. It just sets the stage ...
I would suggest that the play button stays the same as it always has - a triangle to begin then a pause once playback begins. But, once playback has started, a new button appears like this:
The circle encapsulating the easily recognisable play triangle is pointing in an intuitive direction: anti-clockwise, implying that we are going back in time. The ...
Type of the information captured and number of fields required
It really depends on the type and scope of the information you are asking for and the number of fields that need to be filled:
I have tested and used this pattern successfully in login and and password creation. I think because the interface is so simple and the number of fields required ...
You can change the button to reflect the only available action, but separate the display of state.
You've replaced the button label with the only available action: reverting (unregistering).
Where it starts to get a little confusing is you have a checkmark alongside the button label.
One approach is to separate them. Separate the status 'You are attending' ...
...but name buttons after what they actually do.
This might seem pedantic, but looking at the screenshot the "Select" button doesn't select the video, it confirms a previous selection, presumably by the user clicking one of the videos, etc.
You might want to use the verb that your application will perform, such as Edit, Delete, Play, etc. Or stick with OK /...