Category: OEM Page 3 of 15

Movie Licenses on iPhone a Failure?

I have been dealing with movie and TV licenses for longer than I care to remember, and the pattern (with few exceptions) always was the same: the licensor comes to you saying that, because they are offering you (the publisher) a well-known movie/TV/entertainment property that everyone and their dog are fans of, you should pay them a healthy amount of money (either up-front or as a minimum guarantee against revenues) for them to grant you that license. This means that the publisher starts at a point of significant loss: a six-figure guarantee (and I’ve seen larger ones, too), six-figure production costs and little mitigating the risk that the title might totally tank.

However, in the “old” world (scil. pre-app stores “as made famous by the iPhone”), people considered themselves to be lucky to get their hands on a well-known property as it would at least guarantee one thing, and that was “deck placement”, namely a good coverage across those coveted feature slots on carrier decks around the world. If you had the distribution network and delivered the package, you had a decent chance of making your money back (this even worked with a rotten game that was based on a movie license for a hilariously successful movie).

All new in the App Store World

Enter the “new” world of OS-driven app stores. The formidable Jeremy Laws published estimates of how movie & TV-license-based games were faring on the Apple App Store, and the results are – though not horrendous – humbling indeed. Only a good half dozen titles broke into the top 20 (by sales) in all of 2010. Not a single one ranked in the top 150 (!) of the top-grossing category. The average revenue was estimated by him to hit $1.3m. Now, don’t let yourself be blinded by this 7-figure amount: top-tier movie titles don’t often come cheap and the games behind them need to be reasonably faithful to the blueprint the movie gives you. Otherwise, the IP owner will not approve the game and the revenues will be, well, non-existent. Add to that a revenue share that the IP owner will earn even if the aforementioned guarantees are being settled, it slims down the margins fairly dangerously.

IP Doesn’t Pull as It Used to, or Does It?

The big news is however that the old formula big license + some sort of game = exposure does obviously no longer work (at least not in the same semi-automated way as was the case). With decent relationships into Apple, a good game for a good movie might still get a feature slot somewhere. However, the fact that none of the titles sampled in the above blog post were anywhere close to the top-grossing list shows that the pulling power has greatly diminished. How’s that?

Movie studios and TV production houses (and not only them: sports clubs are good at that, too) traditionally view a license as secondary exploitation of their intellectual property. The rule of thumb for a movie was that the box office should recoup the production costs and the secondary exploitation (DVD, TV rights, merchandise and, well, licenses) would provide for the profits. It is very much an analogue approach in which a scarce good is and will remain scarce unless its producer will (can?) change that scarcity. It does not translate well to the fluidity of a digital environment (with, normally, many more alternatives to access and consume media). It worked in old-world mobile because that ecosystem functioned very similar to a vertical supply chain. No more.

Game publishers suffer (or at least some of them) suffer from a similar perception issue: we have always done it that way… Well then…

A License is a Brand Extension

However, the huge differentiator is the ability to use (and exploit) the interactivity digital media offer and use it as a marketing and promotional channel. Now, a simple adaptation of the movie’s theme into a (traditional) game will not cut this. But more innovative approaches that utilise the ability to communicate with fans opens so many more doors to a) maximise the core proposition (selling cinema tickets, DVDs, digital downloads and such like) and bind people to the brand for longer (which is a potentially huge win for the cyclical movie business).

So, Jeremy’s charts “only” show us that only a few (if any) of the IP owners (and, arguably, publishers) “got” that so far. The opportunities for such an approach are huge.

What anyone who speaks to rights owners over licensing movie and TV properties should do though is take a copy of that chart for your negotiations. And then tell them how they should really treat it: it is a brand extension that leverages the core IP rather than a meagre spin-off license! Seen this way, there is significant opportunity for studios to secure their primary revenue streams and build a new rapport to their audiences. In particular the latter surely is of a value that exceeds six-figure guarantees anyhow.

So I guess we have to thank the iPhone again for breaking open yet another paradigm. And it was time for that, too!

What matters: Handsets or Packages?

It is this time again: my phone contract comes up for renewal. And – as anyone who is following this blog will know (to recap, look here), I have not been all too happy with the treatment I got from O2 UK. So today I started looking around. Given my rather fat tariff requirements, carriers normally throw in all sorts of goodies (scil. free handsets), so started there. I have an iPhone 4 and a Nexus One already, so started to see what else is out there, as there are:

