Question, any guides anywhere on how toggle options in drop down menu's are supposed to look like ?

Just I was using an application that has a toggle menu option, and it doesn't tell you its a toggle!

It does change its name, but of course, you don't know its going to do that because it looks like any other menu item..

So, what is the standard way of showing toggle menu options, in a drop down menu.

Eg. Not a static toggle !!!

  • 3
    I don't think there is any standard, users just fuck around and find out
  • 2
    A couple of suggestions folk just told me about:


    h t t p s : / / w w w . j u s t i n m i n d . c o m / b l o g / d r o p - d o w n - l i s t - d e s i g n /
  • 1

    And this one:


    h t t p s : / / h e l p . b l o c s a p p . c o m / k n o w l e d g e - b a s e / t o g g l e - n a v i g a t i o n - m e n u - s t y l e s /

    Which is closer to what I imagine it should look like, and can be done in text !
  • 1
    Depends on the UI framework. I've seen e.g. radio buttons in a menu, I don't know about a dropdown with these and I can't give a specific example. There should be some examples in the documentation of the framework you're using; if not, a quick workaround would be just using symbols in the labels to signify radio buttons (e. g. 🔘), and you'd have to redraw the menu on each toggle to add and remove the symbols where needed.

    Edit: I thought you were talking about radio buttons, but this should mostly apply to toggles too.
  • 1
    Systems" book or blog or something like that for best practices.

    Buttons, forms and any other interaction should:
    - be visible (so like you noticed: people need to know that the function of a toggle is available to them).
    - be consistent.
    - be familiar (no weird incoherent symbols etc).
    - clearly show use of elements (i.e. a button should look pushable)

    And more you can find on such resources (I recommend Designing Interactive Systems by David Benyon if you're really interested in it.
  • 1
    But as others said: it probably comes down to whether or not the designers actually think about the interactions people will have to perform in their app or not.
    If they don't give a shit the ui will be shit as well
  • 1

    Pondering about it, I wonder about a menu option that reads like this:

    ON - Autosave Messages

    OFF - Autosave Messages

    But then, it isn't clear its a toggle..

    Or what state its in !

    Windows OS is particularly bad for that, since it isn't always clear if something is a toggle, or what state the toggle is in, before you click on it.

    And by then, it can be too late..

    Something plain, but not too long..

    A tick is nice, but there is no tick, how do you know there is supposed to be a tick..

    And if you have an empty box, how do you know the box is empty, and not already full !

    CURRENT TOGGLE STATE is ON - Autosave Messages

    CURRENT TOGGLE STATE is OFF - Autosave Messages

    Kinda tells everything, except maybe its a toggle menu option, you might just think, its to tell you its state, not to change its state.
  • 1
    @NEMESISprj hmm correction of first comment:

    "Search for resources about "Interactive Systems design": books or blogs or something like that for best practices. "
Add Comment