Creative Connectivity - the site for eHealth, telematics and wireless

OneAPI to bind them.

February 20th, 2010 |  Published in Wireless Connectivity  |  3 Comments

There’s trouble in Mobile Earth.  Or so it appeared at the Mobile World Congress in Barcelona last week.  Darkness is spreading throughout the networks, as the twin towers of Apple and Android continue to suck application developers into their empires.  But help was at hand.  Step forward those plucky little hobbits at the GSM Association.  Prior to the Conference their ivory burrow had been echoing to the sound of furry feet as they hastily put together the Wholesale Applications Community (WAC) to thwart those twin evils of the cellular world.

ARPU is precious.  Brand is even more precious.  As without that, you’re just a data pipe.  But both are fading.  The only thing that consumers appear to value these days is downloadable apps, and lots of them.  Last year at MWC, every operator was busy launching their own Apps Store.  A year on, the cellular shires have realised fighting alone didn’t work, so they’ve banded together to pit their combined forces against the dark empire.

It’s an odd alliance, and probably one that is doomed to failure. 

The Wholesale Applications Community is an alliance of twenty four operators, along with Sony-Ericsson, LG and Samsung (a.k.a the handset vendors who don’t have their own high profile apps stores).  This fighting force has been assembled by the GSMA to develop an open platform to deliver applications to their users.  Or presumably those users who don’t own an Apple, Android or Nokia handset.  Essentially, it’s all about supporting widgets, which isn’t a bad thing, by building on the JIL and OMTP BONDI standards. 

I’m assuming that JIL and OMTP think it’s a good idea, as it gets them into more devices, but neither were excited enough to issue a press release.  For that we had to rely on the GSMA.  They waxed lyrical about the way it was completely in line with their principles, and leveraged the work they had already done on OneAPI, which also got its own release.  I’ve always been a bit sceptical about OneAPI, as I don’t see why compelling mobile applications needs to know much about the network.  The good old wired internet seems to have done quite well without a similar knowledge of the ISPs and the grotty last mile of cable.

Which brings me back to that question of doom.  For that I’d like to digress into a brief discussion on jobs and hiring.  Not the sort you and I hanker for, but the rather elegant theories of Clayton Christensen at the Harvard Business School.  If you’ve not read his books, I’d recommend them.  He highlights the distinction between the world where marketeers think they know what consumers want, and what consumers actually do.  In his world, consumers have jobs that need to be done, like constructively wasting their time, or amusing their friends.  Hence they hire a service to fulfil that job – in this case, downloading an app from the iPhone store.  Business models that are successful work on the premise of understanding the job that the consumer needs to do.

My concern with the Wholesale Applications Community is that it doesn’t do that.  Instead it looks at how it can imitate a competitor without understanding the consumer’s job requirements.  Hence I suspect it may quietly die.  To see why, we need to look more deeply into the Apple and Android models.

What most analysts and commentators seem to ignore the fact that Apple didn’t invent the Apps Store model.  Credit to that goes to NTT DoCoMo in Japan, who put all of the pieces in place when they launched their i-mode service back in 1999 (yes, that was back in the last century).  They realised that if everything was going to work they needed to own the handset, the protocols, the application platform, the interfaces, the network, an equitable revenue split with the application developers and a light touch control of the applications themselves.  In other words, you need to own everything in the chain.  A number of European operators tried to bring the i-mode model to Europe, but broke it by trying to change key parts of the model, breaking that end to end ownership.  Apple’s bright idea was to realise that there was one part of the end-to-end chain which you could remove without breaking the model, which was the network pipe.  Their genius was to use the brand awareness they’d already built with the iPod to persuade the operators to let them own every other part of the model.  The rest is history.

i-mode is still going strong in Japan, with 48 million users and growing.  This should be a source of concern for operators, as it suggests that if the Western public behaves in the same way, they’re not going to get bored with their Apples and Androids and switch to something else.

Rather than relying on the hobbits to pull WAC together, what the industry needs is some real wizardry.  At Barcelona, that came in the form of Tadashi Onodera, president and chairman of Japanese operator KDDI.   KDDI don’t support i-mode, having gone down a 3G route, but they do duplicate the end to end control with their iida phones and services.  What Onodera-san was talking about was differential data pricing on an IP network.

Differential data pricing is about being a much smarter pipe, where an operator finds ways to justify billing differently for different data usage.  On a very basic level, my network does that today.  They charge me around 25 millipence for each SMS character I send, but only 4 nanopence for the same byte of internet data.  Which makes SMS data about six million times more expensive than internet data. 