Then I started looking at where, what, how I could get it and at what price, and the UK carrier labyrinth was entered: The Omnia 7 is carried by 3, Orange and T-Mobile, not by O2 or Vodafone (at least I couldn’t find anything to that end). The HD7 is an Orange exclusive, the Trophy is a Vodafone exclusive. The Galaxy S and the N8 seem to be with all of them.

Step 2: tariffs. With an unhealthy amount of traveling abroad to do, my main cost item on phone bills regularly is data roaming, so this is where my sensitivity lies (because of the eye-watering bills I regularly get, I am not bothered about 600 or 900 UK any-network minutes costing £5 more or less), and it became clear quickly: Orange, T-Mobile and 3 are out of the race (their charges are even higher than O2’s). Vodafone looks good (about 1/3 of O2’s rates) but O2 claims to still have their Blackberry tariff for international data roaming (although I struggled to find it on their website). Now, THAT would bring my bill down by a cool £150-200 a month or so. Enter Blackberry. The Bold (which I dearly loved when I had it) or the Torch (which gets decent but still very mixed reviews)? And then: O2 again? In spite of my anger with them?

And then I started to compromise: anything exclusive to Orange, T-Mobile or 3 was out of the question (because data roaming is pretty much a killer for me), which boils it down to Blackberry and O2 or any of the others on Vodafone (which would mean that I couldn’t get what started being my favourite, the Samsung Omnia 7). Hang on: I compromise over some shoddy pounds? Is the handset then not so all important as one might have believed when reading all those blogs, news blitzes and tech publications over the last months?

And, yes, I think it is true to say that – at least in instances where there are certain usage requirements (in my case data roaming), the package is what rules. This is perhaps then the wedge that the carriers –  scrambling for meaning in this new app store world – could use to pry that dump pipe/smart phone dichotomy open. How’s that for an idea?

So, good folks at the carriers, listen up: do it (oh, Vodafone, and get me that Omnia 7, will you? 😉 ).

How Apple Got it All Wrong

Sluggishly reacting applications, latency in almost everything you do, crashes, blank screens, long lag to pick up networks, buggy settings. Do you remember any of this? Sounds like some old-fashioned feature phone that was somewhat overloaded by its ambitious maker, doesn’t it? But, alas, no, it is not. This is the user experience with a one-year-old iPhone 3G, 16GB since 24 June 2010. Do you recognise the date? Then luck will have it that you have experienced the same: the grandly titled “iOS4” update that was being pushed down your throat (or rather iTunes) to your iPhone 3G.

Apple has been hailed for poking everyone else making handsets in the eye when it came out with the iPhone: here is a newbie that got it all right and venerable industry leaders found themselves with cartons full of ostrich egg on their faces: here was someone who got it all right: combining great build quality, maybe only OK-ish specs and unsurpassed UI with a vertically integrated publishing and distribution system that made for a leap in usage of mobile devices. It was a bad slap for the Nokias etc of this world and a revelation for millions of users (even if they were not Apple fanboys).

Software and hardware need to blend well

And then it came back to bite them! I am not a techie but iOS4 on the iPhone 3G feels like someone put a little too much luggage onto too frail a porter: the things creaks and aches at every corner. Gone are the days where one could switch from one app to another in seconds, where the iPhone – in good Apple style – did what you wanted it to do without much ado but breathtaking efficiency and speed. Now, it is clunky and, well, very old-fashioned. It could of course all have been avoided: just don’t push iOS4 to the iPhone 3G (or older models). No one would have cried, you should think: if the hardware cannot handle it, it cannot handle it. Users understand such things one should think. Keep iOS4 to the iPhone 4 (even the numbers match, doh!).

Allowing iOS4 to be pushed to the iPhone 3G was one horrendous mistake!

So is this the latest marketing trick of Apple? Go and spend another £600 to buy a new one, you say? This would be utter and incredible cynicism on a scale that would put Apple right on top of the current bad-boy scale! After all, I am not talking about an old, well-worn something-or-other device; I am talking about something that was only a year ago (which is short in terms of device replacement even in the mobile space) for a considerable amount of money!

