Skype Technologies S.A. is failing its independent software developers.

What must Skype do to develop a successful developer community? How would you score them? How do you approach such a problem?

Developing an effective developer community requires more than just the desire, it require a model, something that will stretch the internal team and inspire developers. It must be so simple that the parties get it. So effective that key dialogs can start.

Eight key dimensions drive the success and behaviors necessary to nurture an effective developer community. This is not just about words. It is also having the right types of personalities and roles involved to make it happen. Too often a developer community is viewed with systems focus. I'd offer up that it is about people. People in all these roles

Judge for yourself: How does Skype's management of the Skype API and developer program score on each of these factors? Where could they improve? How would this map versus Microsoft or Java or...... Rate them "A" to "F" on each of these. Rate them today, then rate where you think they will be in six months. Are they on tract to be the ultimate partner for developers? What new ground must they break to get there?

1. Architecture Evangelism: Are the systems and documentation for developing your product on the Skype platform clear and comprehensive? Are short-term feature release timetables published? Are road maps disclosed and updated? Are contacts easy to find? Do you know who to talk to? Is access managed and measured? Is the developer education program diverse (accommodating many kinds of programmers), dispersed (geographically and across time zones), stepped (from beginners to gurus, from generalists to specialists), affordable, and comprehensive?

   Score: D-

   In Six Months? This is totally dependent on Lenn Pryor. C maybe.

2. Creative Opportunities: Does the API expose many features? Can they be combined to do novel and interesting things? Do they provoke innovative and competitive products and services? What unique opportunities does the API offer? Can solutions bridge APIs etc? Does the Skype developer program provide tools for experimenting and testing a developer's work in progress?

   Score: B.

   In Six Months? This will be a C- unless they expose more

3. User Experience: Does Skype help developers create "star" products and services? Toolkits? Is there effective brand synergy and marketing impact? Are third party tools seamlessly blended into the Skype user experience? Best practices: Apple's UI standards.

   Score: F.

   In Six Months? We'll see whether they become developer friendly C-.

4. Supportive Team: How effectively does the ecosystem work as a team, as a community? How free and productive is the exchange of ideas? How effective is Skype's communication and updates to the community? What is the opportunity for co-development with Skype? What are the risks of Skype obsoleting third party products through surprise changes to the API? When and how does Skype compete directly with developers and other partners? How well is Skype staffing to support the developer community? Best practices: Microsoft Developer Network.

   Score: F.

   In Six Months? Unlikely to see a roadmap in less than six months. Could still be an F although a frustrated and trying F.

5. Legal Agreements and Public Policy: Are contracts and deals between Skype and developers effective? Are they fair? Do they reflect the realities of how programmers develop software and how users use software? Is the legal language clear? Are accurate translations easily available? Are the license terms and conditions best-in-industry? How much does Skype protect developer rights and interests? How well does Skype protect developers by protecting end user privacy? How actively does Skype advocate to governments and industry for personal data privacy, the right to connect, and against hostile regulation?

   Score: F.

   In Six Months? Complete lack of action or general obstruction. This needs to be an A if Skype is to win.

6. Business Exchange: Working on Developer Time: Do you respect the ISV developer's time? How many minutes does it take for a developer to get a technical answer? to apply to the developer program?

   Does the Skype application enable a two way information exchange? Is data flow through the API one way or two-way or even multi-way? How much is static vs dynamic? Exchanges with the client, exchange of information with the user? Security of information? Privacy management, user rights protection? Can developers build on information exchange to create commerce transactions?

   Score F:

   In Six Months? I truly wish for improvement. C.

7. Value Creation: How's the money managed? Integrated? Can payment to the Skype ID be made? Can withdrawals or payments be made? Who pays for services or products? Does Skype offer download "options" for certified software add-ons? Is there a river of monetary opportunity?

   Score: D. Although other free services are creating value on Skype's back.

   In Six Months? D expect little change.

8. Investors & Peers: As a developer can you sit at the table? Do you coexist like eBay resellers, integrated into the financial ecosystem? Is Skype a positive facilitator or are their always barriers? Are investors willing to put money in? Who bankrolls the opportunity? Are business cases relatively easy? Do you travel first class or coach?

   Score: F:

   In Six Months? D at best on current trajectory.

My conclusion.

Now many will say I am very harsh. You are probably right. Most developers would say "Skype is doing their best." "They are a young company." "They basically get it." What developers want is more access and functionality in the API. Communication is a big deal. They also don't want to be screwed by changing Skype road map. I gave the highest score to the API. Without it the only developers interested in Skype would be those applying for a job.

I thought long and hard about posting this blogpost. I did ask other Skype developers. I'm convinced now it has to be said. So this post is more directed to my friends (please don't shoot the messenger) at Skype. It may not be encouraging to get a "negative report card." Still that traces more to a poor attendance record (lack of people) for some of these "streams." Overall the API and developer focus can't afford to be tactical. For example, they focus on what to expose (e.g. voice messaging) rather than on broader strategic issues like how do independent developers make money, create collective value for users. etc. Perhaps thinking more broadly will enable the "score" to change rapidly.

So what score would you give to Skype's Developer Programs? Am I being too harsh? Do you want more systematic metrics? Let me know!