Dapper, for those of you who haven't heard of it, is a web based service that lets you transform, with ease, any site on the web into a semantic API, letting you consume the site’s content as a feed, a widget, a facebook app and tens of other ways. Dapper’s goal is to build the semantic web in a top down approach, based on the distributed effort of tens of thousands of users and site owners who use Dapper to get and distribute content the way THEY like it.
From day one (Dapper launched Aug, 2006), we were focused on building Dapper as a platform for developers and savvy web users, not as a personal tool. Thus, much of Dapper is open source (and more will probably become so in the future), extensible and modular. We've deployed developers tools such as SDKs and web services and attempted to cultivate a vibrant community through our blog and p2p interaction. Last week (Feb 3-4) was one of the peaks of our effort when we hosted Dapper enthusiasts and partners in the first ever DapperCamp, in San Francisco, CA .
Building an eco-system is not an easy task, and requires constant resources, and its doubly hard for a striving start-up with very limited resources and a tight budget. In addition, initially, and for a long time running, it seems like a one-way street where you give and develop and provide, and don't get much in return. In addition, traditionally, Israeli start-ups (being israelis 
have a very focused, down to earth view, asking what’s the immediate ROI of every action, and looking down at activities that are meant to build an "eco-system", "presence" and other obscure terms. However, once you pass the initial hurdle, build partnerships and work with the community, it starts giving back, be it in word of mouth reference, in enhancement of your basic service, in bug finding and in many more aspects. At the end of the day, an engaging community is also an important asset that you'll leverage in your next round, M&A deal or IPO.
So if you want to build an engaging eco-system around you, what can you do?
Here are a few tips:
1. Blog. Then blog some more. Or as the Richter Scales say: blog, blog, blog it all, blog it if it’s big or small, blog at the cineplex, blog while you’re having sex
a. Also comment, trackback and in general engage in the conversation.
2. Listen and react. Try soliciting feedback early and often. Use the feedback promptly in your dev cycles and let people know when their ideas/comments are realized. When you've built/fixed something based on user feedback and you let him know, he'll be loyal to you forever (internet terms). He "owns" part of it.
3. Form communication channels. Emails (with a repository and tracking system), chat rooms (meebo is great for embeddable chat rooms), forums, wikis. Whatever agrees with your culture. Most importantly, don't create a channel if you can't/don't intend to support it. It will be counter-productive. Adding a channel (e.g. forums) is a life long commitment that requires daily monitoring and prompt response.
a. Don't shield your development team from feedback. Let them read support emails / browse the forum etc. It will enhance their motivation when the service gets great feedback, and will doubly enhance their motivation when bugs/issues are raised.
4. Open up as much as you can. Be it open-sourcing whole or portions of your code base, APIs that allow interaction with your core functionality and data or deploying standards (e.g. openID, openSearch), the more you open up, the better. Some tools (e.g. Twitter) have gained their success mainly because of their openness and inherent interoperability.
5. Partner with complimentary service, leveraging each other’s strength. You can think of it as an extension of Youtube’s embedding practice, which made them so successful. What if you could embed your entire site (or portions of its functionality) in complementary services, or enhance your service by embedding others'? This entails taking great care when designing your architecture so that it will be modular and easily integrated, but it opens the way to all kinds of cooperations, and eventually allows your core service to reach larger audiences.
Lastly, whenever you can afford it, establish presence in your reference market. For many, this means the San Francisco bay, though not for all. Engaging physically with your community is still by far the best way to build it. DapperCamp last week, is a great example, and will probably be remembered as a major milestone for our community and eco-system, not only because it gave an opportunity for us to interact directly and deeply with scores of developers and companies who use Dapper, but also because it allowed them to interact among themselves, creating new opportunities for all, and giving us many new Dapper ambassadors to spread the word.
Israeli start-ups are traditionally more technology focused than the general norm, and it is certainly one of our fortes, but it is important to remember that today, more than ever, the web is a social platform, and whoever wants to succeed should harness this platform to the best of his abilities, even if what he does is some nerdy stuff like building APIs…
