Tag: android Page 7 of 11

Spotify Mobile: 3UK bundles with HTC Hero

A couple of weeks ago, I pondered Spotify’s impact on music business models and suggested that mobile may have a role to play in the monetization end of it (which is, unless you’re Twitter, an inherent part of a business model indeed). It didn’t take them long:

Today, the UK arm of 3 – always one of the more creative carriers – announced a handset (and not a bad one either) to be bundled with Spotify Premium (i.e. on the go and no ads): users will pay £99 up front, and then £35 a month for 24 months for a tariff including a Spotify Premium subscription covering both PC and mobile, 750 minutes voice calls, unlimited texts, data and Skype-to-Skype calls. Listen up: all bandwidth included. For a streaming service. Now we’re talking!

3 said that the Spotify Premium service was

worth £240

which suggests that they might want to stick to the £9.99 price point (which would surprise me). But then it is hard to tell which bit of such announcements is marketing and which actual price-setting for the sake of royalties and such like…

3 also said

that the deal with Spotify would extend to other products in the coming months, including 3’s mobile broadband service.

Again, I am curious about the price point: the way it is, it would be a nice marketing deal for Spotify but it could be said that not much was going for taking exactly that offer vs just signing up as it is already. A little discounted however (with the difference paid for by 3’s marketing department) might change the ball game altogether…

It’s all good though: I for one am truly intrigued by the prospect of having more than 6 million tracks (equating to, what?, 6 terabyte or so of music) on my phone!

And one little thing on the side: it is – again – an app and not the mobile web that they choose – in spite of bandwidth apparently not being an issue at all. It is thus another argument for the superiority (for the time being) of apps over mobile web when it comes to UI and input constraints.

Motoblur & Android Fragmentation: The Follow-Up

Yesterday, I blogged about Motorola’s Motoblur UI, which adds an additional SDK for its specific APIs beyond the standard Android stacks. I reckoned that this might mean more fragmentation, which would push it a step closer to the nightmare that was/is J2ME.

I received two quick reactions to this: one reader commented that this was only bad if you wouldn’t have good tools and compilers. To him (@tederf), I would respond that, while it is certainly true that good tools reduce the friction, raise efficiencies and alleviate overall pain, the smallest common denominator is always just that. In my previous companies, we used to produce up to seven or eight different J2ME builds in order to maximise performance of our games on the huge spread of handsets. Could we have done with one build? Probably. Would the result have been great? Almost certainly not!

Anyway, the more interesting reaction came from the good folks at Motorola themselves. They reckoned (via Twitter; they are @motoblur) that:

with all due respect, I feel you’ve misunderstood motoblur, and android fragmentation concerns are a wee bit overblown.

Now, now. I offered them a guest post here in order to explain this further. I have unfortunately not yet had a response (which I take, applying Twitter attention spans, as lasting silence). But I still wanted to use the opportunity to elaborate a little more on this (and, no, I will not lament Moto’s lost opportunity to feature their wares on this humble site).