However, I think that is not it. My suspicion is rather more frightening. It very much feels like Apple starting to overextend itself and learn how complex and fragile it is to deal in the mobile space. Pushing iOS4 to devices that obviously (not only under some special and hard to find circumstances) cannot cope with it is just shoddy. Every game or app developer in the market for more than 2 years would have caught this in QA. Does Apple not have QA? Or not anymore? Or at least not enough? It might happen to you when you try too much too quickly. Apple’s passion (or paranoia?) that drives it to try and do everything itself appears to haunt it now: I mean, QA is really simple. You don’t need cohorts of phDs in elementary physics to do this. It doesn’t take you 3 years to build it up. And – last but not least – Apple appeared to being very much on top of this in the past. So what happened?

A great showcase on the importance of User Experience

I have been throwing this into the faces of Nokia lovers who never fail to point out how technically superior Nokia’s hardware is: users do not give a toss about hardware specs. They care for the overall user experience. The unhappy marriage of the 3G with iOS4 shows what this does when it goes wrong: all the fun of using an iPhone is gone. What good is it when my phone lets me down every 10 minutes? What fun if my e-mail doesn’t open for 20 seconds? How exciting if applications appear to be frozen only to open just seconds after I pressed the home button (that will kill them just in time after I saw that it did, at the end, react)? Utter frustration. Rotten user experience. Complete fail.

Apple shows us, hence, accidentally how important the overall user experience is, and this may well be my final example on this: a simple (well, maybe not so simple) piece of software turns the most coveted consumer device of the day into a somewhat lame brick! However, it also shows how incredibly important it is to match the hardware (and network environment) to what the overall product (here: iOS4) promises to deliver (non-Apple case in hand would be video-calling on the Nokia N70 back in 2005: there was just no way this would work in practice; the experience was just too horrendous).

So, dear Apple, back to the drawing board. And if I may make a humble suggestion: just push the last pre-iOS4 version back to the older devices tomorrow! First thing! Promise! Please!

To all the others: this is a great opportunity! Catch up! Double your efforts! But don’t forget that the coolest frigging hardware (12 MP cameras anyone) is useless if the UX is not matching it either!

App Store Fragmentation: Vodafone & Android

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!

People-centric Design Rules!

Apple’s iPhone is only a marketing fad for vain urbanites. True purists go for Android. Those who see the light in volume go for Nokia or Samsung.

All this are points often heard when one dives into the deeper echolons of most mobile tech blog or forum. Engineers throw up their hands because those “American-centric media types” “don’t get it” and only wave their flag for whatever Steve Jobs, turtle neck and all may put up onto the big screens of his church.

I am not American and I am not a media type. And I don’t wear turtle necks (well, not since c. 1989 at least). And yet, I do prefer my iPhone (3G) over my Nexus One. And this despite obvious advantages of the Nexus: better screen, quicker, haptic feedback (yes, Mr Jobs, I do like that), the concept of open source, etc, etc. So why do I stick to the iPhone? Fanboy? Marketing fad? Vain urbanite?

Here’s why: I have been trying to set up my Nexus so it will do what my iPhone does, and I am not talking of playing a fancy game or running some other app that is not (yet) available on Android. I am talking about the two key things I need a phone for (41-year-old non-techie I am), and that is phone calls and e-mail; calendar (with sync) is important, too. For the former I need my address book, and I need it to sync properly. For the latter, I need my (admittedly too many) e-mail accounts set up on my device and syncing properly. As to calendar, wait for it below. Alas, two very different experiences:

  • On the iPhone, you do the following: 1) plug the phone into your computer, 2) answer “yes, please” when iTunes asks you if it should sync contacts and e-mail addresses, 3) get yourself a cup of coffee, 4) walk off.
  • On the Nexus, you’re OK (-ish) if your life evolves around Google. With a Gmail account and associated contacts (and/or calendars), you’re sort of OK. It does all that. Now – shock, horror – I do not actually send all my mail from Gmail and my contacts are mainly dealt with in my address book (take Outlook or whatever you want if you’re a Windows user). And I use iCal and not Google Calendar. And so it starts: there is no desktop application that would help me do this. On a Mac, the phone is not even recognised when you plug it in (and that is a rare thing on a Mac; is this another piece of Apple vs. Google? I don’t know but I doubt it). So you are finding yourself setting everything up by hand! Entering the POP3 and SMTP (or IMAP) server addresses, user names, passwords, etc, etc for seven e-mail accounts is no fun. And (remember I am not a techie) invariably leads to some box checked wrongly here or a typo in a password there and, kawoom, nothing works. I can set up a Google Calendar/iCal sync BUT that will only sync the specific Google Calendar bit between the two, and not any of my other (work, home) calendars. I can sync my address book with Google, so that works. The whole procedure took me the better part of 45 minutes, including lots of corrections and swearing and led to me abandoning a half-configured beauty of an Android phone. Great result.

