So, we’ve just shipped BRIO beta, and I wish I could say we’ve taken some time to relax; but we haven’t. One of the great/horrible things about Hosted Services is that as bugs come in, we can fix them right away and redeploy… So keep the bug reports / suggestion coming, and we’ll keep plugging away.
We did take time to read through the reviews out there, of course. We’ve always kept our eye on Robin Good‘s input, as he’s got as much experience analyzing and reviewing Collaborative apps as anyone out there. Check out his very detailed review :
One thing that caught my eye (besides “There is no other competitor in this marketplace that offers this much for this little”, or “Brio is a breakthrough web conferencing solution“) is his call-out of the whiteboard functionality. I’d love to hear more of his thoughts on this, and would suggest he apply for a Cocomo private beta account – the whiteboard is built for extensibility, so that any Flex developer should be able to make new tools for it. I would love for someone motivated to add tools to join up
Second item for today : Peldi took some time to go through the BRIO source code and come up with a few statistics. The 2 things he was interested in :
1) How much of BRIO are we shipping as part of the reusable Cocomo Flex SDK?
2) How much of BRIO was built on the server, and how much on the client?
Check out this pair of graphs for the results :
I have to admit, I was pleasantly surprised by just how far we’ve come. Consider that the server code in question will be the same services provided for every Cocomo app, and you get a sense of what we’re trying to do here – Apps on the client (built on our Cocomo Flex SDK), Services on the server.