Settings: autosave on change (remove Save button) #128

New issue

Closed

opened 2026-05-11 11:30:47 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-05-11 11:30:47 -07:00

Owner

Problem

Settings currently requires an explicit Save button click. This is a friction point — users change a setting and navigate away, losing the change with no feedback. Autosave on change is the expected pattern for preference UIs.

Acceptance criteria

All settings fields autosave to localStorage (and where applicable, the store) on change
Remove the Save button
Add a transient "Saved" confirmation flash (e.g. 1.5s fade) near the changed field so the user knows it worked
No data loss on navigation

From

kiwi UX audit (2026-05-11) — cf-a11y priority #4

## Problem Settings currently requires an explicit Save button click. This is a friction point — users change a setting and navigate away, losing the change with no feedback. Autosave on change is the expected pattern for preference UIs. ## Acceptance criteria - All settings fields autosave to localStorage (and where applicable, the store) on change - Remove the Save button - Add a transient "Saved" confirmation flash (e.g. 1.5s fade) near the changed field so the user knows it worked - No data loss on navigation ## From kiwi UX audit (2026-05-11) — cf-a11y priority #4