[HN Gopher] Usability heuristics for user interface design
       ___________________________________________________________________
        
       Usability heuristics for user interface design
        
       Author : boraoztunc
       Score  : 32 points
       Date   : 2023-04-16 18:11 UTC (4 hours ago)
        
 (HTM) web link (www.1984.design)
 (TXT) w3m dump (www.1984.design)
        
       | turtleyacht wrote:
       | Apps ought to be designed with these UI guidelines in mind:
       | 
       |  _Here 's what I'm working on right now, and how long it may
       | take._ Status feedback fosters trust.
       | 
       |  _I speak your language._ Jargon is confusing.
       | 
       |  _You can take things back._ Undo grants freedom from
       | frustration.
       | 
       |  _I behave just like the others._ Inconsistent conventions
       | increase cognitive load.
       | 
       |  _Are you sure?_ Confirm before commit. Eliminate slips  &
       | mistakes. A _slip_ is an unconscious, inattentive error. A
       | _mistake_ is a conscious error, but domain (mental model)
       | mismatch.
       | 
       |  _I auto-populated these fields._ Design so interface favors
       | recognition over recall.
       | 
       |  _Ways to make you more efficient._ Enable power-users.
       | 
       | Aesthetic & minimalist, but not necessarily flat design.
       | 
       |  _I 've written stuff so you can learn more about me._ Provide
       | help and documentation.
       | 
       | ---
       | 
       | As I worked on this, I realized some of this could improve
       | communication between people.
        
         | prime17569 wrote:
         | Apple's old OS X Human Interface Guidelines (pre-OS X
         | Yosemite)[1] said almost exactly the same things.
         | 
         | https://web.archive.org/web/20140603021344if_/https://develo...
        
         | prox wrote:
         | _Pliancy_ : this is something you can manipulate
        
           | turtleyacht wrote:
           | Thank-you. Porcelain vs plumbing
        
         | kitsunesoba wrote:
         | > You can take things back. Undo grants freedom from
         | frustration.
         | 
         | > Are you sure? Confirm before commit. Eliminate slips &
         | mistakes. A slip is an unconscious, inattentive error. A
         | mistake is a conscious error, but domain (mental model)
         | mismatch.
         | 
         | Additionally, don't use the former as a replacement for the
         | latter. While a way to undo destructive things should be
         | present wherever possible, they should also be prevented from
         | happening in the first place where reasonably possible.
         | 
         | Google apps are bad about this. Rather than add a small amount
         | of friction to avert common types of disasters, they tend to
         | lean on undo, which works fine until you end up too distracted
         | to notice the little "X happened [Undo]" notification until you
         | realize what happened a week later when the action you
         | accidentally committed has become irrevocable.
        
       | ChrisMarshallNY wrote:
       | I've followed these basic principles for decades (Full
       | disclosure: I've taken NNG courses -quite a few).
       | 
       | They're really just basic common sense, but you know how it
       | goes...
       | 
       |  _> Common Sense: So rare, that it 's a super power._
       | 
       | https://i.pinimg.com/736x/2b/ac/61/2bac61a609a63386b8342c757...
        
       ___________________________________________________________________
       (page generated 2023-04-16 23:00 UTC)