KDDI don’t see why there should be a binary pricing structure, but instead believe that specific value should be assigned to different data usage.  So far, that’s a policy that’s noticeably absent from Western networks.  The Kindle is one example of how it can be done, but the fact that it is still largely tethered to a few U.S. networks illustrates how alien the concept is.  Which is a shame, as without that kind of thinking, flat rate is going to be a very heavy cross to bear, whether or not WAC works.

So the Wholesale Applications Community may just be a reality avoidance strategy that deflects from the more important underlying issues.  The whole thing is aimed to be complete in 12 months, just in time to announce it at Mobile World Congress 2011.  Or do I already hear those furry feet scampering round their ivory burrow looking for a next year’s new initiative?

3 comments ↓

#1 David Rogers on 02.21.10 at 2:05 pm

You’re missing a point here – applications are steadily moving towards widgets and web applications anyway. A large number of the apps in the Android market and for the iphone are essentially web apps. It is very very easy for these to be converted for any platform (provided there are consistent APIs across devices – which the JIL and BONDI technology solves).

The iphone and Android devices cover relatively high-end users at the moment, whereas WAC is likely to also cover mid-range RTOS devices as well as all other platforms. It gives developers far more access to consumers and consumers far more access to applications.

#2 Nick on 02.22.10 at 5:45 pm

It was not my intention to denigrate widgets or web apps. They are important for building a uniform user experience across handsets and giving developers a wider platform. What does concern me is that the WAC is a publicity stunt, and as such something that may hinder rather than help that development.

If the announcement had included any one of Apple, Android or Nokia, then I might think differently, but it sounds like the rather pathetic scream of a toddler who wants the same toy as its siblings. Rather than being a well considered initiative, it seems to have been cobbled together at the last minute. The WAC website was only registered the previous week by O2, the content on it is derisory, particularly for an organisation that is promoting web applications, the main standards – JIL and BONDI didn’t have enough notice to issue press releases, and from all accounts, the GSMA was still desperately signing up operators the night before the launch.

I have no problem with well considered industry initiatives. I do have a problem with ones that are made up for PR events. They have a nasty habit of deflecting people from the real work in hand, as everyone sits back in the reflected glow of the media coverage and forgets to do anything. I suspect that the WAC falls into this category.

In may be wrong, and only time will tell. The WAC domain is registered for another 351 days. Lets see if the community lasts that long.

#3 Kevin Smith on 02.23.10 at 10:34 am

Hi there Nick,

Nice to see the Tolkein references, although I can assure you that OneAPI was not forged by Lord Sauron in the Land of Mordor where the shadows lie, but rather around the corner from Chancery Lane Tube station (a lot more convenient for Hobbits 😉

Just to clarify a couple of points:
– OneAPI is a network API. It is less useful for mobile applications as you point out – these are well served by widgets, BONDI and all the native libraries already. Instead it is more aimed at desktop web developers who may want to query a mobile network for information to enrich their web app. For example at the demo stand we had a geofencing desktop browser application – where friends/employees across various operators were tracked by triangulation of their phones and could be SMS’d when they reached a certain area. The network provided the remote fix and messaging, which was then mashed up with Google maps and tiny URL. With the first release of OneAPI we are not trying to be groundbreaking, just make it much easier to use these network code snippets in existing apps. Our SDK has AJAX, Java, PHP etc. libs to help this. Subsequent releases have features requested by developers such as video streaming Quality of Service, knowledge of a phone’s data connection strength, and ‘waking up’ phone applications remotely via SMS/UDH. All of which will be couched in Web-friendly and simple APIs – no Telco PhD needed…

Note that the payment API is probably the most attractive for native mobile applications as it can provide ‘charge to bill’ across operators, which is not a native device capability. Any device OS with HTTP capability can access OneAPI – security and consent/privacy are of course implemented to avoid fraud/spam.

– OneAPI is based on OMA RESTful API definitions, and is due to be standardised in the next few weeks – the standard is available for anyone to implement. In future releases we hope to addd support for other networks (fixed, broadband, satellite) based on developer feedback.

Many thanks!
Kevin
OneAPI project leader, Vodafone.

Leave a Comment

About Creative Connectivity

Creative Connectivity is Nick Hunn's blog on aspects and applications of wireless connectivity. Having worked with wireless for over twenty years I've seen the best and worst of it and despair at how little of its potential is exploited.

I hope that's about to change, as the demands of healthcare, energy and transport apply pressure to use wireless more intelligently for consumer health devices, smart metering and telematics. These are my views on the subject - please let me know yours.

You can Subscribe via RSS »