I’m creating an interface, meant to be used by non-technical business people, which needs to be able to define simple structures to hold some user data.
I want to be able to support Boolean fields, but I suspect that most non-technical people won’t know what “Boolean” means.
To avoid explaining it, I’m thinking of using the word “Switch” and comparing it to a power/light switch, i.e. it can only be on or off.
Does this make sense, or can anyone suggest a better alternative?
For context, it is a mostly English-speaking audience.
I’d use contextual words that relate to the option / question rather than trying to find a one size fits all solution. You might find a good way of representing the options like this but you must consider the context of the language of the option.
So for ‘Activate Widget?’ You would use ‘yes’ or ‘no’.
Or for a list of widgets, you might use ‘enable’ or ‘disable’.
Using language that relates to the option as the user sees it is the best way, this is speaking the users language. They certainly shouldn’t see the word Boolean, unless they’re programmers!
Make sure your designs are clear between on and off so it’s easy to see what option is selected.
If it really is a boolean choice then the obvious choice would be True or False. Otherwise Tony’s answer seems the most reasonable.
I’d name the field type "True/False" or "Yes/No". Or just "Boolean" — people can always look it up in a dictionary.
User-friendly name for Boolean options? – ux.stackexchange.com #JHedzWorlD
No comments:
Post a Comment