Embed Size (px)
DESCRIPTION
Dial2Do Slides for ICIN 2009
Citation preview
Who am I and why do I care?
Rococo Software (2000)Java/Bluetooth Software (JSR82)
200M Mobile phones to date (Motorola, Sony Ericsson, Samsung, more….)
Dial2Do (Rococo spin-out 2009)
Voice Activation Platform targeted at hands-free users (e.g. drivers)
Text, Email, Twitter, Reminders and more - by dialling a number and speaking
Partner with hands-free providers to offer services “Powered by Dial2Do”
What if telcos were really web 2.0 savvy?
Text messages might be free, in return for thembeing open, searchable, and re-usable
Every time I texted a friend, or called them, itwould be / could be posted to a website
When I went to call someone, contextualinformation would be pulled realtime from theweb
Mobile attraction
Mobile is simply “where it’s at” for developers
The notion of not being able to seamlesslyengage with “my web stuff” while on the movewill soon be “quaint”
Hence, lots of “web pedigree” developers nowrushing to mobile
5M Mobile users (Aug 08)25M Mobile users (Feb 09)65M Mobile users (Sep 09)
And when they get there, they have quite areaction…
I’d rather develop for?
Lots of tools, mostly free, core setworks for any browser
Billing and pricing easy, and my shareis predictable ! Many apps free…
Application available day one,worldwide, under my control
I figure out how to get noticed
InternetLots of tools, mostly free, each set may
address a different “platform”
Billing can vary wildly, and share willvary based on approach, on-portal, off-portal, aggregators. Free is still treated
as suspicious!
Control is with the operators, oraggregators, or both.
Operator cherry picks winners
Mobile
Different capabilities may be availablein different regions, operators, devices
Process could involve both cost andtime to be “certified”
Wish list
Help ease fragmentation issues
Share more revenue
Simplify getting paid
Get out of my way
Let me at the network assets
Fragmentation
Fragmentation is getting worse, not better
platforms : Symbian, Microsoft, J2ME/Java, Apple, Android, LiMo, WebOS,….
devices : regional variations, operator variations,…
approach : native apps, widgets (Yahoo, Google, Widsets, Opera,… ), web apps, …
network : Orange APIs, Vodafone APIs, O2 APIs, … ONE-API?
OMTP-BONDI?
Simplify getting paid
Payment options are all over the map
Network based billing APIS
Minimal intrusion to end user experience
Predictable payment timescales
Share more revenue
Apple’s 70/30 is a black hole - sucking in developers
What affects developer decision?
How hard is it? How cool is it? (rich)
Who will be able to use it? (reach)
What’s the time-to-use? (speed)
How much money can I keep? (margin)
How will end users be able to pay? (payment)
Think hard about reach…
Source: Shamelessly taken from GetJar App Store Comparison on Slideshare
App Store Comparison
Source: Shamelessly taken from GetJar App Store Comparison on Slideshare
?
Developer Choice (or confusion)Platform / Device APIs telephony
service platforms
Aggregator / Service APIsNetwork /
Operator APIs
Orange APIs
Betavine
oneAPI
Ribbit (part of BT)
Jaduka, Ifbyphone, Twilio, CloudVox
Many social networks
Lots of social networks
Summary
APIsLots of them! The question is - how to make a sensiblechoice, commitment to a given set of APIs?
Key considerationsReach, Price, Time-to-Use, Revenue Share, Geography,Skillset, Richness/Features
Hard stuffCall control, billing and payment, rich network access.No common APIs across operators/carriers.
Help?See links in backup slides
Links / References
http://oneapi.aepona.com/
http://developers.facebook.com/
http://blog.dial2do.com/
http://www.slideshare.net/sos100/presentations
http://www.alanquayle.comCEBP andVoice Mashups http://thethomashowecompany.com/
