What should be default value of select (drop down list)?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I'm wondering what is the best practice of designing select / drop down lists. In some projects I've worked in the select on a form was filled with first value from the list. In other project we had always "-- select --" option chosen before user selected something else. I can imagine also empty field.
Is there any guideline about it? What is state of art in this matter?
drop-down-list select
New contributor
add a comment |Â
up vote
1
down vote
favorite
I'm wondering what is the best practice of designing select / drop down lists. In some projects I've worked in the select on a form was filled with first value from the list. In other project we had always "-- select --" option chosen before user selected something else. I can imagine also empty field.
Is there any guideline about it? What is state of art in this matter?
drop-down-list select
New contributor
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm wondering what is the best practice of designing select / drop down lists. In some projects I've worked in the select on a form was filled with first value from the list. In other project we had always "-- select --" option chosen before user selected something else. I can imagine also empty field.
Is there any guideline about it? What is state of art in this matter?
drop-down-list select
New contributor
I'm wondering what is the best practice of designing select / drop down lists. In some projects I've worked in the select on a form was filled with first value from the list. In other project we had always "-- select --" option chosen before user selected something else. I can imagine also empty field.
Is there any guideline about it? What is state of art in this matter?
drop-down-list select
drop-down-list select
New contributor
New contributor
New contributor
asked 2 hours ago
Landeeyo
1084
1084
New contributor
New contributor
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
I wouldn't say there are guidelines as such, but most design systems provide an insight on how to use dropdowns. Here are a few examples:
Material Design: Exposed Dropdown Menu
IOS - Pickers
Sidenote, Apple generally doesn't like dropdowns, they take you to a whole other page with selections.
Microsoft Fluent Design Guidelines
Not exactly what you are looking for but worth taking a look.
General Guidelines (from my experience):
Default Dropdowns: Explanation - Dropdowns that have a default state.
Examples - A dropdown that allows you to select a font. The default font is always selected.
Guideline - Provide a placeholder with the default option selected.
No state Dropdowns: Explanation - A dropdown that has no way of knowing the default state of selection. Examples - A dropdown that is used to select your nationality. Guideline - Use an explanatory placeholder. For the example above, the placeholder would be "Select Nationality" or even "Select" would do.
Field Specific Dropdowns: Explanation - Dropdowns that have a predefined purpose. Examples - Calendars, Time selectors, Username/ Profile selection. Guideline - Use field specific placeholders. If I am designing a calendar input, then the placeholder will specify the day's date. Time selectors will have a similar placeholder displaying the current time. profile selectors for selecting a single profile from a list of profiles will have the current profile being used as a placeholder (see: facebook).
Hope this helps ^_^
New contributor
add a comment |Â
up vote
2
down vote
There is no "best practice" here, those two options are completely different.
Pre-selected - use if you have a reason to believe one of the options is most likely (this can be based on most popular / probable option, or on data you know about the user), or if you want to push the user for that option.
Blank - "please choose" - use this, if you don't know or if you need to make sure the user makes a conscious choice.
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
I wouldn't say there are guidelines as such, but most design systems provide an insight on how to use dropdowns. Here are a few examples:
Material Design: Exposed Dropdown Menu
IOS - Pickers
Sidenote, Apple generally doesn't like dropdowns, they take you to a whole other page with selections.
Microsoft Fluent Design Guidelines
Not exactly what you are looking for but worth taking a look.
General Guidelines (from my experience):
Default Dropdowns: Explanation - Dropdowns that have a default state.
Examples - A dropdown that allows you to select a font. The default font is always selected.
Guideline - Provide a placeholder with the default option selected.
No state Dropdowns: Explanation - A dropdown that has no way of knowing the default state of selection. Examples - A dropdown that is used to select your nationality. Guideline - Use an explanatory placeholder. For the example above, the placeholder would be "Select Nationality" or even "Select" would do.
Field Specific Dropdowns: Explanation - Dropdowns that have a predefined purpose. Examples - Calendars, Time selectors, Username/ Profile selection. Guideline - Use field specific placeholders. If I am designing a calendar input, then the placeholder will specify the day's date. Time selectors will have a similar placeholder displaying the current time. profile selectors for selecting a single profile from a list of profiles will have the current profile being used as a placeholder (see: facebook).
Hope this helps ^_^
New contributor
add a comment |Â
up vote
2
down vote
accepted
I wouldn't say there are guidelines as such, but most design systems provide an insight on how to use dropdowns. Here are a few examples:
Material Design: Exposed Dropdown Menu
IOS - Pickers
Sidenote, Apple generally doesn't like dropdowns, they take you to a whole other page with selections.
Microsoft Fluent Design Guidelines
Not exactly what you are looking for but worth taking a look.
General Guidelines (from my experience):
Default Dropdowns: Explanation - Dropdowns that have a default state.
Examples - A dropdown that allows you to select a font. The default font is always selected.
Guideline - Provide a placeholder with the default option selected.
No state Dropdowns: Explanation - A dropdown that has no way of knowing the default state of selection. Examples - A dropdown that is used to select your nationality. Guideline - Use an explanatory placeholder. For the example above, the placeholder would be "Select Nationality" or even "Select" would do.
Field Specific Dropdowns: Explanation - Dropdowns that have a predefined purpose. Examples - Calendars, Time selectors, Username/ Profile selection. Guideline - Use field specific placeholders. If I am designing a calendar input, then the placeholder will specify the day's date. Time selectors will have a similar placeholder displaying the current time. profile selectors for selecting a single profile from a list of profiles will have the current profile being used as a placeholder (see: facebook).
Hope this helps ^_^
New contributor
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I wouldn't say there are guidelines as such, but most design systems provide an insight on how to use dropdowns. Here are a few examples:
Material Design: Exposed Dropdown Menu
IOS - Pickers
Sidenote, Apple generally doesn't like dropdowns, they take you to a whole other page with selections.
Microsoft Fluent Design Guidelines
Not exactly what you are looking for but worth taking a look.
General Guidelines (from my experience):
Default Dropdowns: Explanation - Dropdowns that have a default state.
Examples - A dropdown that allows you to select a font. The default font is always selected.
Guideline - Provide a placeholder with the default option selected.
No state Dropdowns: Explanation - A dropdown that has no way of knowing the default state of selection. Examples - A dropdown that is used to select your nationality. Guideline - Use an explanatory placeholder. For the example above, the placeholder would be "Select Nationality" or even "Select" would do.
Field Specific Dropdowns: Explanation - Dropdowns that have a predefined purpose. Examples - Calendars, Time selectors, Username/ Profile selection. Guideline - Use field specific placeholders. If I am designing a calendar input, then the placeholder will specify the day's date. Time selectors will have a similar placeholder displaying the current time. profile selectors for selecting a single profile from a list of profiles will have the current profile being used as a placeholder (see: facebook).
Hope this helps ^_^
New contributor
I wouldn't say there are guidelines as such, but most design systems provide an insight on how to use dropdowns. Here are a few examples:
Material Design: Exposed Dropdown Menu
IOS - Pickers
Sidenote, Apple generally doesn't like dropdowns, they take you to a whole other page with selections.
Microsoft Fluent Design Guidelines
Not exactly what you are looking for but worth taking a look.
General Guidelines (from my experience):
Default Dropdowns: Explanation - Dropdowns that have a default state.
Examples - A dropdown that allows you to select a font. The default font is always selected.
Guideline - Provide a placeholder with the default option selected.
No state Dropdowns: Explanation - A dropdown that has no way of knowing the default state of selection. Examples - A dropdown that is used to select your nationality. Guideline - Use an explanatory placeholder. For the example above, the placeholder would be "Select Nationality" or even "Select" would do.
Field Specific Dropdowns: Explanation - Dropdowns that have a predefined purpose. Examples - Calendars, Time selectors, Username/ Profile selection. Guideline - Use field specific placeholders. If I am designing a calendar input, then the placeholder will specify the day's date. Time selectors will have a similar placeholder displaying the current time. profile selectors for selecting a single profile from a list of profiles will have the current profile being used as a placeholder (see: facebook).
Hope this helps ^_^
New contributor
New contributor
answered 1 hour ago
Chemicalinck
513
513
New contributor
New contributor
add a comment |Â
add a comment |Â
up vote
2
down vote
There is no "best practice" here, those two options are completely different.
Pre-selected - use if you have a reason to believe one of the options is most likely (this can be based on most popular / probable option, or on data you know about the user), or if you want to push the user for that option.
Blank - "please choose" - use this, if you don't know or if you need to make sure the user makes a conscious choice.
add a comment |Â
up vote
2
down vote
There is no "best practice" here, those two options are completely different.
Pre-selected - use if you have a reason to believe one of the options is most likely (this can be based on most popular / probable option, or on data you know about the user), or if you want to push the user for that option.
Blank - "please choose" - use this, if you don't know or if you need to make sure the user makes a conscious choice.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
There is no "best practice" here, those two options are completely different.
Pre-selected - use if you have a reason to believe one of the options is most likely (this can be based on most popular / probable option, or on data you know about the user), or if you want to push the user for that option.
Blank - "please choose" - use this, if you don't know or if you need to make sure the user makes a conscious choice.
There is no "best practice" here, those two options are completely different.
Pre-selected - use if you have a reason to believe one of the options is most likely (this can be based on most popular / probable option, or on data you know about the user), or if you want to push the user for that option.
Blank - "please choose" - use this, if you don't know or if you need to make sure the user makes a conscious choice.
answered 1 hour ago
vsvec
1615
1615
add a comment |Â
add a comment |Â
Landeeyo is a new contributor. Be nice, and check out our Code of Conduct.
Landeeyo is a new contributor. Be nice, and check out our Code of Conduct.
Landeeyo is a new contributor. Be nice, and check out our Code of Conduct.
Landeeyo is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f120941%2fwhat-should-be-default-value-of-select-drop-down-list%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password