Alpha & Telco words together? Great!

One of the CES 2013 most commented news has been the AT&T announcement of its Call Management API and Alpha API program.
Powered by Voxeo Labs Tropo API and the Ericsson IMS. The annoucement got a lot of awareness. A big congrats to those companies.
You can find an excelent post on that by Alan Quayle here.

Solaiemes always aimed telcos opening its assets to 3rd parties in an easy wat to create services on top with win-win-win value (telco, developers, and final users.
We have been listening during years from carrier people: "we are not allowed to launch in beta", "people will not accept betas from us", "impossible to launch without a final closed spec behind". Well, finally, bells were ringing, bands playing and everyone in holiday attire.

A major telco realized that beta is better than nothing, and that even "alpha" is good, as perhaps the final product needed will be adding ideas from 3rd parties as feedback. This is how technology world works and telcos are part of this world.

We invite all telcos to follow the alpha-strategy to find new use cases for their communication assets, to open their networks for external innovation, because new services and innovation will seed the future revenues. And of course, please telcos...this strategy is the good one for RCS joyn :-)

Multimodality approaches. Old approach.

Yesterday, reading the DevCentral newsletter (the AT&T newsletter for developers) and talking about multimodal interaction (multimodality), in plain words, using voice to command the mobile browser :-), they talked about 2 options: Fat and thin clients (On Device Clients).

• FAT CLIENT was a mobile application including ASR (speech recognition capabilities) and TTS (text to speech).

• THIN CLIENT was a mobile application able to encode/decode the voice to send to remote server where IVR resourcer are based.

In both alternative to get multimodal solutions, you face the same problem, only powerful smartphones have the resources to run those clients (symbian, windows mobile and possible iPhone and Blackberry) but with difficult compatibility from handset to handset.
Additionally, if you want to get connected with multimodal capability with several CRM (m-banking, m-ticketing, etc) you do not want to install so many application. And a lot of people prefer mid tier devices with good browser but not so "open" to create thin or fat clients.

In our opinion, these restrictions reduce the "potential market" of multimodal enabled mobility solutions or m-CRM offers. Why not using native mid-tier handser capabilities as browser and the voice and data simoultaneus offered in 3G and class A GSM/GPRS/EDGE handsets.
Stay tunned, tomorrow we will unveiling our approach not needed fat or thin client :-)
juan

Good News !!! AT&T launchs Video Share IMS based service

At least a very good new in the IMS industry, AT&T (formerly named Cingular) launched in several US cities the commercial service of Video Share.

The link to press release is

http://www.att.com/gen/press-room?pid=4800&cdvn=news&newsarticleid=23983

and their specific website

http://www.attvideoshare.com

the pity is they only talk about use cases mobile to mobile.

Remember please that video share has a lot of amazing use cases mobile-to-server and server-to-mobile to be offered to your customers (public security, enterprise, media companies and even personal blogging services)


juan mateu