Tomorrow I’ll be presenting at the Illinois Institute of Technology Real-Time Communications Conference and Expo, its a collaborative event, where industry and academia connect. The presentation I’m giving is on ”The Winners and Losers in the move to Real-Time Cloud Communications,” shown below.
If you track my presentations on this topic, the new material focuses on 2 things.
- What we mean by the term Telecom App Developer;
- And how the telecom application developer ecosystem can evolve.
Telecom application developers range from the hard-core that can use ClearWater, Mobicents, OpenCloud, hSenid Mobile etc. for building core telecom infrastructure applications. This is essential to lower the cost of service operations to that of other providers like Whatsapp and Skype. A recent OpEd piece in TelecomTV “OTT is dead – long live the Telecom App Developer” explores this topic in a little more detail. Then there are developers building telecom services on platforms like Ameche and using APIs / web-scripting on OnMobile, Tropo, Twilio, APIdaze, RestComm, etc. With WebRTC extending the services out to any web-connected device.
All of these developers come from the IT/Web side, it’s just a matter of specialism. From the few thousand focused developers building the infrastructure applications to the tens of millions of developers – some like myself only capable of cut and paste programming but nonetheless building telecom apps. The stories of many of these developers are reviewed on this weblog, from operators like Algar Telecom and Orange Poland taking control of their future; through the many businesses running on telecom APIs; to the powerful web-scripting tools making cut and paste programming possible.
Cloud communication networks are immensely powerful platforms upon which businesses can run more efficiently and new services created that can make our lives easier and more fulfilling. The TADSummit is about recognizing all these developers, they may not all use the label telecom app developer, but they are increasingly using such capabilities. Recognizing this category of telecom application developers helps share experiences to build the ecosystem faster.
A common refrain from many who have been here before is the telcos are the gatekeeper, they will act as a barrier and stifle the ecosystem as in the past. But things have changed. The Telco is no longer the gatekeeper. 2600Hz, Aculab, Apidaze, Bandwidth, Plivo, Restcomm, TelAPI, Tropo, Twilio, etc. are building successful businesses working direct with developers, they do not need telcos. Also telcos are slightly more motivated than in the past at the CxO level, communication revenues are under threat if not in decline and this also drives focus. The app store is lost to Apple and Android, communication services is now the focus. If telcos can get it right, they can help grow the market faster and expand globally, but the other 2 actors are not wholly dependent on them. So of all the actors in this ecosystem telcos have the most to lose.
The presentation finished on a plug for the TADSummit which is focused on building the telecom application developer ecosystem using the TAD Manifesto to set out what is required and the TADS website to promote those building telecom application developer success, which we will be explored through the many case studies at the TADSummit, 21-22 November. And, just to mention, Huawei is the latest TADS sponsor!