Like I said in the podcast there are definitely some bad reasons to use a toggle switch (they’re cool, different, fun). The so-called good reason to

Why toggle switches suck (and what to do instead)

submited by

Style Pass

2024-07-08 13:00:05

Like I said in the podcast there are definitely some bad reasons to use a toggle switch (they’re cool, different, fun). The so-called good reason to use one being that you need the action to take immediate effect.

But my problem is that this describes the outcome. It doesn’t explain why a particular action needs to take immediate effect in the first place.

But if the request is slow there’s a risk the system won’t save the change. This could be catastrophic or just annoying depending on the use case.

Some settings have 2 options (and use a toggle switch) and some have more than 2 options (and don’t). Notice how Airplane Mode is on and Wi-Fi is off.

Now admittedly I’m usually the first one to challenge “it must be consistent” but if you can be consistent you should be consistent.

And usually when a designer tries to avoid a page refresh it creates all sorts of issues that degrade UX that didn’t exist in the first place.