User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My application has auto-saving and versioning/revisioning (keeps a copy of every change).

It also has the ability to save draft versions of things, which I define as "something that you want to save but isn't valid". By valid I mean, normally say a First Name is required, but this object doesn't have one, but you want to save it anyway (like a Gmail draft).

The question is, is there a benefit to the user of keeping all the draft versions in addition to the regular (valid) versions?

The drawback would be that, in their list of revisions they can go back to, all the draft ones would be there too. Do they want to rollback to a draft version?

share|improve this question

As long as rolling back doesn't immediately remove more recent versions, there's no reason not to give access to drafts. Giving users more choice is always a good idea as long as it doesn't impede previous functions.

Based on your concerns it sounds like you should:

  • Clearly label previous versions that are drafts, possibly with mild highlighting or a red "draft" tag
  • Give users a check box to either hide or show drafts

It probably makes sense to hide all drafts (except for the most recent version, if it is a draft) by default, and let users use the check box to "show drafts."

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.