Ads are not an endorsement by the blog author.

aimInfo

Public Journal
 Back to Journal Archives | Subscribe to Alerts Alerts Subscribe to Alerts | Feeds
< End of a very bus
Friday, March 3, 2006
We Are Live >
Monday, March 6, 2006
March 2006
Monday, March 6, 2006

Now its Your Turn

Kool and the Gang - Celebration


Today is a historic day at AOL as we announced, just moments ago, a software development kit for AOL Instant Messenger.  Open AIM will empower you, as the developer, to write custom clients, plugins, and eventually bots.  When you include this SDK with the web presence API and AIM Module-T (IAmAlpha, or AIM Modules) we are really starting to build compelling social network development tools.  The SDK will be available starting at 5AM EST today at developer.aim.com

For now, lets concentrate on the Open AIM SDK and get into what it can do for you.  First, the development kit is written using COM, so plugins and custom clients can be written for Windows in languages like C++, VB, C#, and eventually J-Script.  In the near future we will have solutions for LINUX, MAC and Windows Mobile devices.  Why is this important?  We now have a solution to provide all AIM users and consumers to build their own IM clients and to extend the features of Triton via plugins.  Of course all of this is free of charge.  How do I get started?  Well my team has provided a quick start guide, and tutorials, in addition to numerous coding examples, from the simple to the complex.  Our examples are in C++ and C#.
What are the limitations?  Basically anything goes, with the exception of writing multi-headed clients, though as always read the EULA and FAQ for the exact limitations.

Now that we have released this, I will be blogging more and more to help answer questions and to be your guide to using the SDK.  Check back later today for a post on some more details on using the SDK to build a custom AIM client.

I really would love feedback on this.  The small group of engineers who wrote this API have been working on this for 2 years and we really put a lot into this.

PS - Hopefully this explains my disappearance for the past week.  I have been working 18 hour days trying to get this out the door.


gregsblog at 12:42:00 AM EST Blog about this entry
This entry has 9 comments: (Add your own)
  • #9 Comment from bangbang023 
    3/6/06 6:00 PM Permalink
    avarame: If you really think AIM is going to die because of a closed network, you're only kidding yourself. Those multi-headed clients only promote the use of other networks. Why would AOL want to help promote MSN/Yahoo/Jabber/every other network? They wouldn't and they don't. It's quite simple and pretty damn logical. I'm not sure why so few people actually grasp the idea of trying to run a business, but the general rule of thumb is to keep people away from your competitors.
  • #8 Comment from avarame 
    3/6/06 2:15 PM Permalink
    "Basically anything goes, with the exception of writing multi-headed clients."

    Thank you for demonstrating how much you Don't Get It.

    Multiprotocol clients are out there. They are stable and mature. They have survived your attempts to kill them. They are gaining in popularity. They are not going anywhere. Embrace them! It costs you nothing and makes users a lot happier.

    Open systems live forever, and all who use and operate them benefit. Closed systems either slowly die or get forced open, usually to the detriment of the owner. History has shown this over, and over, and over. Does AIM need to be yet another example?
  • #7 Comment from ejdmoo 
    3/6/06 1:44 PM Permalink
    How soon will you be adding Windows Mobile support?
  • #6 Comment from earthling1375 
    3/6/06 11:56 AM Permalink
    P.S. Congratulations! It's a great step forward and I'm sure it took a herculean effort.
  • #5 Comment from earthling1375 
    3/6/06 11:39 AM Permalink
    Why aren't you allowing presence on multiple networks? Isn't that part of what's exciting about an API/SDK for AIM for the end-user?
Show all comments (4 more)