Why didn't AOL open source its IM client?

AOL is getting a lot of credit for "opening" its ubiquitous AIM instant messaging software "to open source." However, like Microsoft did recently by revealing documentation to its APIs and protocols, all AOL has done is open access to its OSCAR protocols necessary to create open-source implementations.

This is great, but consider just how much more AOL could have done, and for its benefit.

Like open sourcing its instant messaging server and client software. Think about it. What revenue does AOL protect by keeping its IM software closed? Sure, there's advertising revenue from the obnoxious ads it sprays around the client, but that is thinking far too small.

The real money is in abundance. Or in "adoption-led markets," to borrow Sun's nomenclature.

Let's imagine that AIM was the default messaging platform for enterprises and consumers. Open source makes that much more likely because it would likely lead to a more widely distributed and used collaboration platform. It would get embedded into all sorts of different applications.

A platform used by everyone is much more valuable than a platform used by many people. AOL would almost certainly continue to guide the platform because it would have more developers that grok the code. It would therefore still have the opportunity to provide advertising, support (in the enterprise), and other services around the core platform.

The instant messaging collaboration platform. Not just first among equals or one of many.

But AOL didn't do this. It simply made it easier to read up on how AIM works. That's great, but it's a poor shadow of what AOL should have done.


Related Links:

• Go back to category Software Development to read more reviews and articles.
• Go back to Software Magazine's main page.