Having looked over Alec’s presentation, (which is very good BTW for the audience I think he’s targeting) and following his blog, this is what I see. It appears they are using some scripting languages (probably Ruby or Python) to farm the databases of various applications, e.g. Outlook, Skype, etc. They appear to be looking for direct information, like your phone numbers and IM handles and such, and indirect information, like your making assumptions about where you are based on your calendar and when you log in and log off over various services. They then mash all this stuff up and combine it with some kind of call receiving thing (like a SIP proxy server, e.g. Asterisk or SER which I think he has mentioned). If I had to make a guess, I would say they are building some rules to determine if and where an incoming call gets routed.

The basics are very interesting. The devil is definitely in the details. Its basically Artificial Intelligence. In fact, I’ve wondered whether some of the rules based languages for expert systems, e.g. Prolog, might be applicable. As we saw during the AI days, AI is REALLY hard. The good news here is that they have a very constrained space upon which they are trying to be smart and potentially lots of information that can be used to make good decisions.

We’ll see how it turns out. It has lots of potential

FM

There are of course good and not so good things about it.

The good:

They have added IM as a basic component of the service. There was mention of video a couple of times, but right now it looks more like Voice and IM are the strong suits.

They seem to be focusing on “interoperability”. If there was ever a word that cried out for specific definition, its “interoperability”. More on this in the Not so good section unfortunately.

The client user interface looks very clean.

The not so good:

It appears to be a silo. While there has been a lot of talk lately about open standards and avoiding silos, this appears to be going in the silo direction. You need to use their clients (at least if you take their site at face value). I don’t know for sure but I would imagine that all that presence information is sent to the client in using an XML schema that I have a feeling isn’t openly available. I’ll have to do some experiments on connecting with my client and see what I find.

“Interoperability?” I’m not sure what they’re really talking about here. I think what they are referring to is that I can use the Tello client to access multiple services, either voice or IM, thats one way to look at it. The question is, does this really mean interoperability. When you ask an engineer what interoperability means, you’ll probably get something like, multiple implementations of the same protocol working with each other. That’s clearly not what they’re talking about here.

Lots of smoke. This may or may not actually be good. There’s this inherent conflict between trying to be open and talk techincal to woo the developers vs. talking high level and dressing everything up in marketspeak to address less technically sophisticated users. They clearly have gone down the latter path. IMHO, this path is hard for even Grandma to understand.

All that said, the service does look somewhat interesting. I’m a little hesitant to call it revolutionary, if its not me too, its not too far ahead of me too. I wish them the best of luck!

BTW, I agree with Andy, this has nothing to do with what iotum appears to be doing.

FM