Germany
Hi there,
I am thinking about creating a new SDK with standardized API that would enable convergence between Internet and Telephony communication services. The features of this SDK would be e.g. presence, instant messaging, call-setup and call-control, authentication and identification, billing support, remote control of and by devices like mobile phones etc. My idea for this SDK is to make it available to a wider audience to stimulate the upraise of applications on mobile phones, PC, and Set-Top-Boxes to create a seamless, unified communication experience for the end-user regardless of terminal used (e.g. PC, TV-set, fixed or mobile phone, etc.)
To understand the requirements in the market, especially from the various developer groups, I would like to ask you the following questions:
(1) What would be the preferred “feature list” of such SDK, i.e. which Telephony-typical communication services would you want to see in the SDK?
(2) What should be the supported devices?
(3) What is the preferred mode of operation, i.e. do you want to have the SDK as download version and setup all the networking and configuration stuff yourself or would you like to see a “hosted” version where the platform is operated by some service provider and you just use APIs that is exposed (cf. IMDB) ?
(4) Would you be willing to pay for such SDK and how your preferred payment model looks like, e.g. subscription, pay-to-own, pay-per-use, pre- or post-paid, …?
I am thinking about creating a new SDK with standardized API that would enable convergence between Internet and Telephony communication services. The features of this SDK would be e.g. presence, instant messaging, call-setup and call-control, authentication and identification, billing support, remote control of and by devices like mobile phones etc. My idea for this SDK is to make it available to a wider audience to stimulate the upraise of applications on mobile phones, PC, and Set-Top-Boxes to create a seamless, unified communication experience for the end-user regardless of terminal used (e.g. PC, TV-set, fixed or mobile phone, etc.)
To understand the requirements in the market, especially from the various developer groups, I would like to ask you the following questions:
(1) What would be the preferred “feature list” of such SDK, i.e. which Telephony-typical communication services would you want to see in the SDK?
(2) What should be the supported devices?
(3) What is the preferred mode of operation, i.e. do you want to have the SDK as download version and setup all the networking and configuration stuff yourself or would you like to see a “hosted” version where the platform is operated by some service provider and you just use APIs that is exposed (cf. IMDB) ?
(4) Would you be willing to pay for such SDK and how your preferred payment model looks like, e.g. subscription, pay-to-own, pay-per-use, pre- or post-paid, …?