New answers tagged dropdown
2
As you mentioned, the user cannot select both SD and HD formats. Why not roll up into a single group annotated as "Format Type". All options can then be listed within the group as radio buttons. This may work better but takes up slightly more space.
download bmml source – Wireframes created with Balsamiq Mockups
0
I think the main question to ask is why to use dropdown?
A dropdown takes less space, but makes the user click on it to see the options - moreover, after the user chooses an option she can review other options only by clicking on it yet again (though it is not always important).
You can put the dropdown items in order of their chance to be selected. Or ...
0
My recommendation would be to with a logical approach based upon the use case of where you see this dropdown being used and what is the information which is most critical to your users. For example if you are using this in the backend CMS for a e-commerce site and your user is the owner who wants to see how many orders have been paid for and then how many ...
0
NN/g article explaining different sorting which should be used depending on the scenario. Alphabetical Sorting Must (Mostly) Die
Widths and heights are ordinal data, meaning that they have an inherent monotonically increasing sequence. Such items should almost always be sorted accordingly.
Other times, items have domain-related logical groupings. ...
0
I find people have issues tracking down options in logical order when the list is longer than 4 items long. Some ways to address this issue:
Group the options and label the groups.
Stick the logical options in a sentence, or madlibs style form. You can make complicated options much easier to understand, and you can break options lists down into smaller ...
6
Menus are a navigation element and so what make the most sense is whatever makes navigation easier for your users.
Your first example is a good menu, as although you have only one item under 'Otters', it wouldn't make sense renaming 'Otters' to 'Sarah' as it would then look like 'Sarah' were a type of animal. Additionally, if you get a second otter to keep ...
1
I would wonder if theres any established best practice for this situation. This would depend on different factors.
Scalability:
If your navigation menu is category based and there is significant possibility that the number of menus under it may increase, its definitely good to keep it as category. Example, If 'Accommodation' may contain 'Guest House', ...
1
A approach I would take is to provide the alternate filtering option on the page of the main level only.For example,taking your last example of filtering by hotels the design would be something like that
download bmml source – Wireframes created with Balsamiq Mockups
The advantage of this method is that you can provide the superset of results ...
2
Menus don't have to be logic they have to be meaning and useful.
If there is one "child" then you do not need a "parent" like a unique radio button does not make sense.
Having sub-navigation on-click is common but very replaceable
Most web sites do not have sub-navigation menus. A book of one chapter does not need a summary: you just read it, a house with ...
0
A list can be sorted in one of the following ways
Technical Ordering (Ascending/Descending)
Logical Ordering (FIFO, LIFO, Sequential)
Ethical / Value Driven (Projected by Paradigms)
2 seems to be a bit more difficult of a case, do you order from most restrictive to least restrictive or the opposite.
What you are looking for is a value driven ...
6
How about this layout?
download bmml source – Wireframes created with Balsamiq Mockups
I guess the users need to decide if they want either SD or HD so this should be the main option. Then, secondary, they can select whatever other option you offer.
This solution also enables you to set a default for users. You could work with radio buttons ...
10
Unless you can proceed without selecting (leave the field blank) one SD options, I would suggest you go with a radio button.
You layout remains consistent if you are using the same input mechanism for similar tasks. Making it easy for the user to proceed quickly.
Radio buttons are faster (easier also in many cases) than using a drop down menu. The ...
6
Situation n°1: The user knows where she can find a location: you can use a combo box instead of a drop-down.
You want you design the combo box adequattly so the user knows she has to start typing in it. You surely want it to be auto-complete.
Below, an example taken of Facebook profile editing.
Situation n°2: The user does not know the location she ...
1
I see a clear distinction between where to use button, radio button or dropdown.
Button - is typically used to submit information. If you just want user to select an option without submitting the information you can use Button.
Radio Button - is typically used to provide a selection to user if you have a very few option to select. Anything in the range of ...
0
Have you considered incorporating a toggle switch into the button?
I'm not sure if this would be an improvement over the radio/menu option but it might help your users understand what you're trying to achieve. It's still not great, though, if only one option is available at a time.
0
Dropdowns require multiple clicks vs single - multiple events (clicks) to activate/select one, and they are not "readily" visible (the options) until you activate the dropdown.
Radio buttons are groups (single one active) - no multiple selection available without a new radio group
your buttons have the features of multiple select (select any number as well ...
20
A single button should perform an action, and not act as a radio button. If you want buttons to act as radio buttons, you should use a segmented button.
There is established precedent for this in both mobile and web UI, so people are likely to already understand what they do. Additionally the design of segmented buttons shows that the buttons are ...
0
Command Button is meant for executing some command as per the caption it holds. Like this, every UI component has its own purpose.
The UI components can be used for different purposes other than the ones they are actually intended for. For example, like in your case, command buttons can be used to accept various options from user, or for that matter, even a ...
25
This kind of UI elements exists and is used in many applications even if differently.
Facebook events
Google calendar
If well designed they are even more affordant than the usual radio buttons.
The thing is, because of this affordance they seem "auto selected" so there is no need of a validation like in your example. Therefore I would say radio ...
1
In your tab design you are hacking in a drop down menu due to space constraint. Why not be consistent and use a drop down for the entire thing.
Also, drop down menus have good integration in the OS (atleast iOS does it, where they pop-up the menu options from the footer ) making the interaction not so clunky. It gives you a comfortable target area compared ...
3
Use tabs if both of these are true:
the list is always only going to be short (say 3 items long)
the typical user will regularly switch between options
Use a dropdown if any of these are true:
the list is either long or is likely to need more options in the future. Tabs simply don't work when you have many tabs to show at the same time and not a lot ...
1
This is a tough question that is very much dependent on the proficiency of your user and the type and importance of the information being requested. That said, I have found a few things to be true in testing.
It is usually not a great idea to have a default selected unless you are very certain that the overwhelming majority of users want that option. Most ...
1
It's a good practice to use default values in dropdowns. If you can guess or preselect one of the options the user won't need to select it him or herself.
In other cases you maybe won't know which is a good default or maybe for political reasons you would prefer not to preselect it. In these cases I would recommend using radio buttons when possible (this ...
1
It becomes difficult to detect and handle the failure mode wherein a user forgets to make a selection, if the default option is a valid selection. As an example, many forms asking you to choose a state would get submitted with AK (Alaska), the first by alphabetical order.
17
A dropdown list (or combobox) should already be a clear indication that you need to select an item from there, so wasting the first item by telling someone this is redundant and a poor idea.
The only times that I would recommend having some other text in the dropdown are:
when it is not essential to select an item
when you want effectively to select ...
2
You problem seems to be that you're collecting a number of buttons in the same list that are completely different from each other. Being in a single drop down menu implies a relationship between them that isn't there. Viewing system messages and marking an object as read are so far removed from each other, they should never be part of the same menu.
...
1
Don't bother the user with information about the system unless it directly impacts her. She only needs enough of a mental model to understand how things work with regards to her. (See the Design of Everyday Things by Donald A. Norman for more information on users' mental models.) This means that you should only make minor edits to some of the action names ...
Top 50 recent answers are included
