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

I have a customers detail view with things like their name. At the top there is a toolbar where they can save, reload, delete etc...

On of the properties they can edit is a list of phone numbers. When someone adds or deletes or edits a number. Should this be automatically saved or should it be saved after the users clicks save on the customer itself?

share|improve this question

Be consistent throughout the interface.

If you have a save button related to the entire "customer detail view", then the save button should be used to save all information under it. To prevent errors of unsaved data, you can show an alert when the user changes data and tries to leave the screen.

However, I would argue that auto-saving is becoming an expected feature of web applications.

Related: Guidelines for when to auto-save settings vs "save" button and When to save data?

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.