[(Web Anatomy: Interaction Design Frameworks That Work )] [Author: Jr. Robert Hoekman] [Jan-2010]

by Robert Jr. Hoekman

At the start of every web design project, the ongoing struggle reappears. We want to design highly usable and self-evident applications so our customers can work efficiently, but we also want to devise innovative, compelling, and exciting interactions to dazzle our users and make waves in the market. And which approach wins is often a circumstance of who's leading the the aesthetics-driven visual designer or the usability-minded conservative.Renowned design researcher Jared Spool, founder of User Interface Engineering, and veteran interaction designer Robert Hoekman, Jr., author of Designing the Obvious and Designing the Moment, want to resolve this conflict once and for all. In Web Anatomy, they introduce a collection of interaction design frameworks——sets of design patterns and other elements that compose entire systems——and reveal how the psychology behind these standards leads not only to effective designs, but can also serve as the basis for cutting-edge innovations and superior user experiences.Web Anatomy A reference guide to interaction design frameworks* An examination of the psychology behind the standards* An in-depth look at what works, what doesn't, and where to go from hereCiting examples from both the successful and not-so-successful, Hoekman and Spool break down the elements of common interactive web systems and subsystems, explain why they work, show when to use them and when to avoid them, describe implementation considerations, offer examples of innovations, and put a big spotlight on the possibilities.Read Web Anatomy now. Reference it for years to come.

Genres: Design, Website Design, Nonfiction, Usability

Unknown Binding

First published September 12, 2009

Reviews

[Mikal · Rating 2 out of 5]

Web Anatomy was a surprisingly poor book given the authors pedigrees. The authors try to build the case for "design frameworks" a not altogether distinguished resource apart from design patterns and components.

The distinction is somewhat arbitrary. For example in many implementations such as the MailChimp pattern library, design patterns and components (reusable code), live together.

Ultimately the ambiguity forces the authors to spend too much text justifying itself.

The book effectively is broken down into an intro that lays the foundation of what frameworks are and why they are important, and next a section that covers examples of frameworks and finally a conclusion which purports to demonstrate how to build your own framework libraries, but instead attempts to justify itself once again. Here its unclear how segments made it past the editor, specifically how the authors claim frameworks are an integral solution to solving Amtrak's usability issues are odd.

Another oddity is the choice of case studies, the authors choose easy and at times arbitrary (movie sites) frameworks to document. Admitting in some cases that the findings were not their own but simply the outcome of a workshop.

Ultimately frameworks have the most value when viewed as a research deliverable owned by the research team, this allows it to be liberated from the communicative work pattern libraries have to deliver and allows it to have a more natural update process that integrates design research into the development process.

[Nathanael Coyne · Rating 2 out of 5]

I like the concept but feel this book is a little lacking. I feel the authors should have avoided specifics and just focussed on developing and consuming interaction frameworks or gone for the full reference guide like Christian Crumlish and Erin Malone’s Designing Social Interfaces. Read more on purecaffeine.com.

[Alwyn Velasquez · Rating 4 out of 5]

So far so good. This book is chuck full of information. A bit technical but an informative read.

[Jörg Hoheisel · Rating 2 out of 5]

nothing new