Please enable JavaScript.

Coggle requires JavaScript to display documents.

Heuristic Evaluation (10 Design Heuristics (Feedback (Support error…

- - - - Clear Language
      - Expected language
      - Be consistent within your software and with similar software
    - - Speak the user's language
      - Use things that we're familiar with in the physical world
    - - Form follows function
      - layout is driven by what people want to do
      - Proper signal to noise ratio
      - Don't add value when it will take away from user focus
  - - - Is it clear what I can do on this site?
        Is it large enough to encompass what I wanted to do and can it even do that?
      - Exits from mistaken choices, undo/redo, not forcing people down fixed paths
      - UI depends on the task.
        If it's something you seldom do --> constrained wizard.
        If it's something you do all the time or the set of things I want to do is large --> large alternative paths
      - The expert --> lots of freedom.
        The novice --> constrain.
      - Balance between constrained and freedom is key
    - - Keyboard shortcut
      - Recommendations
        
        Requires algorithm that gives you not only relevant, but also related material to your task.
        Hard to do
      - Good defaults w/ options
        
        Search box..
        type but also include radio button to most common choices
      - Ambient information to help make better choices
      - Proactivity
        
        Gives user a choice based on their decisions
    - - Bedrock to UI Design
      - Tells the user that what they are able to do is clear based on the UI shown
      - Good preview (picking documents on Word)
      - Clear navigation with proper context but that doesn't mean add extra unnecessary steps
  - - - Time
        
        If interaction happens immediately --> show outcome
        If interaction takes about a sec --> show indicator status (wheel of death)
        If it takes more than a sec --> progress bar, timer
        If it takes a good chunk of time --> def have a timer and progress bar
      - Space (how much storage you have left)
      - Change (made changes to a document and the program asks if you want to save)
      - Action
        
        (traffic lights are both color indicated but also location of light tells user what the light indicates for accessibility)
        
        Next steps (you've made an account and now what)
    - - Prevent data loss
        
        When you're about to save something that already exists, offer to overwrite, skip save, cancel completely, or use a unique name
      - Prevent confusing flow
        
        Would you like to save? Save, Don't Save, Cancel. Whats the difference between don't save and cancel?
      - Find GUI
        
        Command line requires you to remember specific syntax and it's not commonplace for the average user
      - Prevent bad data
        
        When user fills out a form, and they missed something, be specific and tell them what they need to do instead of just saying it's wrong
    - - Make the problem clear to help the user recovery, hyperlink to error, english language summary
      - Make form requirements clear
      - Show path forward. Give the user instructions to maybe fix the problem
      - Provide alternatives. Search UI, try typing this, etc
      - Recognize errors that users might not know about. Bad sites.
    - - Proper documentation
      - Learning by examples
        
        PHP, Adobe Lightroom
      - Help clearly
        
        EULA. Creative Commons summarizes the important parts of EULA and also the official version and also the code executable version
      - Help people have fun
        
        Easter eggs, humor