RCS-e API exposure:A valuable asset to create application innovation & revenue generation?

Madrid, 5th October 2011

Lessons from the past

Communications are more than person to person

Lessons from the past

All device-tiers & all MNO’s services tend to

succeed

Lessons from the past

When the enabler is “usable” by the ecosystem

to create cases on top, it is enriched with not

initially thought use cases.

Lessons from the past

Telcos got huge revenues from

ecosystem created use cases

Lessons from the past

Yes, the SMS

Lessons from the past

Oops!

The present…

Does it matters NOW ?

The present…

YES!

The present…

RCS-e

The present…

RCS-e is:

Instant Messaging

File Transfer

VideoShare

….all from your phonebook

The present…

RCS-e aims to:

Be present in all device tiers

Be offered by all/most of MNOs

The present…

The delay of the RCS launch brings an

interesting scenario

The present…

OTTs already launched successfully

• WhatsApp

• Huddle

• iMessage

• Blackberry Messenger

• …others

The present…

Not bad… OTTs did the harsh task of

evangelizing

The next future…

RCS-e becomes REAL

The next future…

G5 Telcos expected to

launch soon

(Q411 to Q2/12)

The next future…

Could telcos compete with

stablished OTT messaging

competitors ?

The next future…

Yes, of course

The next future…

Focusing in replicate

SMS strengths

The next future…

All device tiers capable

The next future…

Universal service

The next future…

Openness

The next future…

Thinking in RCS-e as

enabler, not as final

application

The next future…

In SMS is was done

with SMS Gateways

The next future…

Lots of cases created

with simple APIs

The next future…

Alerts (banking, etc)

SMS to TV

M-commerce: ringtones, wallpapers

Voting

Etc…

The next future…

Remember !!!

The next future…

Friendly APIs for the

developers ecosystems

The next future…

You know…REST, WS…

The next future…

The next future…

Not PARLAY ! please

Apps vs Enabler

Ok, ok, but App model

already succeed, doesn’t it?

Apps vs Enabler

Not really!

Apps vs Enabler

Smartphone growth is real

Apps vs Enabler

The model 1 use case 1 app

not so successful

Apps vs Enabler

The most successful apps are:

Browser

Email

Messaging Apps

Apps vs Enabler

YES, communication enablers

Apps vs Enabler

Make RCS-e a “app-solution” driver

The telco business

From downloadable Apps

to

“phonebook service contacts”

Easing Innovation

The telco business

Attracting 3rd party Innovation to

empower the telco enabler

The telco business

App Stores are owned and

managed by device/OS

manufacturers

The telco business

“Service Contact Stores” would be

owned and managed by MNO’s

The telco business

A great difference !

The telco business

And also possible win-win revenue

sharing with “service contact” use

case developers

The telco business

Could exist a middle point?

The telco business

YES, apps using RCS-e APIs as

comms enabler

The telco business

Telco still being more than mere pipe

The telco business

And offering API’s as OTT comms, it

is easier to optimize the network

usage.

The telco business

Ok, Ok, but…when this scenario with

RCS-e APIs would become real in

the field ?

The telco business

Let’s say….

The telco business

TODAY !

THE HOPE

examples

mash-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

www.solaiemes.com

Addtional info:

http://www.rcseopenandubiquitous.com/

http://www.youtube.com/solaiemes

http://www.slideshare.com/solaiemes

http://blog.solaiemes.com