Which interoperability?

2007-09-12 14:49:35 by Fabio Forno

When designing and some new IM based services two concepts of interoperability are available:

  • try to offer your service to most IM systems
  • chose an open protocol, that's to say XMPP, and stick to it

Apparently the first solution seems more portable. Try to imagine a small startup like ours seeking for venture: the first question in the interview could be "how large is your market?". You sum the figures of MSN, AIM, Yahoo GTalk and others and you get the impressive number of few hundred millions. Impressive uh?  You say "I'm using XMPP, GTalk and few others use it" and you have almost failed the entry question, since your figures lose at least a zero. 

The problem is that this kind of interoperability is the dark side of the force: don't be too greedy with the figures, but choose a solution that can grow, because you may end up with a large unsatisfied user base not using your service

Let's explain it with an example. In the last days I've tested the IM integration of Twitter and Jaiku and today I've tried Plugoo , a flash based widget embedding a chat window into a web page and allowing visitors to chat with the page owner. Twitter and Plugoo are interoperable accordingly to the first concept: they allow you chosing any IM system. Jaiku, instead is committed to XMPP only. All these systems have few usability issues, since IM integration is new and there are no well known patterns for solving problems. However the more promising is Jaiku: many of its issues are being addressed and the developers have plenty of options for improving the service (multi user chat for channels, a savvier use of resources, x-html, ad hoc commands, client capabilities, just to list some features of XMPP that may be handy). Instead I don't see many chances for improving Twitter IM integration and Plugoo: apparently open, they are stuck to the small (almost null) subset of common features of the adopted IM services. Any improvement is stopped, but simply (in term of of expressiveness) and cumbersome (for users' interaction) text based commands, that's to say they are forced to used '90s like solutions when ICQ and IRC were already there.

So, when asked "how many users?", just say "one day as many as Internet users, XMPP will be as ubiquitous as now SMTP and the Web are. Why? Because it's the only way to make things work, the other will simply fail" ;)

Posted in jabber

3 Responses to "Which interoperability?"

  1. Nÿco says:

    > You say "I'm using XMPP, GTalk and few others use it" > and you have almost failed the entry question, > since your figures lose at least a zero. Wrong: They only lose fame. The real "thing" is: XMPP gets you MSN/WLM, AIM, ICQ, Yahoo! Messenger, but let's not forget the non-more open, but less famous Gadu-Gadu, QQ, Nate On, MySpaceIM, for which transports are do-able or already available. Besides, you can say that the biggest IT industry leaders have products and services based on XMPP: IBM, Sun, Google, Adobe, Oracle, JBoss, Red Hat, HP, Apple... and so many open source projects and communities.

    1. Fabio Forno Says:

      Gateways have the same problems of multiprocol clients: you can't base your service on all the advanced features of XMPP, so you can't count on them (unless you tell a small lie ;))

    Trackbacks

    1. from klvidymw
      klvidymw
      klvidymw
    2. from ptvrmxjx
      ptvrmxjx
      ptvrmxjx

    Leave a Reply

    Not logged in. You have to fill the data below to leave a post. Please register here

    Nickname:

    Email:

    Antispam code:

    XHTML: You can use these tags: [ a abbr acronym b br blockquote code pre em i strike strong ]


    To send a trackback, use this url.