Features
- Cover Type: Paperback with 456 pages
- Published by: O'Reilly Media, Inc. June 1, 2007
- Written in: English
- ISBN 10 Number: 0596528108
- ISBN 13 Number: 978-0596528102
-
Book Dimensions:
9.1 x 8 x 0.9 inches
- Weighs: 1.9 pounds
Reader Reviews
§ The title of this book does tend to focus things, doesn't it? A book totally dedicated to working out navigation challenges in Web products means that it is destined to be a one-stop keeper on your shelf. If you work in any capacity on Web front-ends, navigation is often the issue of issues, the source of stimulating and heated team discussions. This book won't end those discussions but the information in it will certainly add calm perspective to them. _Designing Web Navigation_ seems to have it all in one place, including practice discussion at the end of each chapter and further reading recommendations. The amount of information is impressive. There is not a page without a visual aid of some sort. I certainly like having lots of screenshots of real sites with the commentary of the author. I also like the practical knowledge of the author which informs his writing -- he emphasizes the variability of the rules in the complex contexts we Web workers tend to work in. Note, for instance, how differently he approaches Amazon's tabbed navigation from how usability guru Jakob Nielsen writes of them. Nielsen never passes up an opportunity to exclaim what is wrong wrong wrong about Amazon's tabs. Kalbach, instead, explains the motivation behind each passing stage in the evolution of those same tabs, giving the dynamic context. This rings true for those of us with daily working knowledge in constructing user interfaces. I was a bit disappointed that the book did not have more on the specific problems of designing Web *applications* instead of conventional Web sites. However, the book is written is such a way that this is not a problem. The advice and arguments on p.236 "Don't start by designing the navigation on the home page" encapsulates quite well something I have learned working on agile development teams over the years. I had a few problems with the readability of this book. Page numbers look like squished gnats and all paragraph sub-headings were a pretty but painful light blue. The extremely large line-height weakened the separation of paragraphs. As I mentioned, this book is chock full of the right material that belongs on your shelf for when you need it...and you will. §
Comment | |
(Report this)