I've found that having a good undo is far, far better than a commit step. I think the best ux would be - Apply changed immediately. - Provide indication that t

I've found that having a good undo is far, far better than a commit step. I think the best ux would be - Apply changed immediately. - Provide indication that the change was applied (maybe pop a checkmark our for a second or two) - Provide an undo that at least revertes to the state when the dialog was opened, but ideally even be able to recent to snapshots from before previous changes. (So that if you close the dialog then decide you don't like it you can go back). COMMIT is useful in databases because you have made a "permanent" change and for atomicity reasons. If you make undo effective and there is no concurrent access it is unnecessary.