Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Ingredients for a Successful Service Innovation...

Ingredients for a Successful Service Innovation Ecosystem

I created this deck for eComm 2009, which was organized by Lee Dryburgh as a
"TED-style" conference to look into the future of the emerging communications industry. The deck was developed in collaboration with, and presented by, Chris Mairs (our CTO). It addressed how communication operators could enable platforms for innovation.

Andy Randall

March 04, 2009
Tweet

More Decks by Andy Randall

Other Decks in Technology

Transcript

  1. Some Examples 17 million iPhones sold 15,000 applications 500 million

    downloads 5 million downloads / day 175 million active users 660,000 developers 52,000 applications 140 new apps / day
  2. Why Are Telephony Apps Scarce? •The innovation opportunity is not

    obvious • How many variants of Find- me/Follow-me are there? • Why are there more Salesforce mashups than Salesforce users? •SDK restrictions Opportunities for innovation
  3. Why Are Telephony Apps Scarce? ! Hide legacy/TDM grunge !

    Provide familiar paradigms (RESTful APIs, etc) Low barrier to product creation
  4. Why Are Telephony Apps Scarce? ! Hide legacy/TDM grunge !

    Provide familiar paradigms (RESTful APIs, etc) The Simple Development ILLUSION ! Regulatory issues ! Billing and inter-carrier comp ! Stateful error handling and corner conditions ! Design and testing is difficult ! Must interact with network infrastructure ! Security policy
  5. Why Are Telephony Apps Scarce? Clear route to market Mass-market

    approach is not suitable for high-cost, high-utility applications
  6. Why Are Telephony Apps Scarce? Clear route to market Mass-market

    approach is not suitable for high-cost, high-utility applications
  7. Why Are Telephony Apps Scarce? Clear route to market One-off

    download fee is often not the best revenue model
  8. Enable Seamless Integration Network services (e.g. network address book, shared

    call list, message store) Parallel APIs for different device types (RESTful XML, JavaScript libraries, EBIF, ...) - one size doesn’t fit all One-touch distribution mechanisms for users to acquire widgets for multiple device types
  9. Lower Barrier to Product Creation •Reuse existing Web 2.0 paradigms

    •Pre-canned widgets •Lots of tutorials •Sample “GA quality” code
  10. MetaSwitch Strategy Social Community Third-party developers 200+ partners 400+ carrier

    customers " leadership " right APIs " sand box " tutorials " source code " blogs, forums " engineering resources