To clarify a couple of things outright:

  1. I would be delighted would I be mistaken (and note that I am not a techie, so this is a distinct possibility!).
  2. I would be equally delighted would Motorola manage to regain some of its lost ground. The world clearly would be a better place with another strong manufacturer regaining old strengths (although maybe with better UI this time around – which Motoblur certainly seems to offer [see picture on the right of the Motorola CLIQ!).

But let’s go back to the general issue of Android fragmentation threats (the fact that I pointed this out – again – en cas de Moto is of course purely coincidental).

So let’s dive in: with open source software, there is always the intrinsic possibility that fragmentation will occur. Why do people customize it? Because they can! vendors, developers and operators that make up the Open Handset Alliance (which releases Android) can tweak is in whichever way they like (or “need” to) and for any number of reasons: to protect IP, to optimize performance on their network or for certain devices or simply because they feel they need some distinguishing factors, some degree of uniqueness. The result can be, however, as one analyst puts it that

there will be multiple flavors of Android, all of them incompatible with each other. That, in turn, necessitates different versions of each application or updates to accommodate the entire device ecosystem. On the whole, such activity negates the cost efficiencies inherent in the idea of a standard, open operating system, and potentially makes the Android Market a confusing place to shop for widgets.

And that’s what you call fragmentation. Interestingly, there were rumours that Google had made the Open Handset Alliance members sign “non-fragmentation agreements” but it seems that this is either not true or not enforceable.

Others point out that HTC, Samsung, Dell, Verizon, (may I add Motorola?) all have phones on the way that run on different software to the others. Reports of version conflicts, lack of backward compatibility, etc, etc. I mean, hell, there is even an “alternative” Android app store (with 223 apps as of tonight)… Sounds familiar?

Dear Motoblur, if it is different with your SDK, please enlighten us! I am sure I will not be the only one applauding!

Image Credit: http://www.visionmobile.com

More Fragmentation: Android & Motorola’s Motoblur

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…

droidcon: Android Conference, Berlin (4 Nov 2009)

As Android continues to roll out (at least 18 devices by year-end), the ecosystem around it starts to sprout, too. To highlight this, an Android-centered business and development-oriented conference, Droidcon, will hit Berlin on 4 November, and I will be giving a keynote on licensing models and open source (full programme here).

It looks like a very exciting event, so I’d like to encourage everyone to come (there are 4 parallel tracks, so you do not have to listen to my ranting…)! Register here (and, no, I do not earn a commission).

I’ll post a little preview on what I will be talking about more specifically ahead of the event, so stay tuned.

App Bonanza or Analyst Bonanza?

In the last two days, two forecasts informed us about the value of the mobile app market in – convenient as ever – the distant future that is 2013. US analyst firm Yankee Group predicts the US app mobile market to be worth $4.2bn by then. Today, British analyst Wireless Expertise (run by former Netsize exec Anuj Kanna) topped this easily by predicting the (global) app market size to be $16.6bn by that time (free copy of the report here).

I can hear your moans…

However, let’s have a look at the numbers then, shall we? At the end of 2008, there were 4.1bn mobile phones in the market. Because apps tend to thrive most on smartphones (and the analysts seem to thrive on them, too), let’s have a look at that sub-sector. I would estimate the smartphone share to being somewhat under 10% (Symbian claims c. 250m devices in market, Apple has some 30-odd million, so RIM, Windows Mobile, Android, Palm, etc should probably be OK with the balance of some 100m). In Europe and the US, the share is much larger but in the big volume markets China and India it is bound to be much smaller, at least for the time being. Global smartphone shipments in 2008 were around 140m.

If we estimate a 20% growth year-on-year for smartphones (vs. 5% for the overall phone market, which seems to be loosely in line with the general dynamic), then we would end up with something like 900m smartphones by 2013. Yankee Group predicts that smartphones in the US will quadruple by then (from 40m to 160m) and does not seem to be very far off. Wireless Expertise thinks the global number will be 1.6bn, which again, might not be that far off.

The question is however if people will really download this much stuff: Yankee Group predicts that the actual value of the market will rise 10-fold and that the average price point of an app will be $2.37. Why that is so, you ask? Well, pay $495 and you will know; I don’t…

Now, the good folks of Wireless Expertise see the thing quadrupling until 2013. They do, however, count “ordinary” mobile games as they are being sold through carriers amongst the apps, which means that their starting point is higher, namely $4.6bn in 2009, so they’re looking at this quadrupling. They raise some smart points on app stores and how they (well, it) changed the way users access and consume content, how carriers will need to look for alternatives to increasingly commoditized voice and messaging propositions, etc. But why there should be a 400% rise in e.g. traditional J2ME mobile games remains – whilst it would be wonderful – pretty much in the dark.

Talking of J2ME and feature phones: I do not know how they are being woven into the equation but there would certainly be a wide field for any self-respecting crystal-ball-reader here: on the one hand, app consumption on such devices has traditionally been fairly shabby but, on the other hand, this could well change if connectivity, bandwidth, UI and the right price plans would come together to offer a compelling mobile web solution. So then apps would need to be translated into widgets or something like that. Would users then pay for them? Don’t know. Or would it be the “Freemium” model according to which “Free gets you to a place where you can ask to paid?”

The challenge of these reports is their “simplified” assumptions: if only one of them fails, you go “oops”, and your prediction is halved (or worse). On Wireless Expertise’s case, this is particularly clear: their assumption is that there will be a dual strategy of (presumably OEM-driven app stores) and mobile web-based widget stores. Now, they further assume that Ovi, Windows Market, etc will all be as successful as Apple’s App Store. By early (anecdotal) data, this could not be further from the truth (see here for what that may mean). Nokia in particular struggles to get its head around a viable and compelling media strategy (cf. here and here). And hence the beautiful hockey stick would actually fall flat on its face.

Now, I am not predicting total doom and gloom, in the contrary. I do think that Apple’s wake-up call has brought a much-needed new wave of innovation and I also believe that this will be successfully incorporated by some carriers and OEMs. But by all of them? Not very likely.

And so we see: the reports are a touch on the optimistic side when it comes to volumes and assumptions. But, hey, that’s their job, I guess, and after all they have at least dropped their masks now: Yankee Group call it fairly openly a “gold rush”. And what happens then we had been shown a long time ago: you end up eating your shoelaces. So maybe this is less of an app bonanza and more of an analyst bonanza then…

EA Mobile, Namco Bandai and the State of Carrier Decks

After many rumours and ominous statements that it was “reviewing its activities” Namco Bandai confirmed today that EA Mobile will thenceforth act as its distributor for mobile games outside the US and outside any app store.

After Taito and Eidos, EA Mobile just gobbled up another major distribution deal and the exodus from J2ME games distributed via carriers continues. It also means that EA’s dominance over the operator decks has just increased a little more yet again. It had estimated (back in June) that its 2009 mobile revenues would reach $185m (although this arguably includes Apple’s and other people’s app stores as well as embeds).

What is worrying is that this cements the oligopoly of games distribution in all major markets. EA Mobile, Gameloft occupy the top 2 slots very comfortably with Glu an equally comfortable but distant third. I-Play, Digital Chocolate, Real and Connect 2 Media are fighting for place and Xendex, Handy Games and a few others seek (and sometimes find) niches to prosper. THQ Wireless, Vivendi Games Mobile have departed. Player X found a new home under the mighty wings of Zed. And then? If the above companies all manage to maintain a healthy business, this might be enough; there are silverback gorillas in every market segment. If not though, this might become a doomed sub-sector; the limelight would then be on the (failed) ecosystem operators tried to build: overly fragmented with everyone of them wanting it just so and just their way rather than agreeing on a largely unified structure and processes pressed margins from a system that has been tough from the outset (handset fragmentation and international spread mean fairly high cost per capita anyway).

The accumulation of external properties arguably also mean that EA will need to run a business that is almost a combination of a publisher and an aggregator (with its very own challenges). The issue of shelf position (will they give Tetris and the Sims undue preference over Space Invaders, Pac-Man and Cooking Mama?), the commercials of their own deals (they anecdotally paid Hasbro a handsome sum), and the generally dominant position will all come into play and it is inconceivable (well, is it really?) that their partners will continue to play ball.

It might of course only be a brief interregnum on the way to an app store world. Smartphones are very much on the rise and, in that world, such stores seem to rule. Apple has taken the lead, Android followed suit and new stores are springing up almost by the day, which also includes operator-led ones: Orange already has one, Verizon Wireless has announced one (mobile web-based) and so has Vodafone (which might actually be bigger than Apples) as well as many others. The OEM all do the same (even though some carriers want to disallow them): Nokia Ovi, Blackberry App World, Sony Ericsson, LG, Samsung, you name them, they have it. The question of course is if that might mean the same thing all over again: will they again want it all just so? Will they again have it just their way so that a user would have the unique flavour of operator X on handset Y in this unique way, meaning that – again – thousands of SKUs would be required to service them? Groundhog Day? I hope not!

Image credit: http://www.antitrustreview.com/files/2007/07/files51lsaydhrsl.-ss500-.jpg

Is Spotify finding the Business on the Move?

Spotify was a breath of fresh air when it hit the markets. Finally, there was someone who combined the ease of iTunes with unsurpassed breadth in catalogue. Lots of songs. Always available. And even the ads weren’t all that bad (which is why few people upgraded to the ad-free premium version [more on this below], much to the dismay of label executives who – rightly – fail to see the greater good of dependable revenue streams from those few ads; although they are getting more, mind you).

Then, back in July, Spotify submitted its iPhone app to Apple. And the big wait began. After lots of back and forth and speculation if it would or would not, Apple finally approved the app. So now it’s live, and not only on the app store (where it ranked #1 on the UK store when I checked tonight) but also on Android Market. A Symbian version is in the works.

All reviews I have read are raving: from “very impressed” (and that’s the Daily Telegraph no less) to having “to pry it out of my cold, dead iPhone” (Wired), everyone waxes lyrical about the thing. It comes with a load of stuff, too: streaming all your favourites from over 6m tracks on the go sounds promising, and one can also sync up to 3,333 (what a number!) songs for offline use in the networks’ broadband doldrums.

The trouble (!?) is: you can only use it as a premium subscriber, which means forking out £10 per month. Which brings me conveniently to the key point, which is the business underlying model.

The labels are fairly happy, it seems. Because they got shares in Spotify itself. Some more equal than others though: the majors are said to have received a disproportionately high stake). The same report claims though that ad income is only £82,000 and, in the UK, only 17,000 users had signed up for the premium version. However, shareholders and all that, Spotify still has to pay the labels a fee per streamed track, irrespective of the user paying or not. Tricky model, that. Note though that this might be different in other countries: according to reports, the world’s largest major, Universal Music is making more money from Spotify in Sweden than from iTunes!

Anyhow, all this was before the mobile app, and mobile may well be the game-changer for them… The launch of the iPhone app, glorified niche audience or not, seems to have gone fairly well (#1 position on fhe app store within days of launch). Spotify reckons that mobile is where its future lies. And this had been echoed (and well ahead of the actual launch!!!) by others in the industry, and perhaps rightly so: if users are used to (and in love with) a service they are more likely to pay for it if that means they can also have it whilst on the road. For the marriage of music with the world’s leading MP3 player come mobile phone, the iPhone, this seems to be made in heaven: I can have the smallest model and still carry 6m+ tracks around with me? Wow! Here’s value-add!

The much-discussed freemium model it is then: get them hooked on the free desktop app and convert them to paying users on mobile. It has long been known that users are more likely to pay if stuff is portable (I can still recall the disbelief of music executives when they realized that people would pay more for a monophonic ringtone than for a full-blown music track). And whilst now the link between (free) basic service on the desktop and (premium) mobile service is new, the principle is old and proven: and it is simply added value (plus the little things like being used to paying on mobile and having convenient existing billing models in place). If the user perception is that they are getting value for money, they are willing to pay. And if it is for such a fairly special thing such as music (don’t we all love and nurture our very own musical mix tastes?), the step is even easier to make.

Spotify fully expects this to fly: they are upgrading their servers already. Labels are said to be still a little jumpy but I reckon their experiences over the last decade or so have shown that their is a need to re-think incumbent models…

Page 7 of 11

Powered by WordPress & Theme by Anders Norén