« O'Reilly "rethinks" Emerging Telephony conference, kills same | Main | Mobile Activity Heating Up »

Why Skype and Vonage must live

Or why Mark Gibbs is wrong when he says quality, support and integration issues hamper these 'closed' technologies.

Mark, interop happens when each party has an abiding interest in it.

Consider IM interop.

AOL, Microsoft and Yahoo only opened their messaging protocols part way. No interop on animation, file transfer, voice chat, webcam chats, conferencing, emoticons and variations on super-duper-emoticons, mood and presence messages, etc. Only the most basic of text message exchange.

Why the limitations? Because text interop is a commodity and the rest still have economic value. Interop for a commodity feature builds network effects without giving up capabilities that distinguish your community's identity.

Standards freeze innovation, for good or ill. VoIM (Voice over Instant Messaging like Skype) is still new. Skype is still evolving how to work in the hundreds of network and compute environments in hundreds of millions of situations. Those situations are challenging and evolving on their own. How you cross firewalls, scale p2p, and adapt streams for mobile conditions aren't ready to be locked down.

Like Microsoft, Skype opened up to third parties by publishing protocols. You can write your own voice mail client in an hour. Skype has APIs for presence, IM, voice and video calls, voice messaging, billing, and call routing. Skype has a budding developer community, mashup contests and free wrappers and other tools for programmers. Skype even publishes a high-level working API roadmap. It's still early, Skype's not done. And Skype is far from closed, Mark.

P.S. My first thought for a title was "Why Mark Gibbs must die" but I'm sure he's much too nice a guy for that sort of linkbait.

TrackBack

TrackBack URL for this entry:
http://skypejournal.com/blog-mt/mt-tb.fcgi/3704

Comments

Standards freeze innovation, for good or ill.

The internet is based on standards, yet it does not suffer from a lack of innovation. If anything, it shows that open standards win out in the long term.

Skype opened up to third parties by publishing protocols.

Where? All I've seen from Skype has been "black box" binary components. For example, if I wanted to write a Skype client for Linux that runs on machines without the X Window System installed (ie, a typical Asterisk server) I can't - I can only get a Skype binary and that binary requires X Window installed. Maybe if I was a Skype partner I could get the needed specifcations to write my own client, but that's hardly what I would call published protocol specifications

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Brought to you by:

Emerging Communications Conference

Auto generated tags