Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I'd probably use chekboxes. Though mainly because of the width of the layout. Switches would be a bit wider. What's good about switches though is that they convey more of an on/off function.
Jilano2180311d@powerfulparadox That's most definitely true. "I don't know what I want but it's not that"
@Fast-Nop Fair point, but many things in life don't accommodate for that (e.g. traffic lights), so I thought it might still work when people are used to it.
That being said, it would also be possible to go from greyed out to coloured, I guess.
@Fast-Nop If the contrast is high enough color-blind people should be able to see which side of the switch is active and use the common convention of "left=off, right=on" to determine which options are enabled, unless someone was devious (and stupid) and reversed the meanings somehow.
@Jilano With traffic lights, you always have red at the top - and in many countries, colour blind people are not allowed to get a driving licence. But that's not a reason to limit accessibility unnecessarily in other domains like apps.
WCAG 2.1 clearly has the requirement to never convey meaning via use of colour alone. Colour plus something else is OK though.
Wack678311dI'd say it depends on your context. On laptop/desktop, I'd use checkboxes, while on mobile/native mobile a switch. But I guess this is up to your taste
@powerfulparadox That's the point - switches need an additional convention that is not visibly part of the UI. That's why I consider them as inferior to checkboxes.
But I guess in today's totally botched up smartphone world where you have to access a function by putting all five fingers and then doing galaxy style spirals inwards and outwards, usability just isn't important anymore.
@Fast-Nop You forget that checkboxes also have that same convention (why not have an empty box mean selected? it's a convention, too). It might feel more obvious for checkboxes, but it's fairly well established these days for switches, too. I wouldn't consider the switch to be much worse (if any) than checkboxes, and they have the potential advantage of disentangling the collection of settings from the potential perception that they are a heirarchical list (which checkboxes can imply).
Nanos854010dIf the choice is between only those two, then tick boxes.
I find switches can be confusing because it isn't always clear if a switch is on or off.
3rd option, stop using graphics and use old fashioned words !
Especially useful when for whatever reason, the graphics are not working..
Then you just have to make sure that logically, your yes and no match up with user expectations..
Screen saver = ON / OFF
Deactivate screen saver = YES / NO
First one is more easily understood than second one !
C0D44526510dIf it's mobile, I'm assuming so with the notifications....
Use switches with labels embedded s
Left side = off
Right side = on
If you want to be sure users understand what's going on, have the "on" turn green and "off" turn gray or something so it's feels faded out.
on touch open a dialog box which contains yes, no and close where no will be preselected, green and highlighted after clicking it close the dialog box without setting that bool true, make yes red and keep size of yes less than no. Finally after clicking close whole app should close. You can also display banner ads between yes and no keep no above and yes below the ads.
Nanos85409d> If you want to be sure users understand
> what's going on
I'm reminded of Windows 10 here, it has those funny slider switchy things, where you don't know if a feature is on or off, as it isn't clear from the colour choices.
Is dark grey on and light grey off..
Is my monitor setup correctly or is the colour off a bit, I still don't know !
Lets try it and see what happens..
Words, words would make it so much easier to understand.
Unless its something like: