Comments on: Alan Quayle and Developer API Fatigue http://blog.dial2do.com/2009/02/12/alan-quayle-and-developer-api-fatigue/ Commentary, news and analysis on voice services from the Dial2Do team Mon, 08 Mar 2010 16:24:45 +0000 http://wordpress.com/ hourly 1 By: Brendan Lally http://blog.dial2do.com/2009/02/12/alan-quayle-and-developer-api-fatigue/#comment-365 Brendan Lally Thu, 30 Apr 2009 16:45:02 +0000 http://dial2do.wordpress.com/?p=348#comment-365 I don't see a lot of of 'vision' on the horizon or the problem getting solved any time soon. I agree that lack of a 'real' Internet player is just going to have it 'the samol'. Even oneAPI may not get out of the starting gate much I don’t see a lot of of ‘vision’ on the horizon or the problem getting solved any time soon.

I agree that lack of a ‘real’ Internet player is just going to have it ‘the samol’.

Even oneAPI may not get out of the starting gate much

]]> By: #mwc09 part 3 « Voice. An Opinion. http://blog.dial2do.com/2009/02/12/alan-quayle-and-developer-api-fatigue/#comment-229 #mwc09 part 3 « Voice. An Opinion. Thu, 26 Feb 2009 18:33:06 +0000 http://dial2do.wordpress.com/?p=348#comment-229 [...] as these are part of the potential ying/yang Zen solution that I dreamed about in my post about Alan Quayle and Developer API fatigue. Exec summary: BONDI - common APIs for Mobile Web Apps; ONE-API - common network APIs for accessing [...] [...] as these are part of the potential ying/yang Zen solution that I dreamed about in my post about Alan Quayle and Developer API fatigue. Exec summary: BONDI – common APIs for Mobile Web Apps; ONE-API – common network APIs for accessing [...]

]]>