Yes. Toggles are unnecessary, a phenomenon of weird nerds. Just match the system settings and you’re fine.
Do you mean altogether unnecessary, or unnecessary as a persistent toggle on the main screen?
If you’re talking about the former I’d disagree, easiest way to explain is with my own real-world example.
I put basically everything in dark mode, but our ticketing system’s website I put in light mode (even though they have a dark mode) because their dark mode looks like shit.
our ticketing system’s website I put in light mode (even though they have a dark mode) because their dark mode looks like shit.
Once, a client asked me to put a spinner on a page that was slow to load. I made the underlying SQL query 2000 times faster instead.
A toggle is not the best solution to your problem.
Maybe there’s a case to be made for a theme setting on a screen somewhere. Or as others have said, this could be set at the browser level per site.
I just think having a toggle up in the header is sort of a UX waste.
I think the better alternative would be for browsers to have some kind of per-site override instead of relying on every single site building the same system and putting the option in a different place.
If a setting is universally supported by all sites (which dark mode should be, along with the other common accessibility flags), it shouldn’t be something that the sore needs to control.
It probably wasn’t clear in my post but I’d be happy with the toggle being in the browser (not something I’ve historically thought about but a great idea), it was more about the existence of a toggle.
I do agree with @jaredwhite@humansare.social that having the toggle in the header is a waste of space. Same with horizontal tabs.
Why is this so messy? I understand nothing from it.
When I loaded this page on my phone (Firefox on Android), the colors changed several times during loading, then the layout shifted so that only a third of the screen was used for text. That makes taking the author’s thoughts on web design seriously difficult.
