<aside> 💡 This page contains all the research and preparation for this article. Feel free to use any of this information for your own purposes! If you cite the published article, I'd ask that you'd please credit me, preferably providing a link to the article or a link to my website at https://www.sergix.dev. Not required, but much appreciated!
Question: How do you best clarify the primary action the user should take?
Primary action: intended action of a section, such as a dialog confirmation or form submission; "final" action; primary goal; typically positive (https://www.lukew.com/ff/entry.asp?571)
Secondary action: less utilized action; typically negative; alternative to the primary action (https://www.lukew.com/ff/entry.asp?571)
Tertiary action: miscellaneous actions, not the intended (https://uxdesign.cc/ui-cheat-sheets-buttons-7329ed9d6112); can have similar style as a secondary action, but need to carry different visual weight (https://uxmovement.com/buttons/visual-weight-of-primary-and-secondary-action-buttons/)
dangerous actions as the primary/default action
Windows User Experience Guidelines — OK first
Apple Human Interface Guidelines — OK last
GNOME — OK last
Material (Android) — OK last
Linux — OK first
Java — OK first
NY State UX Toolkit — OK first (https://apps.labor.ny.gov/ux/doc/v1/design-primary-actions.html)
https://lawsofux.com/jakobs-law — use patterns common in other applications
For more than 2 options, the first and last options should be the most important actions the user should take — https://lawsofux.com/serial-position-effect
visual weight (https://www.lukew.com/ff/entry.asp?571)