Your SlideShare is downloading. ×
0
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
TADS Plenary Alan Quayle TAD Manifesto
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

TADS Plenary Alan Quayle TAD Manifesto

675

Published on

Review of the TAD Manifesto Status

Review of the TAD Manifesto Status

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
675
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
13
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The Telecom Application Developer Manifesto Update http://tadsummit.com/2013/10/01/tad-manifesto/
  • 2. Purpose of the Manifesto • Telecom voice and messaging revenues, a $1T market, are under pressure from web-based Over the Top service providers. • The telecommunications industry must deliver more services faster to survive. But the existing ecosystem has failed to deliver, hence the need to recognize and develop a sustainable and profitable telecom application ecosystem. • This Manifesto sets out what is required to make the Telecom Application Developer ecosystem a reality, through identifying the needs and responsibility of the three main actors in this ecosystem: developers, vendors and telcos. • The Manifesto reviews the history of how we got to a point where the $5T ICT industry is missing a critical component of a profitable and sustainable telecom application developer ecosystem; and why the web provides an important model in addressing this gap.
  • 3. Progress So far • Manifesto released for public comment on Oct 1st 2013 – Feedback from 50+ people • Pre-conference surveys across telcos, vendors and developers – 80+ survey responses
  • 4. Revenue Defining what is meant by Telecom App Developer Internal Telco Developers Partner Developers Telecom App Developers Mobile App Developers Long Tail Developers Product
  • 5. Revenue This Is A More Accurate Representation Internal Telco Developers Partner Developers Telecom App Developers Mobile App Developers Long Tail Developers Product
  • 6. What do we mean by Telecom App Developer? Developers that recognize they build telecom apps today Hardcore Telco Software Infrastructure (10ks) IT/Web Programmers building on FOSS, telecom app platforms and telecom APIs (1Ms) ‘Cut and Paste’ web developers using web-scripting and graphical tools on app platforms (10Ms) All based on IT / Web Technologies and Development Principles
  • 7. TADS is about Building an Ecosystem Hardcore Telco Software Infrastructure (10ks) Developers that recognize they build telecom apps tomorrow IT/Web Programmers building on FOSS, telecom app platforms and telecom APIs (1Ms) ‘Cut and Paste’ web developers using web-scripting and graphical tools on app platforms (10Ms) All based on IT / Web Technologies and Development Principles
  • 8. Needs and Responsibilities Developer Needs/ (Responsibilities) Vendor Responsibilities/ (Needs) Modern and easy to use tools, docs & support (Communicate Needs) Meet Dev tech needs Support and protect the telco network Go-to-market support Brokering Viable business models Innovation Community of developers (Publicity) Telco Needs/ (Responsibilities) Safely expose assets Help from vendors in building the necessary go-to-market support and business models Process that supports hundreds of new services Industry-wide (Publicity) Best Practices
  • 9. Key Points from Feedback • Promote successes • Share knowledge and experiences, education is required • Access to customers matters

×