Web Application Design Patterns (Interactive Technologies) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Web Application Design Patterns is a must read if you are in the business of designing web applications, or simply want to understand the elements of a well-designed web application. Pawan Vora has condensed best practice, along with research and his solid experience, to create a useful reference about designing web applications. Even if you skimmed the book and looked at the designs, it will spark creative design ideas. -- David Dick, Technical Writer
Excellent! A very complete and exhaustive overview of patterns for web applications with many previously undocumented patterns. This book is written in very accessible way and will tell you (nearly) everything you need to know when designing web applications. A must-have for any designer! -- Martijn van Welie, Pattern author, Philips Design
This is the type of book you'll want to read with your entire team and a flip chart, because every page will produce a list of actionable changes to the applications you're developing. Pawan Vora has produced an amazing catalogue of the essential patterns for designing today's
web-based applications. -- Jared Spool, Founding Principal, User Interface Engineering
- Publisher : Morgan Kaufmann; 1st edition (March 9, 2009)
- Language : English
- Paperback : 448 pages
- ISBN-10 : 012374265X
- ISBN-13 : 978-0123742650
- Item Weight : 2.03 pounds
- Dimensions : 7.5 x 0.9 x 9.2 inches
- Best Sellers Rank: #5,712,124 in Books (See Top 100 in Books)
- Customer Reviews:
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
As an application developer - when I think of design patterns, I think of relationships and interactions between classes and objects in the code (i.e. Factory Pattern, Decorator Pattern, Observer Pattern, etc). The 'Security' and 'User Authentication' topics in this book are all about how it looks on the page. This book is about UI design. The title does not fit with the content - in my opinion.
If a web application were a car - this book would be all about paint jobs. There is nothing 'under the hood'. It has nice pictures but has little to offer in terms of content for a serious application developer.
This is not primarily a coding text. So largely, it avoids delving into whether you might use ASP or JSP [or something else] to define those pages. Instead it gives overall good policies or characteristics that your website's pages should have, leaving the implementation details to other texts.
Each pattern, and there are many patterns, is described in this way - By defining the topics "problem", "solution", "why" and "how". Typically, a pattern is buttressed with at least one screen capture of an actual website that uses the pattern. Readers will recognise many prominent websites, including Yahoo, Google, Flickr and Netflix. But also relatively minor ones like Wine, Zoho and Mint. That is one of the book's attractions. None of these are made up examples, which should help keep the reader's attention.
One chapter is on searching. Here, be aware that the discussion is about how to present search results. A UI issue. It does not go into the actual complexity of finding results for a query and then sorting those according to some relevance criteria.
Unfortunately, there is one discordant feature of the book. Notice the names given above, that Vora uses for the topics of a pattern. He has paid careful attention and chosen good terminology that is succinct and self explanatory. Alas, this is mucked up by a cumbersome and unnecessary repetition of a few phrases, like "allow users to" or "allow them to". Literally every second or third page often has one or more instances of the above. They should be replaced with "let users" or "let them". Shorter and more active. Lets the reader focus more easily on the underlying messages. Just like the way that each pattern has the topics "why" and "how".
This is also worsened by the text using the above long phrases as titles, like on pp. 188-9, "ALLOW USERS TO SORT DATA COLUMNS" and "ALLOW USERS TO FILTER LARGE LISTS". It's not just on these pages; it's easy to find other instances. Titles should be as short as possible, as in "why" and "how". The author understands this, yet he keeps contradicting himself. I suspect that at some level, he automatically uses the longer passive phrase, without questioning it.
Attention has also not been paid to minimising other types of titles. On p. 227 there is "OFFER USERS ALTERNATIVE TEXT INPUT OPTIONS". Better is "GIVE USERS OTHER TEXT INPUT OPTIONS". Or on p. 247, replace "INFORM USERS OF THE SELECTED VALUE(S)" by "TELL USERS THE SELECTED VALUE(S)". When you write a title, not only are you allowed to be concise, you should be.
Ditto for figure captions. Figure 9.7 says "Flickr allows users to add tags to photos they upload". Just say "Flickr lets users add tags to photos they upload". As above, it's not just this figure. There are many others with the same problem.
In case you're wondering why I'm harping on this. The book is about design patterns. The terminology of a "pattern" is about 15-20 years old, and is borrowed from architecture. But when applied to a website user interface, you can think of a pattern as a generalisation of a [good] writing style. For decades, there have been books on the latter. The book looks at the ease of use of a website's pages. Step back and look in a metalevel sense at the book itself. Apply the book's motivation to itself and judge it by this.
to have a copy of "Web Application Design Patterns" as an important
addition to their knowledge base. Web developers and companies feeling
they can "handle it themselves in-house" will find this book an
absolutely critical must-have. It is obvious that years of experience
and research have gone into the production of this valuable reference.
Written at a college / professional level, Vora's style remains,
however, as user-friendly as his design solutions. Presented in a
straightforward PROBLEM --> SOLUTION --> WHY --> HOW format, this 429
page volume skips the editorializing and pontificating; instead, it provides
concrete examples and explanations of underlying concepts. This
book is a veritable encyclopedia of solutions to today's software
interface design issues.
Colorful screen shots grace almost every page, helping the reader
quickly understand problems and resolutions with real-world examples.
Along with the expected discussions of everyday mechanisms such as
forms, user authentication, and navigation schemes, "Web Application
Design Patterns" forges on with detailed examinations of rapidly
evolving areas such as Rich Internet Applications (RIA), social
networking sites and more.