Switches are two-state controls that apply their change the moment they are flipped, with no Save button and no confirmation step in between. The eight blocks here are mostly about what surrounds one: an integrations directory where each card connects one app, a grouped preferences list with a frequency dropdown and a locked row, connected accounts with a count strip that follows the switches, a matrix with a switch at every event-and-channel crossing, a consent list sitting above one category that cannot be turned off, and the switch alone as a card, a tile and a settings row.
That immediacy is the whole contract, which makes it an obligation too. A switch sitting inside a form with a Save button is lying about when it takes effect, and if a change needs confirming, a checkbox is the honest control. Because it commits straight away, it also has to survive a write that fails, returning to its old position by itself and saying why, rather than leaving a state on screen that the server never agreed to.
One row per event and one column per channel with a switch at every crossing. The grid is the only layout that lets someone see an event is on for email and off for SMS without opening anything.
A grid of apps where each card carries a logo, a category and one control that connects or disconnects it. State is readable from the grid itself, so nothing has to be opened to check what is live.
A privacy screen listing optional tracking categories above one that cannot be turned off. The required row is shown on and disabled with a reason, because hiding it makes the list look shorter than the truth.
Linked social and sync accounts, each row carrying its handle, last sync time and status. A count strip above follows the switches, and an account that has broken offers Reconnect where the switch would sit.
A switch applies its change immediately: flipping it is the action, and there is nothing further to submit. A checkbox records an intention that takes effect when the surrounding form is saved, which is why it belongs beside a Save or Submit button and a switch does not. If a change needs confirming before it is applied, the checkbox is the correct control.
It should return to the position it held before rather than staying in the new one, because leaving it flipped shows a state the server never accepted. Pair the reversal with a message naming what failed and offering a retry, so the person is not left guessing. Showing a brief pending state while the request is in flight is fine; silently keeping the new position is not.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Switches are two-state controls that apply their change the moment they are flipped, with no Save button and no confirmation step in between. The eight blocks here are mostly about what surrounds one: an integrations directory where each card connects one app, a grouped preferences list with a frequency dropdown and a locked row, connected accounts with a count strip that follows the switches, a matrix with a switch at every event-and-channel crossing, a consent list sitting above one category that cannot be turned off, and the switch alone as a card, a tile and a settings row.
That immediacy is the whole contract, which makes it an obligation too. A switch sitting inside a form with a Save button is lying about when it takes effect, and if a change needs confirming, a checkbox is the honest control. Because it commits straight away, it also has to survive a write that fails, returning to its old position by itself and saying why, rather than leaving a state on screen that the server never agreed to.
One row per event and one column per channel with a switch at every crossing. The grid is the only layout that lets someone see an event is on for email and off for SMS without opening anything.
A grid of apps where each card carries a logo, a category and one control that connects or disconnects it. State is readable from the grid itself, so nothing has to be opened to check what is live.
A privacy screen listing optional tracking categories above one that cannot be turned off. The required row is shown on and disabled with a reason, because hiding it makes the list look shorter than the truth.
Linked social and sync accounts, each row carrying its handle, last sync time and status. A count strip above follows the switches, and an account that has broken offers Reconnect where the switch would sit.
A switch applies its change immediately: flipping it is the action, and there is nothing further to submit. A checkbox records an intention that takes effect when the surrounding form is saved, which is why it belongs beside a Save or Submit button and a switch does not. If a change needs confirming before it is applied, the checkbox is the correct control.
It should return to the position it held before rather than staying in the new one, because leaving it flipped shows a state the server never accepted. Pair the reversal with a message naming what failed and offering a retry, so the person is not left guessing. Showing a brief pending state while the request is in flight is fine; silently keeping the new position is not.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Connect the tools your team already uses.
Connect the tools your team already uses.
Connect the tools your team already uses.
Connect the tools your team already uses.
Connect the tools your team already uses.
Connect the tools your team already uses.