In the app I am working on the user is presented with a list of item on the left and a panel contained with input fields on the right. The user will navigate the list and edit pricing criteria for each item in the list. In order to make the process easier and smoother, I have been playing around with some different actions.

The first is having a Save and Cancel button so the user can save the data, and then have next and previous buttons to navigate the list.

The second is having a "Save & Continue", "Save", and "Cancel" button. This way the user can decide whether they just want to save the current item and remain viewing that item, or they can flow through the list by saving and continuing.

Is there anything wrong with having a "Save" and "Save & Continue" button?

  • You can call them "Apply" and "Save"? Feb 3, 2015 at 9:12

2 Answers 2


Can you support auto save in this context?
As long as users don't experiment with the data it would smooth the process. Make it even faster by providing a key sequence for the next button. If that would work, you can just have a status indication immediately adjacent to a 'next item' button, like the pattern illustrated below.

enter image description here

If you need to allow undoing changes (in response to @DaveAlger's insightful comment), you'll want to include:
- an undo/cancel option for that particular form (toward the bottom)
- and (optionally) an undo for each field when a change has actually been made

enter image description here

  • 1
    this is great - i understand the system without even reading any text at all
    – DaveAlger
    Feb 3, 2015 at 0:56
  • 2
    one other suggestion - people generally need a way to cancel out of things like this so make sure to provide a link that looks nothing like a button for that (just a simple underlined cancel word off to the side and they will find it if needed)
    – DaveAlger
    Feb 3, 2015 at 0:58
  • This is great thank you. I think ultimately this would be the desired direction to go in. But unfortunately it is to much work to fit in the development sprint at this moment, so I was trying to come up with a secondary option. Feb 3, 2015 at 19:18
  • If I get a chance, I'll add a "phase 1" version here ;) Feb 3, 2015 at 19:49

The general approach tends to be "Save" and "Next". There's an implicit assumption that the wizard saves when you move onto the next step. You can probably make it more clear by showing a "saved" notification "toast" message on the screen.

To be clearer, consider the following set

"< Previous" "Save" "Next >"

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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