Design patterns and javascript libraries
Written at 00:05, on Wednesday 9 May 2007. Tags: c-md javascript webdesign .
A large part of the discourse on web development today is focused on design patterns and interface components. But what are they exactly, how are they useful and how can they change the way we work? More importantly, what are their limitations, the scope of their application?
Design patterns are sort of an evolution of the style guide, which we are familiar with from graphic design. But while the style guide documents and prescribes the use of graphic design for communicating a certain brand, design patterns abract common problems in interaction design. A common examply is undo functionality.
There are lots of design patterns available today. The Yahoo! Design Pattern Library focuses on creating small components which can be used as building blocks for creating your own web application. A similar library for interaction design is provided by Jenifer Tidwells’ Designing Interfaces. Martijn Welie’s design patterns is broader in scope and describes also complete web site patterns. A nice collection of good pattern examples can be found in this screenshot collection
Design patterns are only one part of the story though. In order to efficiently and quickly use them, a lot of Javascript libraries have been developed that provide customizable pattern-based components. The Yahoo! User Interface Library provides lots of components that are made according to the results of their extensive pattern research. Other Javascript libraries, such as Prototype and Scriptaculous, jQuery and Mootools often provide similar functionality but they’re often based on developer needs, and mostly focus on easily adding Ajax support and animation effects. Despite this, they are excellent starting points for design pattern components since they are easier to use and offer a stable base which takes care of browser bugs. Most libraries can be extended with plugins, thus allowing you to fully leverage their advantages.
Together, design patterns and Javascript libraries are becoming the new building blocks for creating rich internet applications (RIA’s). And unlike Flash, it’s possible to make them completely accessible, which means that they can be used by people with disabilities, but also by search engines and mobile devices. The possibilities of these RIA components and design patterns on the web are now starting to emerge. But these are just foundational building blocks. What’s next step in this evolution of the development chain? And how can we leverage these design patterns now that the Web is starting to become available on mobile devices and game appliances? Should we adapt them, or come up with new patterns for other browsing devices? What consequences will multi-touch interfaces have for this work? Lots of interesting stuff to think about…
Comments closed | Permalink
