Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 1
    A dialog isn't worse than throwing away the user's work, but it would be worse than saving what the user is working on as a draft so they can come back to it later. Saving something as a draft can require a LOT more labor (and regression testing; especially regression testing) than a dialog, depending on how "save as draft" is implemented. Commented Jul 7 at 14:17
  • 1
    And there can be security implications for saving something as a draft (again, depending on implementation). You don't want sensitive information saved to a client machine unless it is properly guarded. Commented Jul 7 at 14:19
  • 1
    Users/stakeholders have already explicitly told OP to implement the confirmation dialog. Instead of implementing a random UX receipe, we have to get approvals and reconcile the changed design. Commented Jul 7 at 15:01
  • 1
    I don't believe the app should overinterpret what the user wants it to do. If they tell it to close the form, that's what the app should do. It shouldn't try to read their minds, "Oh, they probably also wanted to save the changes, let's do it silently just in case". It's medical data. There should be nothing implicit about submitting such sensitive information. It is your job as a medical institution employee to take personal responsibility and explicitly submit the data, not our app's job. The app's just a tool Commented Jul 8 at 14:25
  • 1
    @SergeyZolotarev the suggestion here is to save a draft, not to submit. Commented Jul 8 at 22:44