Choose against the task constraints
In this invented note editor, a confirmed save returns revision 12. A competing edit returns a version conflict instead, requiring the user to inspect both versions. The second situation is not just a louder success message. No measured completion-time benefit is claimed.
| Condition | Inline result feedback | Blocking dialog |
|---|---|---|
| Confirmed ordinary save | Show saved revision and let work continue | Acknowledgement may add a redundant step |
| Unresolved competing edits | Can expose a conflict review region | May suit a bounded decision if focus is managed |
| Unknown save result | Display uncertainty, not saved | A success-styled dialog would still be wrong |
Use concise inline feedback for revision 12. Present conflict resolution only when the user must decide what to retain, preserving both drafts. Avoid an extra OK step after every ordinary save; validate the actual write result before claiming completion.
Messages follow write outcomes
| Attempt | Result | Suitable feedback |
|---|---|---|
| S-A | Accepted as revision 12 | Saved; revision 12 |
| S-B | Version conflict | Review competing drafts |
| S-C | Response lost | Check saved state |
Which attempt may safely show saved?
Show the worked answer
S-A. S-B needs a decision and S-C needs reconciliation. Closing a message cannot turn either into a confirmed write.
Check the chosen interaction
- Ordinary success is readable without a mandatory acknowledgement.
- Conflict review preserves the user’s text and the competing version.
- If a dialog is used, its close behaviour and focus are tested.