Cocomo basically leverages the Adobe Connect back-end to deliver features such as Data Messaging (think traditional Remote SharedObjects), VoIP Audio, Webcam Video, File Sharing, Text Chat and so on. The tool is provided in shape of a developer framework and component set that can be used to build Flex based applications.
Cocomo is definitely a very cool platform and on the surface it makes it easy to build real-time applications that may otherwise be quite difficult to build. But I also see an enormous overlap between Cocomo and Flash Media Server.
This comes as no surprise since Adobe Connect uses Flash Media Server as its foundation, and Cocomo applications feel very familiar to the experienced FMS developer. A key differentiators is the fact that Cocomo is a pure client side framework, meaning the developer has no access to the server side code. This is not a big issue since Adobe is aiming to provide all required functionality without the developer requiring access to any server side logic.
What concerns me are Adobe's efforts to push further into the domain of their own developers, and potentially competing with them on a playing field on which the referee may be playing for the opponent. I'm not yet convinced whether Cocomo will open more doors than it will close, and it is clear that any application built using Cocomo is competing with applications that were previously built with FMS. Undoubtedly this will drive some developers away from FMS since Cocomo is now the suggested way to build collaborative applications.
Having taken part in the Cocomo pre-release program I have had the opportunity to use the technology first hand and the team at Adobe (many of which are familiar faces) have done an incredibly good job. The platform cannot be faulted from a technical standpoint. No, it's the business perspective that worries me greatly at a time where Adobe is trying hard to drive more developers towards FMS.
I'm a huge fan of online collaboration and real-time applications on the web, and that's what got me most excited about FMS in the first place. I now seem to be receiving mixed messages from Adobe about which one of their platforms to choose, and right now I must say that I am highly skeptical about the approach that they are taking with Cocomo. I understand the business decisions behind it, but I don't think I agree with them.
Also, I may be wrong here but I couldn't find a reference to screen-sharing in the current Cocomo API, something that Adobe's own services built on these platforms do offer. If that's the case it means that the API provides less functionality than Adobe's (competing) service.
I guess the rationale is to make it easier to create collaborative applications, which I think Cocomo does well, but you're right that this now means Adobe is treading a fine line between giving its existing developer community the tools to create interesting applications, attracting new developers with Cocomo, whilst also competing via services like Acrobat.com and Connect.
They surely are treading a fine line and I'm concerned that they may overstep it. You are correct that there is no mention of screensharing yet, but if they add it then my guess is for it to be Cocomo (and Connect) only. Meaning I doubt they will add it as a new capability to the Flash Player as a whole. Level playing field?
It's a real shame. I know that I can build great apps with Cocomo, but I am concerned that FMS is being cannibalized as a result. The component set in Cocomo is impressive, and it is what FMS deserves. No doubt they have also build a great server side framework, but developers are not going to lay their hands on that.
Moreover we have heard no details on Cocomo pricing yet.
Bottom line: yes I can see myself using it, but every minute I spend on Cocomo is one minute away from FMS. I'm not sure if this path is a good one.
Maybe the FMS community is small enough and the risk of p*ssing them off is one worth taking in exchange for more new business from developers who haven't considered building collaborative apps before. I'm sure Adobe must have weighed up their options at some stage, but I am not seeing a clear message. What are the differentiators between FMS and Cocomo exactly? How much value can a developer add to what Cocomo already provides? Let's wait and see I guess.
Thanks for putting your thoughts out here. I was going to respond in the comments, but it became an essay, and so I moved it over to my place :
http://blogs.adobe.com/collabmethods/2008/11/of_re...