I'm developing a desktop application and in the application settings management dialog I've add a button that once pressed, reset all fields to default values.
I'm wondering what is the standard for that button text. I've taken into account the followings (seen in popular software):
What is the more appropriate? Is there a standard for this?
If you can only use one word from 'reset to default options', use "reset". It clearly communicates an action.
Using "defaults" is ambiguous because it can mean restoring defaults, but could also open up a more detailed set of options. For example (in an image editor) you might choose always save to jpg or png or whatever by default, or to have a X*Y px canvas for new files.
If there's room for it, expand on what you have already suggested. Leave no doubt what this button will do. A couple of suggestions:
"Reset All Fields to Default"
"Reset All Fields to their Original Settings"
It is just as important to stay within the existing Style Guide of Content. Try to use as many existing terms and phrases as possible. Consistency is usually the correct solution.
And for extra measure, a confirmation modal may be good practice. Especially if this action can not be undone.
In my opinion, you should better concern about using this button. Please read: Reset and Cancel Buttons | Nielsen Norman Group. I think the arguments can be applied to a desktop app too.
Reset: Don't Use
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? The Web is characterized by frequent movement between pages and users rarely encounter the same form twice. Thus, a Web form is almost always cleared when the user sees it. Even when a user revisits a form in a single session, it is usually faster to edit the old data than to erase it and start over.
The Reset button hurts users in three ways:
- The worst problem about Reset is that users click the button by mistake when they wanted to click Submit. Bang — all your work is gone!
- Having two buttons at the bottom of a form clutters up the interface and makes it harder for users to clearly see their next step. Some small amount of wasted time is spent scanning the useless button and deciding which of the two buttons is the correct one.
Even when users do want to eliminate some of the data they have entered into a form, it may slow them down to have a dedicated button for doing so, since the extra button means that users have a choice:
- edit the erroneous fields and replace the old text with the new text click
- Reset and type the new text into nice clean fields
Also, check similar question on https://ux.stackexchange.com, like Is a cancel button necessary in a web form?
If you will still want to use the button, please consider that "Reset" is a standard, recognizable term and, with the proper position in the UI, suggest the implication of an action in all fields. You can use "Reset to defaults" / "Reset all" if you want to be sure the action will be clear for all users.
Just to sumarize. Correct answer depends mainly on available space for your label. Your problem has been already solved in whole bunch of different apps. Most common uses are:
In my opinion everything else is will be inconsistent to what people used to for years.
As someone mentioned before, please consider providing confirmation screen / modal / window etc.
