Skype understand the importance of standing as a Service provider and no longer a simple Client provider. Something that cannot be accomplished without massive adoption in different devices, platforms and software.
Although we can reflect once again about the approach that has being used by them.
- Skype API is something that will work only for Skype Network. The flexibility of the service goes immediately to the ground. So if you implement it, make sure you know you won't be to re-use the code somewhere else.
- They are claiming some openness based on an old client side SDK API model. Which dismiss all potential of the currently heavily deployed solutions like SIP, which is everywhere, from Servers, Platforms, Hardware, Gateways etc... I'm not a SIP fan, although strategically would be wiser for them.
- Skype shares bandwidth without user concerns. Would you be up to risk embedding such black box into your own application or Product?
- Most IMPORTANT! Latest Skype IPhone client mention about not being free anymore from certain date. So if you are looking forward to implement Skype, bare in mind they can actually start charging for their services or clients at some point, which may turn your "FREE" application useless.
Apparently they may need to speed it up since Apple announced that Facetime on IPhone 4g, will use Open Standards including SIP, STUN and ICE. Which is a mature P2P technology heavily used and deployed and of course the same as we are using on XMPP Jingle Specifications.
Open Standard P2P already won this 'battle' which Skype still persists to fight.