Good point. IMO, Anki shouldn’t even have a “Save” button, and just save the changes directly…
Yes, this is one of the solutions that I initially suggested.
The idea behind the story was to say that no matter how you design your interface, some users will always understand / use it poorly, or in an unintended way.
I’ll be a bit nitpicky but it seems that the interface worked extremely well in this case. Good interface helps users do what they want, in this case they wanted to get rid of the popup and they seemed to have been able to do so very efficiently. In a similar fashion, the interface should help the user save the settings efficiently. A save button in a regular position is a perfect way to do that, but silent saving, along with the reset buttons, is common as well these days.
confirmation pop-ups are a poor UI design strategy.
Confirmation popups are very useful for settings that are more complex. If you spend a while changing a setting and then decide that you don’t want to have the change, you can simply discard your changes in the confirmation popup. If you don’t have that option, you have to recreate your setting manually. There are alternatives such as drafts or undos, but these are quite unconventional in settings.
Besides, a lot of GUI software uses confirmation popups. How can you just say that these people have been doing it wrong for years. Event CLI uses comparable confirmations for actions, as in
delete file? yN.
We are talking about paying attention to a small action that is actually not that frequent while creating cards requires a lot more attention. Just pay attention.
You know, I actually don’t think that paying all of your attention would help. You’d have to know exactly how Anki deals with deck settings. Here’s two windows, deck options, and a an equalizer from my DAW. Both are windows with preset toolbars. Notice how both have the dropdown list with a preset, and a menu with various operations on presets. This pattern is very common in various software such as image or audio editors.
My DAW uses a menu but it’s not uncommon to have save buttons as well:
Guess what? The save preset option saves the preset. If I don’t save the preset and close the window, my settings are still preserved. I don’t need to press any save buttons to have the settings that I changed. Tell me, how the user is supposed to know that the button that is situated where the “save preset” option is commonly situated and that has a dropdown with stuff like “add preset” and “rename preset” is required to also save settings for the current deck?