Switches

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.

24 blocks

Integrations

App directories where connecting is a server call and should say so

Integrations, shelf

Directories where the result of connecting should be visible at once

Integrations, ask first

Apps that read workspace data and should ask before they connect

Email preferences

Email settings that save themselves: grouped rows, a real frequency listbox and a required row that explains itself

Email preferences, pause

Inboxes that need a break: pause everything without losing a choice

Email preferences, forecast

Showing what the choices add up to before they arrive

Connected accounts

Social and sync settings where pausing, resuming and repairing an account are server calls

Connected accounts, health

Seeing the state of every account at a glance

Connected accounts, fix first

Putting the broken account in front of the person

Notification settings

Per-channel delivery as an accessible grid: one row per event, one column per channel

Notification settings, channels

Turning a whole channel off without losing the picks

Notification settings, preview

Choosing by the message instead of the channel name

Data & privacy

Consent and tracking choices that save as you go, over one that cannot be turned off

Data & privacy, receipt

Showing exactly what leaves the device next to the switches that decide it

Data & privacy, levels

Three presets over the details: most people pick a level and stop

Switch card

One connection that needs a mark and a line, with a status that means something

Switch card, preview

A switch whose effect is visible: the week it adds trips to

Switch card, fold

Off should be quick and forgiving: no confirm, a way back

Integration card

App directory tiles where the switch and Manage are separate controls

Integration card, setup

Connections that need one answer first

Integration card, pulse

Showing what the integration does so the switch has a visible cost

Integration row

Settings lists of connected apps: the integration on one line, with Manage that works

Integration row, services

One account with several services under it

Integration row, sync

Integrations whose value is freshness

01

Using Switches

Reach for it when

  • A setting that takes effect the instant it is flipped: visibility, a digest, a feature
  • Connecting or disconnecting an integration from a directory
  • A grid of events against channels, where every crossing is independent
  • Consent, where someone should see everything they are agreeing to at once

Reach for something else when

  • Options submitted with the rest of a form: checkboxes read as pending until you save
  • A destructive or irreversible change: a confirm dialog, since one stray tap should not be the whole interaction
  • Picking one mode out of several: a segmented control or radio group, because a row of switches lets someone turn all of them off
02

Where it shows up

01

Notification channel matrix

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.

02

Integration directory

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.

03

Consent preferences

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.

04

Connected accounts

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.

03

Questions

What is the difference between a switch and a checkbox?

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.

How should a switch behave if saving the change fails?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.