Microblogging has become quite a rage these days. Twitter, identi.ca, Jaiku (now acquired by google) are microbloging services that have seen a viral adoption growth since the last couple of years.
Recently, we saw a lot of enthusiasm and discussion about using statuslogging / microblogging tools in the enterprise. While not all have been positive reactions, and the fact that microblogging essentially provides an entirely new communication model to the masses, known to us geeks as the 'publish - subscribe' model, very well explained here, makes it a sort of a paradigm shift for formal communication requirements.
We all know how much businesses hate paradigm shifts, especially when it does not translate directly to increase in revenue. More over, most of these talked about tools are publicly hosted, causing the compliance and security departments to discourage them.
So does the enterprise need another communication tool that lets them publish what they are doing at a given time to people / peers who would be interested in knowing?
We think so.
We have been successfully experimenting with various collaborative applications using status logs with XMPP for a few years now. Status messages have been common over IM platforms, just that they have only been used towards realtime presence. We created various custom applications for various organizations around presence & status logging over their internal IM network, to solve business specific problems such as task reporting, attendance monitoring and sales force geo presence reporting. And since the release of cyn.in v2, we have been working on integrating status logging into cyn.in, such that we could introduce a 'paradigm shifting' model of communication to businesses, without intimidating business users with new technology concepts and jargon.The upcoming cyn.in version 2.1, introduces statuslogging seamlessly integrated into the cyn.in platform, and it's various applications like the wiki, the file repository, etc. We think the success of the whole microblogging application model revolves around integration. Twitter is successful because of the various ways it integrates into tools that people use every day, such as instant messaging, desktop widgets, social network platforms, etc.Similarly we realized that an enterprise version of twitter would really work only if very contextually integrated into the tools that their teams already use for collaboration. Our customers spend significant time on their cyn.in systems collaborating with each other.
With cyn.in v2.1, status messages have been tightly integrated into all of cyn.in's applications. Our partners (a growing number since we re licensed cyn.in to be open source software) are using cyn.in as a platform to further build vertical specific collaborative applications, will be able to leverage status messages within their applications with easy to integrate APIs.Status logs thus further extend the 'user context' in cyn.in, an area that has been our key focus. Status messages in cyn.in also have threaded discussions within them, making status messaging the best way to start a conversation!We, and a select few of our enterprise customers, have also been testing the initial versions of the cyn.in desktop, codenamed 'Stacker' since the past six months. Though i cannot reveal much about the stacker at this time, I will say that it does some interesting things with status messages, and sort of blurs the lines between web based collaboration and desktop communication tools like the IM.cyn.in v2.1 releases soon this month. Stay tuned for more updates. I look forward to hearing your opinions.