So why is that?

My answer is: because they design it with engineer-centric design. And that is wrong! Why? Well, because most people are not engineers! An engineer thinks something along the following: I am Google and we love the cloud. Therefore, I will design everything so that it will adhere to that principle and will – in a purist kind of way – design everything in a way that you can beautifully and seamlessly set everything up – if and as long as you use all the wonderful Google services we have. And if you don’t get that, you’re not worthy.

The same works with Nokia: we’re Nokia and we have the best hardware, the best distribution and an incredibly good and powerful plethora of services around it (we did spend time, resource and money after all to become mighty competitors in maps [Navteq], music [Comes with Music], apps [Ovi – and the many iterations before it], etc). I will therefore design everything in a way that I can let this hardware shine as best I can; I mean: we had video calls since 2005, for elk’s sake! And if you are too dumb to configure everything in a proper way and cannot find the destination to where your downloads were stored, you’re not worthy.

Apple looks at things a little differently (and it is not only for the better although, for most people, it is): they provide a tool that brings everything I need over to my phone just like that. Job done. Easy! They will look at whatever tools they need for this. And if it means extending iTunes (which, yes, I know, they had already) to accommodate syncing data other than music and video to something other than a computer, than so be it. In that, they follow their own philosophy as slavishly as the other guys do but they do design it from a people-centric rather than an engineer-centric point of view. And that is why it works so well for people that are not (also) engineers.

They key point is this: Apple does not try (or at least not in your face) to change what people do. If I want to run my e-mail off 5 different domains, then so be it. If I prefer my contacts to sit on my disk rather than in the cloud, that’s fine. They’ll give me tools to facilitate doing what I do already and don’t lecture me on what I have to do to make it work. That this brings about subtle changes in user behaviour is fine: if you convince me gradually that things work better one way rather than another, I might be converted. But to tell me “my way or the highway” does not work! Ever!

The downside is Apple’s control mania, which blocks things (sometimes fairly questionably) because they are (or only might) be out of their control. And this is where Google, Nokia and all the others could score: try to combine things! If you would look at how Apple does things, and then – at the very end – you provide a door (doesn’t have to be a trap door, can be a flashy entry portal) to the innards and machine room of your device, so you can show off whatever you want and open the marvels of technology to those who can and want to handle it – so they can turn their super-smartphone into an uber-super-smartphone. But do leave normal people alone.

In the post-iPhone era, things have changed already (a little): you now get hidden installers (that do not ask you 100 questions on where you want to do what and where and under what penalties and with which risks), you get better interfaces, etc. BUT the default is still engineer-centric and not people-centric. Improve this, and the iPhone killer can be yours!

Image credit: http://www.ntamco.com/main/images/stories/design-is-a-behaviour.jpg

Smartphone Market Shares Q1/2010

Gartner published the latest smartphone numbers for Q1/2010 (or so I read), and it is testament to the continuing rise of this segment: sales increased by nearly 50% year-on-year (and do remember that there was this recession-thing last year). Total sales were 54.3m units in the first quarter of this year. Not too shabby!

On the OS side, the rising stars are Android (9.6% global market share from 1.6% a year ago), which is now bigger then Windows Mobile (and it took it only a year!) and iPhone (15.4% vs 10.5% in Q1/2009). The silverback gorilla still is Symbian which dropped to 44.3% from 48.8%. Blackberry is also down (albeit only slightly: 19.4% from 20.6%).

Here’s a table:

Has Android Got Game?

According to a recent report, Android has zoomed past Apple in US smartphone OS share, taking the #2 spot with 28% behind Blackberry (36%) but now ahead of Apple iPhone OS with 21% (and, yes, I know that Apple somewhat lamely queried the accuracy of this). Be it as it is, Android is growing (and we all knew that, did we not?). According to Google’s CEO, Eric Schmidt, the company now sees 65,000 new phones being activated per day; this equates to a run rate of 23.7m for the year.

This is good news for handset manufacturers like HTC, Motorola and Samsung (all of who are shipping successful Android devices) as well as Google (which is fairly tightly embedded in the whole thing) but does it also reflect on the wider ecosystem of developers producing applications and services for the platform?

