Advertisement
Membership
Login
ACCU Buttons
Search in Book Reviews
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
The premise of this book is that there should be a relationship of collaboration between the user and the software. The software should allow the user to quickly get into a state of flow, where they can focus on the work that needs doing, without having to stop and persuade the software to do the task at hand. Isaacs proposes a number of principles grouped under two main headings.
Don't Impose - make every click count, remember where they put things and remember what they told you.
Be helpful - use visual elements sparingly, make common tasks visible - hide infrequent ones, give feedback, follow conventions, solve problems - don't complain or pass the buck, be predictable and explain in plain language.
The book is split into two parts. The first part describes the principles with many examples of good and bad practice. The principles are easy to grasp and are full of those 'of course' moments. The second part takes the reader through the development of a real project, from talking with the customer to establish the requirement, through to laying out the user interface using storyboards. Only now are the programmers let loose to build the software and the architecture to support the user interface and we see how the initial problems are resolved and for use throughout the project, how to run Usage Studies.
A very easy to read book, yet packed with useful ideas for building collaborative software. Anyone designing and/or building any computer user interface should read the first part of the book and they will find they enjoyed the rest of the book as well. Highly recommended.