Ancestors

Toot

Written by olia lialina on 2024-11-11 at 13:27

In my interface design class, talking about radio buttons, check boxes, menues, switches dilemma, i open material design guidelines 😲 🤷‍♀️ https://m2.material.io/components/checkboxes#usage

why "allow notifications" is not a switcher?

why "allow notifications" needs a twin "turn off notifications"?

=> View attached media

=> More informations about this toot | More toots from GIFmodel@olia.geocities.institute

Descendants

Written by Daniil Baturin on 2024-11-11 at 14:09

@GIFmodel Because if you are Google, surely you don't want to make it obvious how to turn off notifications, do you?

You are thinking like a decent person, but to understand Google's design, you need to be thinking like Google. ;)

=> More informations about this toot | More toots from dmbaturin@functional.cafe

Written by Dragan Espenschied on 2024-11-11 at 19:15

@GIFmodel

This example is quite chaotic and even made it into the following version of the specification, Material 3:

https://m3.material.io/components/radio-button/guidelines#3e7c43e7-66e0-4c40-8a66-ca6389875b3f

On the other hand there's a quite sensible section on switches/toggles that clearly distinguishes "binary" and "opposite" options:

https://m3.material.io/components/switch/guidelines#59aa5700-2061-4f12-ad17-3afeb6b1c805

=> More informations about this toot | More toots from despens@post.lurk.org

Written by Hart of the Wud on 2024-11-11 at 19:41

@despens @GIFmodel I am perhaps very old, but I find most toggle switches completely unusable unless they actually have labels on both sides. Simply changing color and moving right-left is totally meaningless to me. The only exception is when there's some obvious feedback that happens when you operate the switch - like the light switch in a room.

=> More informations about this toot | More toots from praxeology@post.lurk.org