Implementation Focus:

By YUI TeamApril 9, 2009

Dave Nesbitt of Lunch.comDavid Nesbitt is the VP of Engineering at, an online community that helps people share and discover relevant information, opinions, and ideas.

He has worked in software development for the past 20 years.

Prior to, he was the chief architect and director of application development at Vue Technology, which recently sold to Tyco International (TYC) for $43M. David is very optimistic about the potential of Web standards development in today’s environment and an enthusiastic proponent of the Yahoo! User Interface (YUI) framework.

When away from work, David relishes the challenges of fatherhood and is a connoisseur of baseball. Go Angels!

Special invite to Lunch's private beta for YUIBlog readers:

  • Go to
  • On the right-hand side of the screen in the Get an Invite! box is a "Have an invite code?" message. Click on the click here link.
  • Enter the Invite Code YUIBlog and a valid email address. Click Submit.
  • will immediately send you a confirmation email.
  • Open that email and click on the confirmation link.
  • Sign into, a new online community based on the premise that the most useful information comes from people who share your interests, tastes and point of view.

Design and interface quality are huge differentiators for startups. What are the strengths you wanted to build around in the interface?

At Lunch, our strengths are the community's ability to contribute both facts and opinions about almost everything and our Similarity Network which, based on site interactions, connects each person to others who share similar interests, opinions, and ideas. To clearly deliver and communicate to the user it is important for the interface to be clean and easy to understand.

You chose YUI's JavaScript library to help drive the UI. What led you to make that choice?

We selected YUI for a number of reasons.

First and foremost, we felt that Yahoo's commitment to this technology gave a significant advantage in the areas of test coverage, maintenance, and longevity. Standard open source frameworks have the potential hazard of falling into the "flavor of the day" category, where there is an initial surge of enthusiasm that can quickly be abandoned for the "next big thing." We wanted a framework that was going to have a lasting presence.

Secondly, we were impressed by YUI's architecture. The quality and modularity of the interface is impressive. Clearly, there is a concern for keeping the interface clean, whereas other frameworks have a tendency to become bloated over time. Yahoo's architectural shepherding of the interface gives it a better chance of staying slim, usable, and maintainable over the long haul.

Thirdly, we found the documentation and supporting resources to be very helpful. The number of examples and easily navigated Web site facilitate a short learning curve and rapid development. We also appreciated the wealth of JavaScript information available from the YUI Theater.

Finally, we found the YUI blog to be a robust source of tutorial information and the YUI discussion forum to be a vibrant community of helpful implementers willing to share their knowledge and address issues. We didn't want to feel like we were "on our own" when problems arose.

All of these reasons led us to choose YUI and we have not been disappointed.

What YUI components are in use on the site?

Yahoo, Dom, Event, Connection Manager, Get, JSON, Animation, Container, AutoComplete, ImageCropper, TabView, and OverlayManager.

The UI, employing YUI overlays for contextual popups in the ExhiliRATE feature.

What's next for the interface of in coming releases?

Currently we are in private beta but we will be opening it up in the next few weeks. Our goals for the interface, are to continue to optimize the experience for both existing community members and for people just looking to gain knowledge or insight into specific areas of interest. As we move from the closed beta to an open beta it is important that new visitors can understand the value of Lunch and easily jump in and start getting personalized information based on their interests. Creating those easy on-ramps and access points that can engage and drive adoption will be the key priorities moving forward.