Hello! We’re working on a desktop app design. Initially, we had the Save Changes button at the top of the application, like so…
This button would apply to all of the form elements on the page, even those in different categories. For example, you could make changes to your personal information, then update your privacy settings, then your Date and Time settings, and finally click Save Changes.
This pattern seems to have some drawbacks:
- Form validation errors are difficult to manage, especially if the inputs are in a category that’s not selected.
- Generally speaking, for forms, the save button is at the bottom. I’m worried that this might be confusing for our users.
I’m trying to come up with a a logical way of selecting where the save button goes. Here’s my first attempt, and I’d love your feedback:
RULE #1: If the submit button is associated with a form, it should be at the bottom left of the form, or full width.
RULE #2: If the submit button is associated with a document within an application, then it should be on top. Examples would be:
- A document in Google Docs
- A page in Confluence
- A workflow in Hubspot
What I would LOVE would be an article or reference where someone smarter than myself has written about this.