Collanos Blog

As founder and CTO, I would like to initiate a dialogue on our company blog about the technical aspects of Collanos’ offering. This article discusses the main limitations of today’s Workplace release as well as our ongoing activities to address and rapidly fix the problems. The focus is on fundamental platform evolution. I will not talk about business features or collaboration functions today. In my next blog postings, I will shed more light on other aspects like Collanos’ vision, product portfolio and feature roadmaps.

Collanos had been in “beta” for about half a year before dropping the “beta” label two months ago. We have come a long way, but the journey has just started. There are many exciting new features we plan to release to our growing user base. This post introduces some of the features we will release in the coming months.

Starting Out
In eight months, we went through a dozen of small releases, fixing nearly 400 bugs and issues. Don’t be surprised; this is software engineering best practice: quick turn around cycles and “perpetual releases”. We also added many features, and with every improved version, the number of downloads continued to increase. We are about to reach 40,000 downloads, and it is exciting for us to see that famous “exponential curve” (aka the ‘hockey stick curve’) kicking in.

Invaluable Feedback
A big thank you goes to our active user community. Your great feedback helps us better understand what works, what doesn’t, what you like and dislike, and what you miss. This blog post is a summary of the main limitations of our product and how we are addressing them. If you are interested in raving quotes and why users are enthusiastic about Collanos, you can find them on our web site. We have about 30 rotating quotes on the Products page, and new quotes are added daily – just refresh the web page regularly to see them.

Main Limitations
While we receive great feature requests and lots of ideas from users, many could be classified as “nice to have” or are subjective to a very specific use-case. Still, there are a number of issues that come up frequently. In fact, there are important limitations in our current product release that prevent some of our users to deploy the solution more widely. Here is the ranking:

1. User must be online to be invited – An invitee must be online, otherwise there is no way to invite this person. This limitation comes from our current “pure” P2P model with no additional centralized servers or “helper” services.
2. Conflicts can lead to data loss – If two users make changes to content at the same time, then one of the two will likely lose his/her changes. This is a limitation of the current simple “last modifier wins” rule. BTW conflicts cannot be avoided in a P2P system – only mitigated and managed.
3. All content must be received from its originator – The current P2P replication algorithm fetches data from the source (i.e. its originator) only. If the originator is currently offline, its new content or latest changes cannot be received even if another team member is online with that new content.

Near Future
We are addressing all of the above issues with high priority. Our goal is to relieve “user pain” with as simple and pragmatic solutions as possible. We could certainly think of very elaborate and complex “enterprise class” feature sets, but this would only delay the process. Our mantra in engineering is: Deliver great user value fast. In the near future we are going to ship the following features (in this order):

1. Central User Directory – This new central service serves multiple purposes. First of all, it’s a directory for our community so users can easily find other users regardless if they are online or not. You will be able to search by different attributes – much like current social networking sites. And no matter if a person is currently online or offline, you will be able to invite this person.

2. Conflict Bin – This simple “save my data” concept will prevent users from losing their work due to unexpected conflicts. If a conflict happens (again, this is unavoidable in P2P networks), then the overwritten (or even deleted) copy will be saved into the Conflict Bin of the affected user. From there, the data can easily be recovered. At a later stage, we might expand the concept and add support for file versioning. With this, users will be able to refer back to any previous document version.

What’s better? These two features will be rolled out within 3-5 weeks so stay tuned!

3. Improved Replication – Another major effort is going into bringing our replication algorithms to the next level. We are building in some advanced capabilities and intelligence like a peer’s ability of fetching new workspace content from any other peer who already received it, or fetching it from many peers at the same time. Other measures will include advanced optimizations such as measuring P2P bandwidths or dynamically applying priorities. It will also be possible to see how much data is left for transmission on a per object basis.

As you can imagine, the third feature set is a bit more complex to implement. We plan to roll out features gradually with the first set of improvements due in approximately two months. This second-generation synchronization will be the single most important improvement of the Collanos platform. The benefits for our users will be substantial. Users can expect faster replication times and higher transparency of what is being replicated.

And Beyond…
We have a bolder vision, and some of the building blocks are already on the drawing boards:

• Permanent Peer – This service will be an on-demand subscription offered through ISPs. It will boost your overall Collanos experience. Think of it as your other always-on peer that not only maximizes up-to-date workspace content, but offers backup, workspace management, and more.
• Web Workplace – This extension will come with the Permanent Peer. It essentially brings the Workplace to your standard web browser, allowing you to access your workspaces from any connected device. This flexible hybrid architecture will make Collanos the first seamless Peer-to-Peer-to-Web offering.
• Voice Services and Instant Messaging – We will integrate VoIP and more general instant messaging services with our Workplace very soon. The idea is to facilitate individual and team calls directly from the context of your various workspaces. Imagine a one-click conference call with your team!
• Multiple Languages – With the help of our user community, we recently added German to the Workplace and will soon add Chinese. More languages will be added this year. If you are interested in contributing with a specific translation, please get in touch with us.

I hope this information was valuable for you. Do you think we are addressing all the right issues? Do you have questions or would you like to see other topics covered? Please let me know what you think.

Sphere: Related Content

This entry was posted on Thursday, March 1st, 2007 at 4:50 pm and is filed under Collaboration, Product Management Announcements, Technology, Vision & Strategy.

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Share with Shareomatic! | View blog reactions