Microsoft | platformers | platforming | Skype | SkypeExtras | SkypeKit | Strategy | TokBox | twilio | Voxeo

Christensen leaves a cloudless Skype

Big changes need an executive champion. When Jonathan Christensen left Skype last month, he was the last advocate for a developer-centered strategy.

Jchris boardsHis departure is bad for Skype, bad for Microsoft, and bad for Skype’s users. This is good for rivals who understand github culture, developer programs, cloud operations, and API business strategy. Here’s why:

Skype’s third-party development products are failures.

  • The Skype Extras program collapsed from tens of thousands of desktop apps to a few dozen before Skype shut the program down.
  • Skype tried for a UI-free Skype engine but SkypeKit is unattractive. It’s feature-incomplete. It’s a time sync requiring orders of magnitude more effort (about twelve thousand hours for the first Skype-on-TV apps) than alternatives (1 hour for a TokBox or Twilio integration). It’s burdened with outrageous defensive business terms: Skype can withdraw your license at any time for any reason and you may not run SkypeKit on servers, sell your service to business, or serve Chinese markets.
  • Skype is very late to the cloud communication market. Voxeo, Twilio, Jajah, TokBox, and Vidyo (powering Google Hangouts) have been offering hosted telephony and video conferencing APIs for mobile and web developers for years.
  • Skype’s few developer successes rely on cultivating personal influence, on sycophantic access to Skype insiders. Unless you know someone, you don’t get the resources to build or the waivers to release your product. This doesn’t scale and comes off arrogant and sleazy.

This post-Christensen senior management team understands finished goods. They even understand freemium models. But their hearts don’t beat faster at the thought of Skype powering a million web sites and apps. Their eyes don’t light up when talking platform economics. Their guts don’t tell them to bet on APIs, to open up and let a million designers and programmers plug-in to the Skype network.

So management lacks ambition for platforming. This shows in underfunded cloud projects, a closed (vs. public) developer program, staff defections, and belittling expectations. From management’s behavior you’d think outrageous success by Skype developer partners should trigger a publisher’s acquisition or sudden death. Ouch. Real platformers consider customer successes proof your network is attractive.

Skype’s platform-avoidance strategy will fail, probably this year. Skype cannot hope to deliver meaningful integration at Microsoft without the Skype versions of OpenTok and Phono; they will hit a technology wall. And new users from Skype’s Microsoft products won’t hide the overall slowing of Skype user adoption and revenue, or high defection to services that meet specific needs in specific contexts. As Microsoft’s Bing, Xbox, Kinect, Windows, and Windows Phone know, APIs bring you new revenue and new markets.

Circumstance will drive Skype’s managers to an open cloud platform architecture.

They’ll need entrepreneurial leaders like JC to take them there.

But they’ll have to believe.

Do you believe in platforms?

photo: Jonathan Christensen

image_thumb6_thumb_thumbPhil Wolff designs and positions realtime collaboration products for effective people. Phil advises the Personal Data Ecosystem Consortium and is a director of the DataPortability Project. Email editor@skypejournal.com, Skype evanwolf, tweet @evanwolfG+ or call +1-510-444-8234 to talk with Phil. Skype Journalis independent of Skype.


api | design | Developer Zone | Developers | Skype | Technology | TokBox | twilio | Voxeo

Web Developer usability: 3 lines of javascript per feature

Product management has a natural tension between features and elegance, the richness of more and the simplicity of less. This is true for APIS as much as for user interfaces. Telecom technology is complex, a high learning curve for outsiders. In the last year I’ve seen Voxeo, TokBox, Skype and now Twilio expand their reach to web developers by simplifying the programming experience, hiding the details of making connections and streaming media.

Twilio announced this morning that its “Twilio Client” is just three lines of javascript.

<script src="http://static.twilio.com/libs/twiliojs/1.0/twilio.js"></script>

<script type="text/javascript">

Twilio.Device.setup(token);

Twilio.Device.connect();

//you decide what happens next

</script>

With minor code variations you can build call center, conference call, intercom, softphone, audio recording  apps, and text-to-speech apps in the browser. Promoting the launch, “five developers who write the most awesome Twilio Client apps in the next 2 weeks will win new Macbook Airs, tickets to the Twilio Conference, and Twilio Swag.” I’m loving the t-shirt.  For those who use the Client, Twilio is cutting the cost of audio to a quarter penny per minute. 

There are similar examples. A tiny Skype client powers Facebook’s first video calling app. Its API was also dramatically simplified, removing even usernames. TokBox embeds video calls and conferences with a few lines of javascript.  Voxeo launched Phono last year, also a few lines of javascript to invoke their telecom APIs.

The gold standard for realtime communication: can you reduce your cloud service to a few lines in a language four million web programmers use every day? Can you simplify the object model, prune your parameters, and limit option so what is left is pure, elegant, beautiful and useful?

art credit: Twilio

7 years and 12 days since Skype Journal launched as a stand-alone blog.

Topics