Monday, August 24, 2009

Best thing ever- caBIG iPhone Apps and more!


We are seeing a watershed in caBIG software development- the appearance of caBIG® software products in more places, with ever more potential users. Konrad Rokicki's amazing caBIO iPhone app (link) represents a really, really cool working proof of concept, and opening up so many more possibilities! In a similar vein, caBIG developers at Ohio State and Emory are working on integrating the caBIG imaging tools with existing iPhone applications such as Osirix (link). Our own team is hard at work developing an open source iPhone front-end to the caTISSUE application, to facilitate tissue collection in the field, and there are many other developers we talked to at this year's caBIG Annual Meeting who are working on similar projects at various stages of maturity.

Added to all of this is some equally cool and significant work on developing a robust .NET platform for constructing and integrating caBIG software and tools (link). Be sure and check out the screencasts from this year's Hackathon. This kind of effort is critical for extending the caBIG concepts to the parts of the community that have committed to a Microsoft infrastructure. As the program matures, developing these kinds of bridges to the wider community will be increasingly important. Over the next couple of years, we hope to see all kinds of new applications running in new places - it will certainly be cool!

Be competitive!

Driving business in an open source environment can be challenging - just ask anyone who runs a software service and support effort on top of and open source software stack. Being creative, leveraging relationships and defining a role in the community can all create a means for establishing a business position, developing a customer base, and deriving growth as a service provider in an open source world.

Working without the safety net of deep (and unique) knowledge of proprietary software can be seen as just asking for trouble - proprietary commercial vendors can not only charge a premium for that knowledge, they can closely control who has access to critical information such as the current and future APIs, software release plans, and marketing collateral like logos and branding. With that kind of advantage, authorized vendors can have the double benefit of access to an established customer base, and the ability to charge premium rates for their work. In this environment, becoming an authorized vendor means a clearer path to profitability than being just another provider of services.

Into this context, providing services in an open source context can seem much more difficult, where trying to compete with a whole range of other companies, all of whom have equal access to the underlying codebase can appear to dilute opportunities and decrease profitability. In order to develop business, service providers can do some specific things to increase their profile, establish their street cred, and develop a strong customer base. Here are a few examples:
  • Spend quality time with the community. By being present at the meetings attended by the customer base, a provider can raise their profile, develop personal relationships, and both learn and teach what they know about the open source products they are supporting. Almost every open source project has a community behind it, and whether they meet online, via teleconference or face-to-face, those meetings provide a unique business development opportunity.
  • Answer questions and participate in forums. Most open source projects have forums / wikis where the collective knowledge around the products are collected and developed. By answering questions and participating positively in discussions, capable service providers can demonstrate their knowledge and identify where there are opportunities for business development. There is a thin line between using these forums as a means to demonstrate goodwill and develop relationships and spam/hard selling. Being able to tell the difference between the two is a critical distinction for success...
  • Participate in the development of the code. The cool thing about open source code is that it is really owned by everyone. Becoming one of the contributors to the codebase is a very good way to both gain deep experience with the tools, as well as demonstrate goodwill and community engagement. One of the positive effects of this effort is that often work for clients that extend the shared codebase can itself be relevant to the broader community, and can be the basis for the contributor who added it to become the obvious expert on those components (obvious because it was shared with the community, and because the contributor was an active community participant - see above.)
  • Become formally identified with the program. When there is a way to get formal recognition of the status as a designated provider of services around the open source codebase, it can contribute to raising a vendor's profile, and gain a not insignificant amount of credibility as an expert in the underlying software. This is particularly useful when the potential customers are new to the field, and are looking for someone with credentials or other concrete demonstrations of capability.
By getting out there and getting involved, interested organizations can rise above the noise, get noticed, and engage in a virtuous circle that itself can create more business opportunities. Working in an open source environment is never easy, and developing business is hard no matter where that business is located, but by placing effort in community contribution, that work can be pay off downstream.

Monday, August 17, 2009

5 years worth of caBIG!

The deeply intertwined fields of bioinformatics and computational biology are maturing and evolving at a startling and ever-increasing rate. This progress was really evident at the recent caBIG Annual Meeting held last month here in Washington DC. As in much of biomedical informatics, the real development has been in the community. At the July meeting, we had the opportunity to see a whole range of interesting and cool things that people have been doing in the cancer informatics community- all of which represent a significant development over previous year's meetings. Similarly, it was really cool to see how groups within the program have started to develop their own collective approaches to problems that they share. In particular, the Center Deployment folks have initiated an impressive shared effort, working together to instantiate strong, relevant and shared applications throughout the country. On this 5th year anniversary for the program, I can't help but wonder what we are going to see in the next 5 years- it is certain, though, that we are coing to continue to see more and more of the kind of creative, inspired leadership and technology from the program, and that there will be even more interesting and creative solutions to the problems shared by the entire cancer informatics community displayed at future caBIG Annual Meetings!