Voice APIs a Part, Not The Solution
The response to my Voice API post on GigaOM has been pretty good. Lots of insightful comments and several good posts in response. It did mostly confirm a lot of what I was saying, but I felt it was worth spending a moment tying up loose ends.
APIs as Part of a Solution: I think the general consensus is that APIs by themselves are meaningless unless they are attached to a platform with significant value. I think it’s also pretty clear that APIs need to be part of a larger value chain, e.g. consultants to do the integration and a clear solution to a compelling business need. IfByPhone makes it easy to integrate, Jaduka offers the custom integration work for enterprises. Voxeo, mentioned by commenters, also offers a full suite of services.
Consultants Make the Money: While many voice API vendors make varying claims about how easy it is to integrate their APIs into your applications, chances are, you’re going to hire some consultants to do the integration work. I’m sure that makes Thomas Howe happy.
Bookmark with: del.icio.us Digg it Furl iFeedReaders ma.gnolia Maple.nu RawSugar reddit Simpy StumbleUpon
Tags: jaduka, Ribbit, Thomas Howe Fnord
Comment by Dan York
Dameon, Good summary… but I still keep beating the drum: APIs need to be based, as much as possible, on *open standards*. Otherwise: 1) an API becomes just yet-another-way for a vendor to lock you in to their specific platform; and 2) developers can’t use their existing knowledge and have to learn how to use *your* new API. We as an industry need to use open standards-based APIs as much as possible so that we can build a larger pool of people who can build voice applications… the more developers there are who can do it, the more voice apps…
So in my opinion we need to be promoting the use of protocols like SIP, VoiceXML, CCXML and other similar technologies and protocols.
Thanks for raising all these points about APIs,
Dan (who, yes, does work for Voxeo, but would be making these points about open standards regardless of who my employer was)
Comment by Jack Rynes
Dameon,
Nice follow-up to yesterdays conversation. Pulling together all of pieces (API, reliable scalable network and the consulting) is the path to true value and revenue.
@DAN – You have a good point about API’s based on industry standards. Web Services simply points to a “standard” used through out the internet. My only concern with “standards”, being an old telecom guy, is that there always seems to be some nuance to each (SS7, ISDN, etc) making it difficult for interoperability. That said, SIP, VoiceXML and CCXML seem to moving in the right direction.
Comment by PhoneBoy
Ok, I forgot about open APIs, you’re right, Dan.
@Jack what’s the saying, the great thing about standards is that there are so many to choose from?
Pingback by Discover From Your Favorite Topic or Web Page: www.programmableweb.com/apitag/telephony