Sunday, November 11, 2007

Building Yakkle (Part 1: Getting Started)

Now that we have introduced Yakkle, we would like to share how we built both the application and infrastructure around it. We hope that by sharing our experiences and lessons learned we will help others who also have the desire to participate in what we feel is a golden age of self inspired, self supported software development.

Find a Problem You Feel Passionate About Solving
In our full-time jobs we have been forced to endure many, shall we say, sub-optimal collaboration experiences with existing for-purchase online meeting and desktop sharing products. We also frequently see our peers combining a variety of free tools to collaborate, but still struggling due to the lack of “live” visual interaction.

So we asked ourselves, “Can we combine the best aspects of all these applications and tools to create a best-in-class collaboration product, and can we do it in a way is essentially free?”

We found that the answer to our question is yes, and the result is Yakkle.

Get Started By Picking a Software Architecture
Of course, Yakkle didn’t just happen, it had to be built. The first thing we needed to do to create it was pick the right architecture to create the application. We needed an architecture that would allow us to develop quickly at a high level of abstraction, but yet have the performance to achieve the demanding network centric operations of remote voice communications and desktop display.

With our background in distributed, object-oriented design, we knew that it would give us the agility to quickly develop any application, but we didn’t know if it could give us the performance we needed. With that question left to be answered, we decided to forge ahead.

In our Next Post
In our next post we will pick up with more on our distributed, object-oriented architecture and implementation choices. Until then, if you would like to experience the result of our works go to and start Yakkling today.

blog comments powered by Disqus