RCS-e API Exposure

3,432 views

Published on

RCS-e API exposure:A valuable asset to create application innovation & revenue generation?
Solaimes keynote at IMS Global Congress 2011 (Madrid, 5/OCt/2011)

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

  • Be the first to like this

No Downloads
Views
Total views
3,432
On SlideShare
0
From Embeds
0
Number of Embeds
616
Actions
Shares
0
Downloads
80
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

RCS-e API Exposure

  1. 1. RCS-e API exposure: A valuable asset to create application innovation & revenue generation?Madrid, 5th October 2011
  2. 2. Lessons from the pastCommunications are more than person to person
  3. 3. Lessons from the pastAll device-tiers & all MNO’s services tend to succeed
  4. 4. Lessons from the pastWhen the enabler is “usable” by the ecosystem to create cases on top, it is enriched with not initially thought use cases.
  5. 5. Lessons from the pastTelcos got huge revenues fromecosystem created use cases
  6. 6. Lessons from the pastYes, the SMS
  7. 7. Lessons from the pastOops!
  8. 8. The present…Does it matters NOW ?
  9. 9. The present…YES!
  10. 10. The present…RCS-e
  11. 11. The present… RCS-e is: Instant Messaging File Transfer VideoShare….all from your phonebook
  12. 12. The present… RCS-e aims to: Be present in all device tiersBe offered by all/most of MNOs
  13. 13. The present…The delay of the RCS launch brings an interesting scenario
  14. 14. The present… OTTs already launched successfully• WhatsApp• Huddle• iMessage• Blackberry Messenger• …others
  15. 15. The present…Not bad… OTTs did the harsh task of evangelizing
  16. 16. The next future…RCS-e becomes REAL
  17. 17. The next future…G5 Telcos expected to launch soon (Q411 to Q2/12)
  18. 18. The next future…Could telcos compete withstablished OTT messaging competitors ?
  19. 19. The next future…Yes, of course
  20. 20. The next future…Focusing in replicate SMS strengths
  21. 21. The next future…All device tiers capable
  22. 22. The next future…Universal service
  23. 23. The next future…Openness
  24. 24. The next future…Thinking in RCS-e as enabler, not as final application
  25. 25. The next future…In SMS is was donewith SMS Gateways
  26. 26. The next future…Lots of cases created with simple APIs
  27. 27. The next future…Alerts (banking, etc)SMS to TVM-commerce: ringtones, wallpapersVotingEtc…
  28. 28. The next future…Remember !!!
  29. 29. The next future… Friendly APIs for thedevelopers ecosystems
  30. 30. The next future…You know…REST, WS…
  31. 31. The next future…
  32. 32. The next future…Not PARLAY ! please
  33. 33. Apps vs Enabler Ok, ok, but App modelalready succeed, doesn’t it?
  34. 34. Apps vs EnablerNot really!
  35. 35. Apps vs EnablerSmartphone growth is real
  36. 36. Apps vs EnablerThe model 1 use case 1 app not so successful
  37. 37. Apps vs EnablerThe most successful apps are: Browser Email Messaging Apps
  38. 38. Apps vs EnablerYES, communication enablers
  39. 39. Apps vs EnablerMake RCS-e a “app-solution” driver
  40. 40. The telco business From downloadable Apps to“phonebook service contacts”
  41. 41. The telco businessEasing Innovation
  42. 42. The telco businessAttracting 3rd party Innovation to empower the telco enabler
  43. 43. The telco businessApp Stores are owned and managed by device/OS manufacturers
  44. 44. The telco business“Service Contact Stores” would be owned and managed by MNO’s
  45. 45. The telco businessA great difference !
  46. 46. The telco businessAnd also possible win-win revenuesharing with “service contact” use case developers
  47. 47. The telco businessCould exist a middle point?
  48. 48. The telco businessYES, apps using RCS-e APIs as comms enabler
  49. 49. The telco businessTelco still being more than mere pipe
  50. 50. The telco businessAnd offering API’s as OTT comms, it is easier to optimize the network usage.
  51. 51. The telco businessOk, Ok, but…when this scenario with RCS-e APIs would become real in the field ?
  52. 52. The telco businessLet’s say….
  53. 53. THE HOPETODAY !
  54. 54. examplesmash-up Google Weather via RCS-e: http://www.youtube.com/watch?v=iiIcoJUNcTMmash-up Google Translate via RCS-e: http://www.youtube.com/watch?v=bt7CKoCHl_sCRM m-banking demo: http://www.youtube.com/watch?v=DQGINTJEEmYCouponing mash-up: http://www.youtube.com/watch?v=J2CTNliGL0oSocial Plug/connector (FB y Twitter): http://www.youtube.com/watch?v=BatGfIpjMHARCS-e WebClient JQuery: http://www.youtube.com/watch?v=tY8M1t1F2P4Securizing payments http://www.youtube.com/watch?v=5wR9SeM3WE0Bridging XMPP & RCS-e http://www.youtube.com/watch?v=zF_roI2IOA0
  55. 55. www.solaiemes.comAddtional info:http://www.rcseopenandubiquitous.com/http://www.youtube.com/solaiemeshttp://www.slideshare.com/solaiemeshttp://blog.solaiemes.com

×