Simple answer, the law states that they must be off per default.
Privacy by default:
Accept all/reject all buttons are a nice touch, go ahead and use that!
As the most highly voted answer is simply false I am writing this answer just clarify the legalities in the EU.
Under GDPR there are 6 lawful bases for processing personal data. The two we care about are
Consent is something that is opt-in and allows a company to process personal data in nearly limitless ways. To ...
I suggest to add a top level selection between filter X or boosters using radio buttons. Then a secondary level underneath Boosters where they can be selected using checkboxes. If the Filter X radio button is selected, disable the Booster checkboxes.
Depending on whether you want a clear option to have neither Filter X nor Boosters you could add another ...
They should be off by default, AND there shouldn't be too many of them (max 3). There are some sites that do malicious compliance by giving EVERY SINGLE domain their site uses a separate toggle defaulted to on, which breaks the law and gives users that wish to disable them all a horribly designed user experience meant to just make them give up and allow ...
If it is not a confirmation pop/up (which you should try to avoid, since users tend to get them out of the way without reading the message within) the answer is no.
I have to say that I'm thinking about a switch as toggle. A switch does enable or disable something full stop. I doubt that a user would expect something else using a switch. If it triggers a ...
Technically it could, but it's not the expected behavior. When clicking on a toggle the user expects to switch from a state to another , he does not expect to get a pop-in. Except if it's an important warning really related to the state on wich the user have just switch on by clicking on the toggle , i would personally not recomend to use a toggle to ...
You can try removing the background color of the button to indicate inactive state. Having color on both the states is confusing because they both stand out equally. To further improve, use bold typeface for the active state.
A toggle having colour indicates that it is switched "on" - in this case, that means YES. You shouldn't need any further information.
The tick/cross icons can add a fun little bit of flavour to the toggles, but I believe that explanations for toggles generally aren't necessary - the Material guidelines for switches agrees with that idea.
Try adding interval controls only when a user asks to display them. Keep the fields open for input, and surface the option to save only after a user modifies the time interval grid.
I hope I understand your use case correctly, but here goes:
The initial display can be your default. If most users find it helpful, start with the checkbox enabled. That state ...
I suggest to clearly seperate Boosters and Filters if there are not compatible.
Here are 2 ideas :
with a tab system that force user to choose one group
Separate vertically both categories and mentioning it is an OR choice
If I understand correctly, it can be confusing for a user to enable a setting from a screen which only contains login information.
Nevertheless if this is mandatory and within actual context, I would put it within the white card, between the password field and login button so there is a hierarchy of actions (1. enter pwd, 2. choose setting 3. login and ...
The metaphor that comes to my mind is that of a bidirectional joystick or jog switch type control: At rest in a neutral, central position, and causing motion in the direction of either excursion (up or down, left or right).
If executed well, the action of the UI control you describe is very learnable by users, especially if you describe the electric window ...
From my point of view, changing switch button doesn't make it more understandable. If you are going to change it anyway other than a slider, I'd prefer something meant two-sided image/emoji (like gemini) to make it more understandable as it's a changeable item.
And as you say so, putting your name next to this slider icon, does make this icon more like your ...
I think of something like this:
Understandability of the entering mode: either Parent, or Children
Eliminate undefined state and possible confuse, when there are some values in the Children nodes, and the user enters Parent value
Clear UI due to hiding non-relevant input fields
Jumpy behavior of the switch control. The effect should be ...
Actions in table's rows are quite common, as each row represents some actionable domain entity.
One thing you should care of is the data in a row provides enough information on taking decision of making an action. So a user shouldn't dive into details to make a decision and turn back to perform an action.
You can see live example of this approach on the ...
Toggles can only be two way also they are tricky. I think what you looking for is a group button. It is way more intuitive than toggle (it clearly show what is selected, and are labeled), however group buttons require more space than toggle.
I will do it this way:
It seems you may have two issues: which segment is selected, and what can the user search on, especially if the user comes with an immediate intention to search.
In your mock, you have two different data sets, but you're using a control placement way to the right of the data, so to see at a glance which is selected, my eyes have to look right.
The search ...
It's definitely a challenge with toggle buttons. We had to use them in one of our projects and we assumed that indicating the active state by changing the background to the primary colour would be enough.
However, user interviews showed us that we were wrong. Whenever we had a collection of three toggle buttons, the user did not seem to be confused. When it ...
I think this is a very interesting case in understanding whether skeumorphism is the best approach for replicating a physical functionality digitally.
Another well-known example is the notorious volume control button which has a very good rationale in its physical implementation but not so much for digital controls (and same with toggle buttons).
There are ...
That NN/g article is correct, and the answer to your question is, Yes! :)
As also stated in, say, the Switch section of the Material Design Guidelines, the key behavior of a switch is that "[w]hen a user toggles a switch, its corresponding action takes effect immediately."
Every time I've discussed this aspect with fellow Ix designers, we agreed that "...
The examples the "off" switches do not have enough contrast against the background. They look to me as if the option was not only "off" but "disabled" as well.
And I would go with the plain switch or the v/x option.
For 3, all you need is another option called 'Others' or 'Unspecified' as a child. And keep that unchecked while the rest are selected. There is no harm in adding a few additional options if those make sense. At the heart of it all, the tree structure should be clear to the users.
Including a fourth state is definitely not recommended because no one will be ...