The best user experiences are often built on small interaction details.

One example is the humble toggle switch.

It seems simple, yet it’s frequently implemented in a way that creates unnecessary friction.

Imagine opening your settings, turning on Notifications, enabling Auto-save, and activating Sync Across Devices.

Then you’re asked to click a Submit button.

It feels unnecessary because users naturally expect a toggle to represent an immediate action.

Why Users Expect Instant Feedback

A toggle is designed for binary decisions: ON or OFF.

When users flip a switch, their mental model is clear—they expect the system to respond immediately.

Introducing an additional Save or Submit step breaks that expectation and forces users to question whether their action actually worked.

Good UX reduces doubt.

Whenever possible, a toggle should apply changes instantly and provide subtle confirmation, such as:

  • A success toast
  • A status message
  • A visual state change
  • A loading indicator for network-based actions

This reassures users without interrupting their flow.

When Is a Submit Button Appropriate?

Not every setting should update immediately.

If users are editing multiple preferences at once or making changes that should be reviewed before applying, a Save or Submit button makes sense.

Examples include:

  • Profile forms
  • Multi-field account settings
  • Payment information
  • Preferences that require validation

In these cases, users expect to review everything before committing their changes.

Design for Expectations

One of the core principles of UX is aligning the interface with users’ mental models.

Toggles communicate immediate control.

Forms communicate delayed submission.

Mixing these patterns can lead to confusion.

Small interaction details often have the biggest impact on how polished a product feels.

The next time you design a settings screen, ask yourself:

“Does this action really need another click?”

If the answer is no, let the toggle do its job.

🚀 Every practical UX lesson we publish becomes part of UX Crumbs as we build it in public.

We’re creating a learning experience focused on real-world design decisions, one insight at a time.

🔗 https://www.uxcrumbs.app/waitlist