Rating: 
Summary: Focuses on "Desktop", not "Web" UIs
Review: Mandel's book was one of several UI books I got when I was trying to implement a process for designing Web user interfaces at my workplace. Mandel has an entire chapter on it, "The User Interface Design Process", which on flipping through the pages seems quite comprehensive.It turns out, however, that Mandel's intention in this book is to introduce the theory and practice of Object Oriented User Interfaces (OOUIs), through a brilliant "foundations" part that covers the concepts and evolution of user interfaces, two OOUI parts that profile and detail OOUIs, and an "Advanced" part that looks at evolving user interface concepts and issues. Unfortunately, not only are Web interfaces covered in but a single chapter in the last part of the book, but the chapter merely explores, without a conclusion, how the Web interface is strikingly different from the traditional PC desktop interface. OOUI principles are in no way applicable to building Web applications (Consider what impact the OOUI tenet "Users must Understand Direct Manipulation (Drag and Drop)" would have on download time and cross-browser development costs in a Web project). Overall, the book is a great read, a necessary reference for any UI designer, but avoid it if you're looking for solutions, especially for Web-based applications.
Rating:
Summary: Focuses on "Desktop", not "Web" UIs
Review: Mandel's book was one of several UI books I got when I was trying to implement a process for designing Web user interfaces at my workplace. Mandel has an entire chapter on it, "The User Interface Design Process", which on flipping through the pages seems quite comprehensive. It turns out, however, that Mandel's intention in this book is to introduce the theory and practice of Object Oriented User Interfaces (OOUIs), through a brilliant "foundations" part that covers the concepts and evolution of user interfaces, two OOUI parts that profile and detail OOUIs, and an "Advanced" part that looks at evolving user interface concepts and issues. Unfortunately, not only are Web interfaces covered in but a single chapter in the last part of the book, but the chapter merely explores, without a conclusion, how the Web interface is strikingly different from the traditional PC desktop interface. OOUI principles are in no way applicable to building Web applications (Consider what impact the OOUI tenet "Users must Understand Direct Manipulation (Drag and Drop)" would have on download time and cross-browser development costs in a Web project). Overall, the book is a great read, a necessary reference for any UI designer, but avoid it if you're looking for solutions, especially for Web-based applications.
Rating: 
Summary: Not what the world needs
Review: On page 7: "[UI] must have complexity, be interesting, have intensity, depth and richness, and be distinctive. It must have length, in its finish and in our memory, engage our minds, make us think about it." If all my software had a user interface as defined by the term above, I would get no work done. And with the number of software titles available, if they all tried to be complex and deep, and distinctive, surely users will suffer. This is just one example, but I strongly believe that this book starts off on the wrong foot. And it even says to come back to that chapter so to remind yourself which foot you are suppose to be starting from. This book is NOT going to improve interfaces.
Rating: 
Summary: Ironically All Show and No Substance
Review: Some books can trick you into thinking that there is going to be something to say when there really isn't. Sadly, this book falls into that category. Bound between the covers are 400-plus pages of common sense, rants about Windows, praises for OS/2, and constantly repeated philosophies that are never truly demonstrated.
There is an interesting section on memory and the way people learn, which are important considerations for designing UIs, so it's not a complete loss, but when the book actually got down to putting something together, it doesn't really have much you can look to for guidance. The iceberg analogies and the perspective models weren't very helpful either.
At the start of every chapter, the author cites numerous quotes from people no one has ever heard of and doesn't give any context as to why we should listen to them.
The most ironic aspect, however, is that the book, at times, is poorly structured. The sections don't seem to have any logical ordering to them making whole portions sound like a rambling of loosely connected topics, and of the text will cite a table or figure and then display it in a completely different section or even two pages down the line from where it was cited, making the examples seemingly irrelevant to the text.
All-in-all, this is one you can easily avoid.
Rating:
Summary: for the novice really
Review: the book isn't a bad book but it's more of a reference and a little on the novice side. If you haven't already, check out "The Human Interface" by Jef Raskin. That is a far superior book.
Rating:
Summary: for the novice really
Review: the book isn't a bad book but it's more of a reference and a little on the novice side. If you haven't already, check out "The Human Interface" by Jef Raskin. That is a far superior book.
Rating:
Summary: for the novice really
Review: the book isn't a bad book but it's more of a reference and a little on the novice side. If you haven't already, check out "The Human Interface" by Jef Raskin. That is a far superior book.
Rating: 
Summary: Effective blend of theoretical and practical
Review: The Elements of User Interface Design does a very good job of covering theory and application with easy language and real world examples. I found the Key Ideas and tool tips to provide extrememly useful information. I would highly recommend this book.
Rating:
Summary: Read it to look busy on a lazy day
Review: This book will not tell you how to create an intuitive and loyalty-inspiring interface for your company's applications. It won't help you create technologically cutting edge interfaces. It doesn't tell you how to design software or plan for change. It offers essentially no applicable guidelines for style or component choice. It doesn't have much to offer when it comes to the graphic design of icons or splash pages. And it won't tell you how to write the code to make a good UI happen. What will it do? At best, it will open your mind to the field of human interface design, if you don't know it already. But there are no revelations and no surprises here. If you have no previous knowledge of user interface design and/or have little knack for such things, Elements will break you in easily and comprehensively to the concepts. But with a little experience or common sense, you could gleam as much from a good twenty page tract as from this verbose tome. Skim it in an hour, or use it to feel vaguely productive during a lazy day at work, while you stare out the window. But don't count on much in the way of concrete benefits.
Rating:
Summary: Better than Alan Cooper's book
Review: This is a very good book on user interface design - far better than Alan Cooper's About Face. But if you want a book that tells you how to write code to make good user interfaces then this is not for you. Instead, try "Constructing the User Interface" by Ian Horrocks.
| 
