I identified as the most preferrable strategy for user not to lose their data implementation of confirmation/discard dialog when exiting original one.
I expect a few more form dialogs to emerge in the app though, for example editing of the profile.
Nielsen Norman Group's research supports the use of confirmation dialogs, but they also point out not to overuse them, so they do not lose significance (see https://www.nngroup.com/articles/confirmation-dialog/). I feel the same, I don't want to add Confirmation/Discard dialog everywhere. I believe if 'post' is going to be the most significant part of the application, it makes sense to put a confirmation/discard dialog there, but I feel less positive about putting it also on profile editing.
My question therefore is, assuming that we do not want to use confirmation/discard dialogs everywhere in the app, what's the preferred strategy for the rest of the forms/dialogs?
This is what I can't decide about:
- User can close dialog accidentally, open it again, but realizing that they lost their editing and data - getting annoyed.
- User can close the dialog as an act of discarding, but after a moment opening it again, expecting original data, but seeing the last uncommitted changes from the previous editing - getting confused.
What could be the ratio of these two scenarios occurring?
I noticed that most of the big web platforms do not preserve changes in their secondary (in terms of importance) dialogs. I wonder if it is based on a UX decision or if it makes just more sense in their scaled implementation.
For more context: Esc, Click on overlay/backdrop, and Close button (that I am yet to put everywhere) do close the dialogs.