Designing Interfaces: Patterns for Effective Interaction Design |
|
|
List Price: $49.95
Our Price: $32.97
Your Save: $ 16.98 ( 34% )
Availability: Usually ships in 24 hours
Manufacturer: O'Reilly Media, Inc.
Average Customer Rating:  
|
| |
PRODUCT DESCRIPTION
Binding: Paperback
Dewey Decimal Number: 005.437
EAN: 9780596008031
Format: Illustrated
ISBN: 0596008031
Label: O'Reilly Media, Inc.
Manufacturer: O'Reilly Media, Inc.
Number Of Items: 1
Number Of Pages: 352
Publication Date: 2005-11-21
Publisher: O'Reilly Media, Inc.
Studio: O'Reilly Media, Inc.
|
|
|
|
|
|
Editorial Reviews:
|
|
Designing a good interface isn't easy. Users demand software that is well-behaved, good-looking, and easy to use. Your clients or managers demand originality and a short time to market. Your UI technology -- web applications, desktop software, even mobile devices -- may give you the tools you need, but little guidance on how to use them well. UI designers over the years have refined the art of interface design, evolving many best practices and reusable ideas. If you learn these, and understand why the best user interfaces work so well, you too can design engaging and usable interfaces with less guesswork and more confidence. "Designing Interfaces" captures those best practices as design patterns -- solutions to common design problems, tailored to the situation at hand. Each pattern contains practical advice that you can put to use immediately, plus a variety of examples illustrated in full color. You'll get recommendations, design alternatives, and warnings on when not to use them. Each chapter's introduction describes key design concepts that are often misunderstood, such as affordances, visual hierarchy, navigational distance, and the use of color. These give you a deeper understanding of why the patterns work, and how to apply them with more insight. A book can't design an interface for you -- no foolproof design process is given here -- but "Designing Interfaces" does give you concrete ideas that you can mix and recombine as you see fit. Experienced designers can use it as a sourcebook of ideas. Novice designers will find a roadmap to the world of interface and interaction design, with enough guidance to start using these patterns immediately.
|
|
|
Spotlight customer reviews:
|
Customer Rating:
Summary: Visual examples for designing for Information Interchange
Comment: This book is by far the best book that does for the User Interface world of computing what Edward R. Tufte's series of books does for the writer's of technical reports and their needs to present and represent many varied types of data and data interaction. Need to show the effects of miles marched, time required to cover terrain, and temperature on Napoleon's armies march on Moscow and show the number of troops he has left alive at every point along the journey? Tufte shows how the French engineer Charles Minard did so. "Designing Interfaces" does exactly the same thing by showing how various UI pioneers have done the same for the Man-Machine interface. Want to see which issues are getting the most reporting in Google News and how fast or slow those issues are fading from the landscape? Check out the marumishi "Treemap" described on page 205 of Designing Interfaces. Highly recommended.
Customer Rating:
Summary: Excellent
Comment: Nutshell review - If you design interfaces for any software project you should read this book. It covers all the bases, is extensive, comprehensive, well written and easy to use as a resource or refresher in interface design techniques.
Customer Rating:
Summary: A staple for your design library
Comment: Designing Interfaces catalogs UI design patterns in use and provides guidance in using them, with plenty of examples. It takes a consistent approach to describing each pattern: What it is, when to use it, why to use it and how to use it. The book is both a good overview and a reference. If UI design is an area of interest to you, then read through this book and then keep it available as a reference.
Customer Rating: 
Summary: Great interface component reference
Comment: For many years now, I have been coding web sites and applications. Through all that time, nothing has ever been as tough for me as coming up with a design that I am truly happy with. Attempting to create an optimized and stable algorithm or coming up with the answer to a problem that requires non-conventional coding practices; these are always challenges, but ones that are most often eventually solved. Creating that mythical eye catching never-been-done-before layout is something that I have attempted and, sadly to say, usually fell short on. I suppose you'd consider this a case of a programmer wanting an application to not look like a programmer designed it. This was my reason for picking up the Designing Interfaces book.
The first chapter talks about how users think. However, as I finished the chapter introduction, I realized that the author and I are definitely coming from two very different places. In my experience, I get very little hands-on with the user base, or the client that the application is being built for. Even if I do talk to the client directly, instead of going through the levels of proper channels, they usually have a set design in mind, limiting my choices. That's not to say, however, that a good designer couldn't be creative given these design constraints. On the other hand, the author mentions that building a user profile is something that eats up a lot of time though it is always worth it, and while I agree whole-heartedly, sometimes a deadline approaches too quickly or it's just not in the budget to give this the time it truly needs. Past this quibble and reading on, the patterns of human behavior in the first chapter give an almost checklist of things to keep in mind when designing, and even though you read and probably think, "common sense", it is very helpful to have in one place.
As the chapters passed one by one, I found the same patterns in my reading emerge. Read the introduction to the chapters the first time you pick up the book to get an idea behind why that particular chapter is important, or, at the very least, for posterity. After that, just skip to the section in each chapter marked as "Patterns" when you need them. These patterns are where the book really shines. Each of these patterns are laid out in a similar way letting you quickly see what it is, when you would use it, why it is used (as in why it is beneficial to your user), how you create the pattern, and then some examples of its use. Considering that there are nine chapters, each with about ten different patterns, this book contains a wealth of information.
I was originally hoping for more of a design lesson; color theory, placement with a hint of golden ratios, maybe a small college art class packed into 331 pages. Though I did not get much of that, at least until the last chapter or two, I definitely found an excellent reference to keep by my side. For example, if I'm building a layout, I'll open the book right up to chapter 4 to see what the common options are; for showing hierarchical data, I'm opening up to chapter 6 to see when and for what reason I might want to go with a tree map over a normal tree. I couldn't recommend it more to someone wanting a helpful component pocket guide of sorts for interfaces, but if you are looking for theory, I'd go with something more geared in that direction.
Customer Rating:
Summary: More Practical Concepts, Less Psychology
Comment: While I don't own a physical copy of this book, I had used an electronic form of it in the course of my studies.
I will first forewarn those who are interested in Human-Computer Interaction (HCI) that this text does not heavily focus on the science of Psychological principles such as Gestalt Perception, nor does it concern itself with techniques/methodologies such as Threading and Model-View-Controller (MVC) to improve the performance of programs. The focus of this text falls strictly on the layout and/or graphical design in regards to interfaces and web pages.
As well, each principle has certain uses depending on the medium used, which the text does a good job of elaborating (for example, cell phone programs would not be designed the same as a full Windows Application).
A word to the wise though: Requirements must come before Design. There are certain design principles outlined in this text that cannot be realized if the very requirements of the program do not allow for it - For example, Microsoft Office 2007 has in many ways disregarded the principle of habituation/familiarity (as it looks much different from typical Windows Applications in general). One will still need the skill of compromise in order to apply the information presented here effectively in the real world.
|
|
|
|
|
|
|
|
