In our discussion, Nathan and I first defined design pattern libraries and component libraries. A pattern library is a repository for ideas and solutions to design interaction problems. Component libraries are comprised of actual functioning parts with real code. An example would be a log-in process. Your pattern would define the experience of logging into your application, from the interaction, and often visual standpoint. Your component would be the chunk of code that represents the set of fields and controls that can be replicated across your organization’s web properties, so that you can easily create a consistent experience for your users, no matter where they may enter your system.
Also huffduffed as…
You’ll learn how to keep your application logic truly decoupled, build modules that can exist on their own independently so they can be easily dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.
Dan and Jeffrey talk with special guest Jared Spool about usability testing in the real world, with practical advice for designers, UI engineers, and developers alike.
Jared Spool is the founder of User Interface Engineering, the largest usability research organization of its kind in the world. He’s been working in the field of usability and design since 1978, before the term “usability” was ever associated with computers.