SpoolCast: Reusable Components & Libraries with Nathan Curtis

Brian Christiansen

September 16th, 2010

Duration: 35m | 18 MB
Recorded: September, 2010
Brian Christiansen, UIE Podcast Producer
Sean Carmichael, audio editor
[ Subscribe to our podcast via Use iTunes to subscribe to UIE's RSS feed. ←This link will launch the iTunes application.]
[ Subscribe with other podcast applications.]
[ Transcript Available ]


Nathan Curtis

Nathan Curtis


If your site has more than one page, chances are you have repeated elements: Repeated interface elements, repeated design patterns, repeated code snippets. When you multiply your responsibilities over a large site and involve many designers, developers, and stakeholders, how do you make sure you’re not wasting your time building many widgets that already exist? That’s where a standardization process comes into play.

Nathan Curtis and the crew at EightShapes are the leaders in standards, reuse, consistency, and libraries. In this podcast, Jared Spool speaks with Nathan in anticipation of his workshop on this topic at the 2010 User Interface Conference.

(Side note: in this context “standards” are different than “web standards”, though completely compatible.)

When do you know if you need a component library? Nathan says the idea often surfaces when designers and developers start chatting about their collaborations. When many people are touching the design, the idea to reuse components comes up quickly. Standardizing on certain page components, for example, helps in many ways. It prevents double work and keeps the experience across sites (especially large sites) consistent. Certain items, say a calendar picker on a travel site, are especially useful to reuse.

While the creation of a library is useful and efficient in many ways, storing the components isn’t free. It requires a manpower commitment and possible software purchases or provisioning. Nathan says to do it right, you should treat it as if it were another project on your team’s plate. But once committed, you can focus on the quality of the components. If you have 18 different video players across your site, someone can take the time to discover which ones work best and then improve the experience across the site.

Beware of how you maintain your library, Nathan warns. If you let it get too out of date, it’ll lose its credibility and people will begin to stray. If you can’t ensure the library will be faithfully maintained, make sure only your critical items are in the library. Prioritize for the components that have the most effect on the User Experience.

Nathan shares many more tips for libraries in the podcast. But he’ll have even more when he teaches a full-day workshop on the topic at this year’s User Interface Conference.

User Interface Conference FifteenExplore Nathan’s workshop and the full conference program. Register for UI15 by September 22 with promotion code BLOGPOST and get $400 off.

Are you reusing your components? Are you curating them in a library? Share your experiences with the community in the comments.

2 Responses to “SpoolCast: Reusable Components & Libraries with Nathan Curtis”

  1. Josh Aronoff Says:

    I’m in the process of developing out our UI Design Patterns and downloaded your EightShapes Unify stuff, Nathan. It was great stuff. I’m finding that my background in traditional graphic design for print, and web are helping immensely. I happened upon this podcast at JUST the right time as I am starting this arduous project.

    Thank you guys for helping me gain perspective in terms of not biting off more than I can chew in a year… 🙂

  2. Quora Says:

    How do you ensure design consistency (or continuity) across a large organization without adding lots of overhead?…

    Hee. I was going to point to Salesforce’s postcard patterns as a great example. This is really a question for Nathan Curtis. He talks a little about the problem in this podcast: http://www.uie.com/brainsparks/2010/09/16/spoolcast-reusable-components-l

Add a Comment