1. Sound interaction designA component must adequately address theneeds of the user. It must be both useful andusable, properly support all of the desiredmouse, keyboard, and/or touch interactions,and plan for accessibility.
2. Clean codeA component’s front-end code shouldvalidate, be cross-browser compatible, lightto download, and optimised for browserperformance.
3. Ready to useA component should be easy to implementwith as little conﬁguration as is practical.One line of code is ideal.
4. Easy to configureA component should be easy to customise.The best components are versatile enoughto work in a variety of situations, giving thedesigner ample control over the main variables.
5. Well documentedA component library must be thoroughlydocumented. At the least, documentationmust indicate how to start using a componentand describe all of the available configurationoptions.
“Libraries give the team speed andeﬃciency, letting them leverage the richhistory of things-implemented-before.”– Jared Spool
★ From Pattern to Component on UX Magazine: http://uxm.ag/h9★ TwigKit’s UI Components: http://twigkit.com/components.html @TylerTate