- Taschenbuch: 559 Seiten
- Verlag: Morgan Kaufmann (14. April 2000)
- Sprache: Englisch
- ISBN-10: 1558605827
- ISBN-13: 978-1558605824
- Größe und/oder Gewicht: 19 x 3,2 x 24,1 cm
- Durchschnittliche Kundenbewertung: 8 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 203.314 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
GUI Bloopers: Don'ts and Do's for Software Developers and Web Designers (Morgan Kaufmann) (Englisch) Taschenbuch – 14. April 2000
Dieses Buch gibt es in einer neuen Auflage:
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
In GUI Bloopers, consultant Jeff Johnson uses 550+ pages to illustrate common pitfalls in user interface design, the all-important iceberg tip that end users confuse with applications and that developers confuse with end users. Reporting on 82 incidents of bad design, Johnson manages to cover the essential point of his message: software designers should think of their user interfaces from the user's point of view. Not profound, but profoundly overlooked in most low-end to mid-range development efforts. His codification of GUI design in eight predictable principles will help GUI newbies realize that the customer must be pleased with the product. Of course, the customer doesn't always understand what he or she wants. Hence, GUI development is iterative. When the customer is not at hand, a surrogate will do, so usability testing is essential.
The bloopers include mistakes in window design, labeling consistency, visual/grammatical parallel construction, coherence of look and feel, and clarity. Most perceptively, Johnson observes that CPU speed in the development group hides many design mistakes. Moreover, context-scoping, already a subtle problem in software design, must be implemented in GUI design. Input error handling is the most psychologically sensitive of all GUI design characteristics. User error messages can easily be too vague or too specific, and diagnostic error messages should be user-manageable, if not actually user-interpretable.
Like the Hollywood outtakes that gave us the "blooper," the entertainment quotient here is measured in mistakes, not successes. Teaching by counter example rather than by example at an estimated ratio of three to one, Johnson panders to our invertebrate instinct to measure our own successes by someone else's failure. To his credit, he recognizes that user interfaces include pedestrian texts (like his) as well as graphical interfaces for computer applications. His self-referential style gives the book an egocentric slant, but he is both priest and practitioner: he submitted a draft to usability testers and reports the results in an appendix. One criticism was that there were too many negative examples. Hmmm.
Thanks to other tester comments, GUI Bloopers is a browsable book, allowing the few nuggets of wisdom to be located. For the most part, the book's value can be captured by reading the seven-page table of contents carefully. --Peter Leopold
"Better read this book, or your design will be featured in Bloopers II. Seriously, bloopers may be fun in Hollywoodouttakes, but no movie director would include them in the final film. So why do we find so many bloopers in shippedsoftware? Follow Jeff Johnson as he leads the blooper patrol deep into enemy territory: he takes no prisoners but revealsall the design stupidities that users have been cursing over the years."-Jakob NielsenUsability Guru, Nielsen Norman Group "If you are a software developer, read this book, especially if you don't think you need it. Don't worry, it isn't filled with abstract and useless theory--this is a book for doers, code writers, and those in the front trenches. Buy it, read it, and take two sections daily."-Don Norman, President, UNext Learning Systems, theorist (The Design of Everyday Things), and doer (The Invisible Computer)Alle Produktbeschreibungen
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
I was at the session at the Computer Human Interaction conference in Holland where Jeff Johnson spoke. But another Jeff, Jeff Raskin also spoke and showed how some of Johnson's examples could be improved.
Raskin also introduced a book, The Humane Interface, somewhat deeper than this one, that helps you to really understand Web design. I'd reccomend reading and understanding Raskin's book so that you can see the few places where Johnson's ideas don't quite work. Then you can use this book, which is 95% right.
This book is by a pro whose career has been spent in designing interfaces and correcting the errors others make. He knows what he's doing, and we'd all be a lot better off taking his advice.
If you are designing information-based products that interact with people, you should first understand every point GUI Bloopers makes. This is a how-to, with lots of good examples, clearly explained. It is neither a work of psychology nor does it delve deeply into reasons why things work or don't. Read GUI Bloopers along with Norman's delightful book, The Design of Everyday Things (for motivation) and Raskin's thoughtful and thought-provoking The Humane Interface (for future directions).
This book made it instantly into the short list of my top recommended books for people who design interfaces. Get it, read it, follow it. Your customers will thank you.
Möchten Sie weitere Rezensionen zu diesem Artikel anzeigen?