← Back to Catalog

Apply versus save prefer autosave

apply-versus-save-prefer-autosave

Apply versus Save; prefer autosave; if not, Save + success/error via message bar or confirmation toast.

Description

Fluent distinguishes Apply versus Save by scope and prefers autosave so users are not left wondering whether edits stuck. Without autosave, Save must report success or error through a message bar or confirmation toast after the commit. Apply when choosing save patterns in Fluent settings and editors. Fail mixing Apply and Save scopes, or a Save path with neither autosave nor success/error feedback after the action.

When to use

Choosing Apply versus Save and feedback after edits in Fluent settings.

Not when

Transient Message-only important failures — use dialog guidance instead.

Agent hint

Prefer autosave; if Save, confirm success or error via message bar or toast.

Pass

Apply vs Save is used for the right scope; autosave is preferred; without autosave, Save reports success/error via message bar or confirmation toast.

Fail

Apply/Save mixed up; no autosave and no success/error after Save.

Citations

Open UX · cited UX rules agents audit against

Privacy · Sources ·