In our web application we have a number of pages to do with user settings, in different categories. For most of them we have a display page with an edit button/link, which takes them to a form which has a cancel/save exit path.
However, for one category of settings we do something different. For the alerts & notifications settings we show all the alerts they can have, and present the controls to turn them on/off individually right there, as well as change their respective options (eg. email address to use as destination). There is no save button/link, the changes take effect immediately. We did this because the typical scenario is the user will want to tweak just the one alert setting, rather than review and edit the lot as a batch. We also recognised that a “save” button would likely be below the window-fold and thus be missed, and we really didn’t want to put a save button against each set of alert settings.
We’re a bit worried the user might be puzzled by the lack of a save button.
What are some guidelines and arguments for and against some setting changes having an immediate effect?
You need to be consistent. Changing what people expect from your application confusing and not a good idea.
If you are saving automatically in one section, why not do it in all of them? If there is a good reason to have the save button(s), then why not have them on all the settings pages?
Many applications break up settings pages to logical groupings and then have a save button for each group. I haven't found it visually ugly, and it is clear what to do. Definitely a better option than only at the end of a long list.
Correct answer by JohnGB on December 23, 2020
For me Auto-save works. This is my scenario and my reasons for implementing it.
Reasons for AutoSave.
Answered by Developer on December 23, 2020
In my opinion, auto-save should be avoided:
We designed a timesheet module for a client that auto-saved entries. The client loved it but then validations kicked in and turned the table up-side-down. Some of the fields were required to be mandatory dynamically i.e. based on the selection of another field. If the user does not captures mandatory data and navigates away, the system quietly ignored the entry. There was no easy fix and we had to introduce the 'Save' button.
Answered by Adeel on December 23, 2020
Aside from consistency, it should also check for platform from your analytics report. If most of your audience is from a macOS background you may want to consider using auto-save since the behaviour of most applications and dialog boxes on macOS is to automatically save.
For Windows users at least most would still be in the Windows 7 and below frame of mind in which case automatic save isn't the norm for most dialog boxes.
Answered by Archimedes Trajano on December 23, 2020
In ancient times, documents would have two states: the "saved" state on disk, and the state being edited. I would suggest that's often a good model, even for on-line applications. To avoid having people lose their work if their connection goes down, it may be good to have the server keep an up-to-date copy of the state being edited, but the "saved" state should generally only be updated if someone affirmatively requests that.
When closing a window after some state has been modified, a user should be allowed to abandon changes, apply changes, or keep as draft. If the user opts for the latter, or if the connection is lost, the next time an attempt is made to edit the state the user should be explicitly formed that the system is retrieving a saved draft.
I dislike having some kinds of changes to a form auto-applied and others not; if certain changes must be auto-applied, I would suggest that rather than using [e.g. a checkbox or radio button, one have a "submit"-style buttons for "Turn XXX on" or "Set mode to YYY".
Answered by supercat on December 23, 2020
Consistency is definitely a must. However, if one group of settings warrant a toggle on/off action rather than actually typing into a set of fields, it may be ok to have these save automatically on each change.
If you are using a toggle style switch it is expected that once you flick it, the action has been saved... Think about turning on or off a light. You could symbolize that it is being save by a short animation or notification after it has been toggled.
You also need to think about what type of users you have. Do they expect things to be saved automatically or do they need the psychological closure of completing the actions by clicking a save button.
It is becoming more of a common practice to use autosave within applications. Google uses autosave for most of their apps but they also use a 'save button' where needed. You could argue that 'web savvy' users would be more used to autosave but 'less web savvy' users may still expect or want to click a button to feel secure that their efforts have been saved.
Answered by JustinRob on December 23, 2020
2 Asked on October 31, 2021 by tal-blizowsky
3 Asked on October 31, 2021 by naveed-iqbal
4 Asked on October 31, 2021
1 Asked on October 31, 2021 by nick-cipher
1 Asked on October 31, 2021 by husseinsd
2 Asked on October 31, 2021 by doubleclickonthis
3 Asked on October 31, 2021
2 Asked on October 31, 2021
1 Asked on October 31, 2021 by ivan-kulezic
1 Asked on October 31, 2021 by jon-sud
2 Asked on October 31, 2021 by lea-grossman
3 Asked on March 2, 2021 by zirnamaraji
2 Asked on February 18, 2021 by swathi
2 Asked on February 18, 2021
1 Asked on February 16, 2021 by harshal-parekh
1 Asked on February 14, 2021 by estela-gaspar
1 Asked on February 12, 2021 by user133718
Get help from others!