<?xml version="1.0" encoding="utf-8"?>

Switch to active state once a change is made

Switch to active state once a change is made Bad Practice
Switch to active state once a change is made Best Practice

Users who understand what's going on in the system feel more confident and trust it more.[1] This is especially important while they're making changes.

The state of the Save Changes button is a good way to communicate system feedback. Display the button as disabled before changes are applied. When information is modified, change the button state to active in order to bring it to users' attention. This will communicate to them that changes have been made and are waiting to be saved.

Improve your UX & Product skills with interactive courses that actually work