- Taschenbuch: 352 Seiten
- Verlag: New Riders (Dezember 2001)
- Sprache: Englisch
- ISBN-10: 0672321513
- ISBN-13: 978-0672321511
- Größe und/oder Gewicht: 17,8 x 2 x 22,9 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 1.274.103 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Designing from both sides of the screen: A Dialogue Between a Designer and an Engineer (Englisch) Taschenbuch – Dezember 2001
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?
Designing from Both Sides of the Screen: How Designers and Engineers Can Collaborate to Build Cooperative Technology is a must-have book for anyone developing user interfaces (UI). The authors define a seemingly simple goal, the Cooperative Principle for Technology: "[T]hose who are designing, building, or managing the development of technology should teach their products to follow the same basic rules of cooperation that people use with each other."
In the first section, they show lots of good and bad UI examples from different devices (PC, PDA, photocopier, even a dashboard). Bad examples include confusing pop-ups, crowded menus, and hilarious error messages like this one from Yahoo! Messenger: "You are not currently connected. Please click on Login and then Login to login again."
The book gives succinct design principles like, "Treat clicks as sacred." A violation of this would be those dreaded "Do you really mean it?" pop-ups. Using a butler as an analogy, they point out that he'd soon be out of a job if he questioned, "Madam, are you sure you want me to answer the door?" A design guideline says, "If you have an Undo feature, there is no need to break the users' flow to ask them whether they really want the program to do what they just asked it to do." Design guidelines like this appear in the margins throughout the book for easy reference and are gathered in a handy appendix.
The second section goes into detail on the creation of the authors' own project, Hubbub, a multidevice instant-messaging application. Whenever a step in the process reflects the application of a design principle, it's called out in purple in the text. Thus, the book itself is an example of a cooperative UI that helps readers keep ideas organized as they read along.
Even if you're not developing user interfaces, you'll enjoy this book. There are many moments of recognition when you see just how flawed your favorite, or most hated, everyday application/operating system/Web site is, and how easily it could have been improved. And you may even find the principles of Cooperative Technology informing nontechnological areas of your life. The authors make politeness and the anticipation of the needs of others seem logical, feasible, and elegant. --Angelynn Grant
This book not only offers a sound and proven philosophy for designing and building software, it explores the dialog between designer and software engineer, and offers insights which when applied will facilitate a higher degree of collaboration between them. With a minimal understanding of the values and motivations of one another, these people are often team members standing in adversarial relation to each other. The authors provide background, model effective thought processes and dialogs, and give the readers clear, concrete principles and examples for design considerations. This book is written for both software engineers and designers and illustrates a process which they can use to dramatically increase the quality of both product and process.Alle Produktbeschreibungen
Die hilfreichsten Kundenrezensionen auf Amazon.com
I didn't give it a 5-star only because, to me, the section of their HUBBUB experience and the conclusion was too long and could have been made more concise. Also, it was disappointing to see their product not following their own design goals well enough, which seemed to make the book less effective.
It is written by a UI Designer and a Software Engineer, and takes into account both of their viewpoints. After an initial introductory section to the basic concepts of good UI design, which is very thorough, as any butler should be (read the book to understand), the authors then relate a real-world example in which they collaborated on the design and implementation of a real product. Along the way, they provide some excellent ideas and techniques for how to go about producing a user-friendly user interface that won't take 5 major releases to get right. The product, an Instant Messaging application called Hubbub, is real and can be downloaded for free and installed on any Windows machine or Palm OS handheld. Although not as mature as other IM's out there, it is eminently usable and has some nifty UI features that the current crop don't offer. But it's not necessary to be a Hubbub user to read the book. It's just a nice side benefit for those who would like to give it a whirl.
In keeping with their overall ideas about good UI design, the book is very well organized, easy to read, and has several nice "GUI" features itself. You can tell that the authors themselves probably had a hand in how the book was put together. It is not overly long (about 300 pages), so it doesn't take several weeks to read. Nor is it written in a typical "computer textbook" style. There are plenty of pictures and figures that really help to demonstrate the various points the authors make. It also makes excellent use of color. But perhaps the best "feature" of this book is that it is peppered with "Design Guidelines", each of which sums up in a sentence or two an important aspect of good UI design. And, just to make it even easier, there is an appendix that brings all the design guidelines together in one location for easy reference later on.
Overall, this is an excellent treatment of a subject that probably causes more headaches for designers and engineers than any other in the world of software development. I highly recommend this book for any UI Designer, Software Engineer or Manager who wants to gain a better perspective on the issues involved in designing a user-friendly UI, and, even better, how to go about doing it right. I would not want to embark upon a UI-intensive project unless all parties involved had read this book beforehand.
After reading Ellen and Alan's description of how a UI Designer and a Developer should interact with each other, it just seems so obvious that everyone should work this way. User needs should affect architecture, and technology constrains design--how hard can it be to understand that? But the implications--design and development are iterative, and ongoing user testing is critical to the iterative process--could change the way some people think about programming projects. (The old Specify, Design, Program, Test, Release process seems somewhat naive in retrospect.)
The book has a kind of fun and lively feel to it. It's clear that the authors were having fun telling their various stories, and were excited about illustrating their points. The writing is casual, which made it amazingly easy to read.
On the other hand, once the informal style sold me on the overall approach, I almost immediately wanted a more rigorous treatment. I'd have loved an Appendix that summarized the formats of the various documents, for instance, and perhaps one that reviews the process flow diagram used at the beginning of the later chapters. (As a former academic, I found myself wondering as well about the independence and completeness of the Design Guidelines, too, but that's my quirk. It's probably not an issue most readers would care about.)
I think this book could become one of those that inspires a sort of religious commitment to its vision, and that that would probably be a very good thing.