GUI bloopers 2.0 common user interface design don't and dos
Is your application or Web site ready for prime time? A major revision of a classic reference, GUI Bloopers 2.0 looks at user interface design bloopers from commercial software, Web sites, Web applications, and information appliances, explaining how intelligent, well-intentioned professionals make t...
Autor principal: | |
---|---|
Formato: | Libro electrónico |
Idioma: | Inglés |
Publicado: |
Amsterdam ; Boston :
Elsevier/Morgan Kaufmann Publishers
c2008.
|
Edición: | Updated and rev., [New ed.] |
Colección: | Morgan Kaufmann series in interactive technologies.
|
Materias: | |
Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627306106719 |
Tabla de Contenidos:
- Front Cover; GUI Bloopers 2.0; Copyright Page; Contents; Acknowledgments; Introduction; Chapter 1: First Principles; Introduction; Basic Principle 1: Focus on the users and their tasks, not on the technology; Basic Principle 2: Consider function first, presentation later; Basic Principle 3: Conform to the users' view of the task; Basic Principle 4: Design for the common case; Basic Principle 5: Don't distract users from their goals; Basic Principle 6: Facilitate learning; Basic Principle 7: Deliver information, not just data; Basic Principle 8: Design for responsiveness
- Basic Principle 9: Try it out on users, then fix it!Chapter 2: GUI Control Bloopers; Introduction; Using the wrong control; Blooper 1: Confusing checkboxes and radio buttons; Blooper 2: Using a checkbox for a non-ON/OFF setting; Blooper 3: Using command buttons as toggles; Blooper 4: Using tabs as radio buttons; Blooper 5: Too many tabs; Blooper 6: Using input controls for display-only data; Blooper 7: Overusing text fi elds for constrained input; Using controls wrongly; Blooper 8: Dynamic menus; Blooper 9: Intolerant data fi elds; Blooper 10: Input fields and controls with no default
- Blooper 11: Poor defaultsBlooper 12: Negative checkboxes; Chapter 3: Navigation Bloopers; Introduction; Not showing users where they are; Blooper 13: Window or page not identified; Blooper 14: Same title on different windows; Blooper 15: Window title doesn't match command or link; Leading users astray and not showing the way; Blooper 16: Distracting off-path buttons and links; Blooper 17: Self-links; Blooper 18: Too many levels of dialog boxes; Poor search navigation; Blooper 19: Competing search boxes; Blooper 20: Poor search results browsing; Blooper 21: Noisy search results
- Chapter 4: Textual BloopersIntroduction; Uncommunicative text; Blooper 22: Inconsistent terminology; Blooper 23: Unclear terminology; Blooper 24: Bad writing; Blooper 25: Too much text; Developer-centric text; Blooper 26: Speaking Geek; Blooper 27: Calling users "user" to their face; Blooper 28: Vague error messages; Misleading text; Blooper 29: Erroneous messages; Blooper 30: Text makes sense in isolation but is misleading in the GUI; Blooper 31: Misuse (or nonuse) of "..." on command labels; Chapter 5: Graphic Design and Layout Bloopers; Introduction; Bad layout and window placement
- Blooper 32: Easily missed informationBlooper 33: Mixing dialog box control buttons with content control buttons; Blooper 34: Misusing group boxes; Blooper 35: Radio buttons too far apart; Blooper 36: Labels too far from data fi elds; Blooper 37: Inconsistent label alignment; Blooper 38: Bad initial window location; Troublesome typography; Blooper 39: Tiny fonts; Chapter 6: Interaction Bloopers; Introduction; Deviating from task focus; Blooper 40: Exposing the implementation to users; Blooper 41: Needless restrictions; Blooper 42: Confusable concepts; Requiring unnecessary steps
- Blooper 43: Asking users for unneeded data