The main points that are usually mentioned are:

  • Low overall numbers: Digital Chocolate’s CEO Trip Hawkins moaned the company sold less than 5,000 units of its hit game “Tower Bloxx” on Android Market, which was indicative for the lack of uptake. If that is so overall, may remain to be seen. I beg to take into a account that Android as a platform is fairly new and the overall install base is still smaller than its competitors.
  • High price-sensitivity: according to an AdMob survey in January 2010, 12.6% of Android apps are paid vs. 20.4% on iPhone OS; the same survey revealed however that the average monthly spend was actually similar on Android ($8.36) and iPhone ($8.18) though higher on iPod Touch, which runs the iPhone OS, too ($11.39).
  • Return policy: Google allows users to return an app for a full refund within 24 hours of purchase. This is seen particularly onerous for games (a lot of which can be played start to finish inside that time frame).
  • Discovery: developers feel Google fell well short of Apple on this one. There is no possibility to discover apps from outside a mobile device (i.e. no iTunes) and Google has not really done anything in terms of marketing either (very much unlike Apple).
  • Ease of purchase: I would like to add ease of use of the buying process. Registration with Google Checkout is a far, far cry from setting up an iTunes account. This will very likely change very, very soon as Google will add carrier-billing now that it decided to move distribution of its branded Google Nexus One from D2C web-only distribution to the usual carrier model.

So what about it? Let us not forget how young Android is – even compared to the adolescent iPhone. The platform launched from an install-base of zero some 18 months ago, with the HTC G1 being the only device out there – and available through a single US carrier, T-Mobile (with a market share around 12%). Whilst I do not want to take anything away from Apple’s superior accomplishments with the iPhone, the growth of Android is not too shabby either! And with a plethora of manufacturers deploying Android-based handsets now (cf. the growth numbers above), Android is likely to be powering into the fore even more (irrespective of whether or not the above stats on it overtaking iPhone OS in the US already being true).

Price-sensitivity is not actually as bad as people think: the aforementioned AdMob survey shows nigh identical average spending patterns. Personal impressions may again be hampered with by early experiences: be reminded that, initially, there were only free apps out there. They will surely still be hanging around, but will they also for much longer?

Apple has always been extremely scrupulous on approval of applications on its platform. And whilst this may now be held against it every now and then (e.g. in the case of nipples or Pulitzer-price-winning political cartoons), it has helped it to uphold a fairly high standard of quality, which Android was lacking (initially) and which even led to “crap-filter” apps. One can however safely assume that this will change once the market size improves: Apple’s margins might be superior to everyone else in the world but that does not mean that the margins game developers can achieve with it are the same. With Android OS primed to expand at a much faster pace, the numbers will clearly speak for it, and – I would posit – that will bring more and more quality to the store, with the fads sinking fast.

Also, do not forget the big brands: they do not necessarily care for a small share of the audience only. Whilst Android was fledgling and just starting up, they may have held back but, ultimately, they are about reach, and Android is certainly bound to deliver that. I would therefore suggest that we will be seeing an influx of large brands (gaming and otherwise) onto the Android platform very soon, and this will also help user orientation as to what to go for and what not.

The discovery of apps will also be helped by the more open nature of Android. There have been a number of announcement for curated stores by carriers (e.g. Vodafone, Orange, Verizon Wireless, Sprint, etc.), and these will certainly not be allowing a free for all! Besides that, the app store model does per se pose some challenges on developers: the more successful a platform (and/or store) is, the harder it is to be discovered. One might need to look for other solutions in that respect…

The billing side of things is bound to improve, too. With carrier-billing around the corner (cf. supra), this will get easier and better. And also easier and better than it is on the iPhone: charges will simply appear on your carrier bill (smart pipe anyone?). Besides that, the business models for games are undergoing significant changes anyhow: Freemium takes centre-stage, and so it should: the model allows people to try a game out and be charged for it only when they know that a) they like it, b) what they are being charged for (e.g. that coveted sword, a couple of precious lives, or that cool background theme).

Remains the return policy. I have been raising this with Google, and it must be pointed out that similar things exist on the iPhone (they’re just “better” hidden). So besides the obvious (Google’s good intentions came back to haunt them), it is also time to think of new business models (cf. Freemium). It is not something constrained to Android: transparency requires you to deliver value. If you do, there are good and transparent means to monetize that value; and users will follow.

So, yes, there is game in Android. If you don’t believe it now, just wait for it! 😉

Page 3 of 15

Powered by WordPress & Theme by Anders Norén