It’s been looming and was long expected but today Vodafone announced it would embed its Vodafone 360 app store on two Android devices next to Android Market. Vodafone says their store would give partners a richer retailing experience than Android Market – but then they would say that, wouldn’t they?
But cheap puns aside, the move does have some legs: Vodafone uses Qualcomm’s Xiam personalisation engine, which provides recommendations based on user behaviour. They claim – and you may have heard that before in any number of my talks – that recommendations are a much stronger driver than promotions, stronger by a level of 4x to be exact. This ties in with my preachings: nearly 3/4 of all purchasing decisions (not only mobile, all of them!) are made on the recommendation of friends. And, alas, this is where “user behaviour” as the applicable pattern comes short: do I care how many, say, Amazon buyers of Grisham novels are also buying other authors’ crime thrillers? No. Why not? Because I don’t know these people. Do I care what my friends may think I like? You bet! Why? Because they know me and my tastes. Doh!
Anyway, back to Vodafone. They have realised (and, credit to them, admit it!) that a vertical implementation where you only get the full scope of 360 services if you have one of two phones doesn’t work. And, well, that’s somewhat obvious, isn’t it? Or is it a reasonable assumption that all my friends will all of a sudden (and at the same time) exchange their various handsets for a Samsung M1? No, I thought not either.
Vodafone did divulge a little data sniplet that must encourage them though, and that is that 360 customers have a 3x higher ARPU than others. If you look at the above (recommendations, friends, etc), that is not completely surprising. So now the next hurdle is to roll it out across their whole range of handsets. And let’s face it: a simple store won’t cut that on its own. Going cross-platform also means that – depending which handset you fancy – you may find different app stores of differing attraction competing with Vodafone’s own for attention (e.g. does Nokia’s Ovi offering seem to have more traction than, say, Blackberry App World but the latter has – from a publisher’s perspective – vastly superior price levels). All in all pretty sub-optimal, I think.
On a sideline: I will be moderating a panel on “How to Make Money as a Developer” this week at Mobile 2.0 Europe in Barcelona and I will be having the immense pleasure of having two operators on the panel (Orange and Telefonica-O2) as well as Microsoft (representing the OS side). This Vodafone announcement highlights some of the challenges the industry is facing. Interesting times!
First, Samsung announced it would drop Symbian from its smartphones in 2010 in favour of its new, home-brew bada OS. Then Nokia said it would drop Symbian (albeit not immediately) from its flagship N-series devices replacing it with Maemo, the OS that premiered on a Nokia device on the recently released geek dream, the N900.
It is said that there are
no current plans for Maemo devices in the [...] X-Series range or the popular [?] E-Series enterprise range
but the word “current” suggests that this might well change soon, too.
This would leave Symbian without its two largest OEM supporters. Will there still be a future for it?
Symbian of course boasts a still very impressive number of legacy devices, and it will therefore be here for a while. However, what does the long-term outlook look like? Android, LiMo, etc all “boast” a nimbler, more agile set-up, allowing for faster development and, arguably, better user experience. This is not necessarily Symbian’s fault (it carries with it its legacy around) but it makes it that much harder for it to reinvent itself.
I am not sure if there is place (and – timewise – the runway) to reinvent itself without the backing of big OEMs. I would be surprised if carriers would use it; they – even more than OEM – require adaptability and customization, which the newer platforms seem better suited to serve. Vodafone’s choice of LiMo for their first two Vodafone 360 devices is testament to that.
The ever-bright Tomi Ahonen suggested a comparison with DOS/Windows and MacOS: he compares Symbian to DOS, Maemo to Windows and iPhone to MacOS: MacOS led in UI and leads to this day. DOS outsold MacOS in spite of its dramatic inferiority because of the legacy instal base. Windows then overlaid DOS and rolled out on all the legacy devices with MacOS, as a result, always playing second fiddle despite its superiority.
The market place in mobile looks different though: DOS was nigh dominant (outside the mainframe and large enterprise side of things) whereas Symbian “only” covers about 5% of the current market. It is big but probably not big enough to bridge the DOS/Windows migration gap. With Android, Blackberry, Windows Mobile, LiMo, JavaFX (if that ever takes of properly), etc all on the map, too, the situation is very different to the DOS/Windows/MacOS world. Would Nokia be quicker in execution, I might still look at it differently but, unfortunately, it doesn’t seem to be that way.
So is it good bye, Symbian, then?
A new round of fragmentation looms. It is something I have been fearing for a while now: that OEM (and carriers) would make use of the open source of the likes of Android and LiMo to produce their very own flavour of apps. So after Vodafone’s 360 announcement (with customized LiMo storefronts, etc), Motorola announced so-called “signature apps” from a number of developers that are all delivered through Motorola’s new “Motoblur” user interface, which
is based on the Google-backed Android platform for mobile systems. Motorola [will] offer an additional SDK for its APIs beyond what is available for Android.
And then it said that
Over a period of time–we’re not there yet–we’ll allow the APIs to be available so people can develop many more applications than we can think of ourselves, but it’ll take us a little bit of time to mature ourselves to a place that we could open up APIs.
Ouch. An additional SDK. Which is not yet there yet. Whilst the Motoblur UI looks actually quite nice, this sounds suspiciously like another round of walled gardens, onerous internal and external QA, fragmentation and pretty much a fall back into the traps of the J2ME uber-customized world where one needs to support hundreds of devices for a commercial roll-out (with the trouble of course being that, all too often, that work meant that it would no longer be commercially very sensible). Oh dear…
It makes one want to call out for a quick advancement of HTML5 with Gears and all, so that one won’t need apps after all. The issue of connectivity and usability, etc would of course still be there. Such despair…
After much huffing and puffing, Vodafone unveiled yesterday what everyone had been waiting for for months and months: its new Vodafone 360 concept, which will replace Vodafone Live! It launches on – drumroll – LiMo-OS Linux phones from Samsung with touchscreen and GPS and, for the H1, AMOLED display (yum!), WiFi, HSDPA, etc, etc, etc. and also supports a fairly big range of Nokia (not on the N97 though!) and Sony Ericsson devices (although, judging by the screenshots, it doesn’t look as sexy on those).
The 360 thing is, according to the press release
a brand new set of internet services for the mobile and PC which gathers all of a customer’s friends, communities, entertainment and personal favourites (like music, games, photos and video) in one place.
It has an address book with nodes into Facebook, IM (Windows and Google) and will “soon” also cover Twitter, Hyves and StudiVZ (the German Facebook clone). Two tailor-made (!) handsets that use a proprietary (!) interface based on LiMo’s release 2 mobile Linux OS. Users can create groups across different networks (which is very neat!), an app store with 1,000 apps at launch (no word so far what this comprises) and syncing with your computer.
So is this the big thing then? Here’s the good, the bad and the ugly:
The Good
- The service reaches out. It acknowledges (this is a big step for most carriers!) that users have a life outside their carrier. Facebook, Live Messenger and Google Talk are a bit thin, I’d say, but let’s cut them some slack; the others will follow.
- It has a couple of neat twists built-in: I mentioned a few above but there is also a feature that uses some spooky thing called the “Vodafone’s proximity algorythm” and which basically automatically favourites your most-loved people: the most frequently contacted people (like your mom?) come closer to the front.
- At least on the custom-built devices, it looks much better than previous attempts by carriers to make something look and feel a little more user-friendly.
- I hear that the whole widget-thing should be really neat. Now, I haven’t seen any of it as yet but the concept sounds good.
- It works across different operating systems (at least LiMo and Symbian).
As a funny side remark, the PR blurb points out that
The beauty of Vodafone 360 is that all the services work together and they are easy to use.
So they weren’t before, huh? 
— sorry, couldn’t resist…
The Bad
Some commentators mentioned that the cloud-hosted address book and generally aggregation of contacts, networks etc through a provider rather than through the handset would tie people to the provider more closely (which might not actually be anything Vodafone would object to). I am not sure how tough it would really be (as you have your computer back-up), so easy on that.
It is still very much a closed-circuit affair: It is Vodafone and no one else. It is proprietary, tailor-made and not open. This is not good (and, yes, I know that the oft-cited iPhone is proprietary and tailor-made, too). Alas, its applications are not – unless your name is Spotify; then it takes a little longer…
The Ugly
The underlying proprietary thinking is nothing I can see working longer term. In a world that is (Vodafone press speak)
a substantiator of Vodafone’s new brand expression – ‘power to you’ – which is focused on putting the customer in control and enabling simple and easy to manage communications, both mobile and fixed
this is also a little bit of a contradiction.
But I will say that it seems to be the nicest operator-built environment I have seen so far. And for this to come from the world’s largest operator is no mean feat and might actually yield some results. Go on, guys, tweak it, improve it, show us!
I know this is a contentious headline but one could interpret the news that Qualcomm is opening its very own app store (which is probably the oldest one!) to any device on any platform on any carrier this way. The provider will open its Plaza service to non-BREW devices (BREW is proprietary to Qualcomm). This could be seen as an admission of defeat in the platform war, which it appears to be losing against GSM platforms.
The title of this post is not meant in any way derogatory but with all the hype about the iPhone it is sometimes easy to forget that we are talking about a niche product that will probably remain a niche product (albeit a powerful and cool one!). In the rest of the world (feature phones aside), a few consortia are fighting for the open-source market, which is – let’s face it – a considerably larger piece than the small premium segment served by Apple.
This week’s Carnival of the Mobilists is hosted by the formidable Caroline Lewko at WIP Jam. I am very happy to note that my latest post on Apple’s growing relevance as a gaming platform is included in last week’s line-up. For the remainder, there’s stuff on LiMo (for some background on where they came from see here) and some very worthwhile piece on mobile marketing amongst much more. And now go to read it here!
An article tells us that AT&T Wireless intends to run all their phones on one platform as soon as 2014, namely on Symbian. Is this odd? I mean: the iPhone isn’t Symbian, is it?
After delays on the part of the much awaited Android (see my original take on that here), one of the “other” Linux Mobile initiatives, namely the LiMo Foundation announced the release of its first version (“R1″) on schedule for March. The beta version of the respective APIs is available on their website immediately. They also said there would be sneak previews of all the good things at next week’s Mobile World Congress in Barcelona, and I will be sure to check it out!
The LiMo Foundation, which is backed by an impressive number of industry heavyweights (quite a few of which are also members of the Open Handset Alliance, the maker of Android), seems to be moving swiftly ahead, and their platform is, in their own words, basically the following:
“The LiMo Platform—leveraging standards and open-source projects—is a modular, plug-in-based, hardware-independent architecture built around an open operating system, with a secure run-time environment for support of downloaded applications. Linux was selected as the core technology for the LiMo Platform for its acceptability by the whole mobile industry, its rich functionality and scalability, its record of success in embedded systems and mobile phones and its potential to easily “cross-platformize” with other product categories.” Middleware components for the platform can apparently be implemented in either C or C++ programming languages.
What seems noteworthy is that the good folks at the foundation seem to have managed to leverage the substantial resource of its members. Its chairman praised “the transparent, balanced and harmonious contribution process [...].”
Just before Christmas, the third consortium, LiPS, had announced that its first release was now complete.
However, it would appear of not so much being a race of who is first but of who manages to deploy on most devices. Given the membership of the three consortia comprises most of the big players (with the notable absence of Nokia although its recently acquired Trolltech is a member of the LiMo Foundation; read the excellent analysis on that deal here), one might ask if would not be perhaps the best idea to merge the whole thing, and deploy one common platform. Wouldn’t that have real impact?
Now there’s been a lot of talk about Linux Mobile recently, with all that Google‘s or rather the Open Handset Alliance‘s Android stuff floating around (see e.g. here and here), and the good folks who aim to push this operaing system are quite naturally busy to ride the wave of excitement and attention over this (and are always very keen to stress that Android is a welcome addition to the forces rather than a bad competitor). LiPS is one of two consortia besides Android (the other being the LiMo Foundation) who intend to further the footprint of Linux in mobile, too.
And, just in time for Christmas, LiPS (whose members include Orange, France Telecom, MontaVista and Access) now has released its first specification. Well, to be honest, it is only the second half of what was already released in June but, hey, now it is complete: it provides APIs for telephony, messaging, calendar, instant messaging and presence functions, as well as – unspecified – “new user interface components.” LiPS stresses that it wants to allow developers to develop applications that will work on all phones under the standard, and from that point of view the voice API should be particularly interesting (voice-controlled games? Ah!).
Unlike its “competitor” (compatriot might be the better word) however, there have been no news on any handsets developed under that specification yet. The LiMo Foundation scored first-line honours here with NTT DoCoMo recently announcing its impressively spec’ed P905i (by Panasonic; using the Viera brand – see here for similar use of brands) and N905i (by NEC) handsets released under the LiMo Foundation specs (see for a showcase of the FOMA 905i series here and here).
A lot of action happening, and good stuff, too! Now, bundle your resources, folks, and conquer!
Verizon‘s U-turn continues: the carrier now announced that they would support the Android OS promoted by the Google-led Open Handset Alliance. This comes only days after Verizon was met with a lot of raised eyebrows after it declared it would open up to handset manufacturers, service and application providers. Upon the launch of Android, Verizon was amongst a select few that were visibly reluctant to support the initiative, reportedly for fear of impinging on their customer base by not being able to control the user experience.
This move may well be an attempt to prevent Google from bidding in the 700 MHz spectrum, the auction for which goes ahead tonight: Google may not see the necessity to bid just as aggressively if it can basically fall back on an OS-agnostic carrier as it can then continue doing what it does best, namely sell ads. The proximity of the dates may indeed point into that direction.
Verizon Wireless had created the most profitable U.S. cellular business by tightly restricting the devices and applications allowed to run on its network. However, its management apparently now came to conclude that it was time for a radical shift: this will have been out of fear to be isolated in a niche when the rest of the market was overrun by new, more powerful devices as well as media empires old and new both of which would bring a richness of offerings mid-term that Verizon could not have supported within the constraints of its tightly-controlled environment.
It may also have thought that opening up would help them to keep growing while containing costs; probably a bit of everything. That last bit is of course one of the reasons that led many partners to throw their weight behind the various OS campaigns that recently appeared to have picked up pace: the LiMo Foundation, C-based Nokia-owned OS Symbian and the Sony Ericsson and Motorola-owned UIQ (in which Motorola had just acquired a 50% stake; see here) will also be driven by the OEM’s attempt to contain cost. Unified OS make mass production much cheaper (and the famously robust Linux kernel also will allow stability whilst being flexible enough to allow enough flavours to keep every marketing and UI expert happy, too).
Everyone coming to their senses? Oh, brave new world.
So, no GPhone — yet. Google, with quite a number of partners, today announced the already much-rumoured “Open Handset Alliance” under which a Linux-based OS, nicknamed Android has been launched (the SDK will allegedly be available in a week’s time). Here’s a video explaining the deep thoughts of the creators (be quick: YouTube has removed it already…).
The whole industry had been waiting for this, and Google seems to have come up with a black-white thing: it goes back to its roots in open source but overlays it with Java, which has caused the content community a lot of headaches (every mobile phone translates it slightly differently, so one needs a gazillion ports). However, Google has teamed up with no less than 34 partners for the launch alone, including such giants as China Mobile, KDDI, Sprint Nextel, TIM, T-Mobile, Motorola (who seem to be dancing on a lot of weddings recently: UIQ and Linux Mobile are also on their plates), Samsung, HTC, Intel and eBay.
So what does it all mean? According to the members of the alliance, it will be better, bigger, faster for everyone: open source means more applications, less bugs and less cost. According to Google CEO Eric Schmidt, it is “a fresh approach to fostering innovation in the mobile industry will help shape a new computing environment that will change the way people access and share information in the future.” Commentators note that there is apparently one caveat: you’ll have to use Google for navigation. Now: does that bother anyone? Give me Internet on my phone on broadband speed and I happily surf with whoever gives it to me, I’d say. To enact a platform, supported by a lot of sector muscle, that makes the developers’ life easier should be good for everyone indeed as it will undoubtedly bring more usage. Traditionally, carriers feared for the consistency of the user experience. Apparently, Verizon and AT&T have already voiced such concerns also here although the explanation sounds defensive at best: they fear too much advertising. Would it be safe to say they rather fear loss of control?
Quite a few companies have tried to take on mobile as the next frontier and quite a few fared rather miserably on the complexities of the environment presented by the sector (Disney’s MVNO attempts, Infospace and a few others spring to mind). With Google’s might this might be about to change though. A fresh breeze and a unified development platform would, in any event, be a good thing.
Interesting though that, as in recent releases on OS-driven initiatives, Nokia is again absent. This is not promising any good in terms of unifying the landscape, it seems. However, both Linux Mobile (on which Android is apparently based) and Symbian (in which Nokia holds a huge stake and which it intends to make its platform of choice) are C++-based. And that would be easing development pains after all: much easier to deal with than the Java layers, which until now were statutory but might only be optional going forth.
UPDATE 7 Nov 2007: Nokia has said its participation in Android is “not ruled out at all”. It would work with it if it would see sense. Now, a convincing statement sounds differently but it IS noteworthy that the Finnish giant felt the need to comment on it so quickly.
US handset maker Motorola acquired half the shares in UIQ, the smartphone software unit, from Sony Ericsson. Sony Ericsson had bought UIQ from handset OS maker Symbian last year. UIQ is essentially a graphic interface adding components to the Symbian OS. Symbian in turn is 47.9% owned by Nokia. Under UIQ, native programming can be made in C++ although the software does support the – in the mobile games space – ubiquitous J2ME standard. Motorola’s new flagship Z8 (nicknamed “MotoRzr” as in “riser”) is running on it already. The battle of the OS giants begins…
It is an interesting move since Moto has been the most active OEM for the use of Linux Mobile: it has released a whole range of phones for the open source OS featuring the penguin. It is also one of the founding fathers of the LiMo Foundation, an initiative it embarked on together with industry heavyweights NTT DoCoMo, Vodafone, Samsung, NEC and Panasonic (and which was recently joined by LG, McAfee, Broadcom, Ericsson and others). Now, I understand that Linux and C++ work together but must admit that my knowledge is more than limited here. It is in any event noteworthy that Motorola goes with a UI based on Symbian rather than straight-forward Linux. Motorola was quick to state that UIQ would only be “one of the actions to support [a] strategy” adding more investment in multimedia product segments.
With hundreds of millions in development cost at stake, it is probably too early to tell but it certainly is a new twist in the quest to uproot Nokia‘s top position with the Symbian s60 platform. So, what’s next?
