Tag: firemint

Conference: Games For Brands

A fairly wonderful conference will open its doors on 27 October in London, UK, namely Games for Brands, an event where we will do just that: investigate if and to what extent games may work for brands. Just speak to Barclaycard (their Waterslide Extreme game [done by Fishlabs] did more than 14m downloads on iOS) or Volkswagen (multiple games by Fishlabs [again]) for the Polo and others and a special VW Golf GTI edition of Real Racing by the recently acquired Firemint).

The event features a fairly cool line-up, too, including speakers from:

  • Rovio (they of Angry Birds fame)
  • Channel 4
  • Google
  • PlayGen
  • BBC
  • EMI
  • King.com
  • LoveFilm.com
  • Tate
  • Wellcome Trust (yes, they’re the Glaxo Wellcome guys)
  • Aegon
  • Matmi (they did games and apps for instance for Lily Allen, Gorillaz, United.com and Vimto – the seriously mixed-up fruit)
  • and, yes, I will be talking again, too (but when don’t I?)

I also have a goodie for the readers of this blog: four of you can get a very special discount and attend for £95.00 only. Tempted? Contact me (either via e-mail or Twitter or through the contact form here).

It’ll be a good one, so come along! 🙂

Mobile Games Publishing in 2011

I have been blogging way too little recently, so here’s – finally – a bigger one again.

What is a Publisher?

I have recently been asked more and more what the role of a publisher in mobile gaming is today. I mean, heck, there are now even websites proclaiming the (traditional) publishers’ death. On the other hand, venerable old and ruthless new ones are on a spending spree acquiring – seemingly – studios and smaller publishers by the dozen: In the past year or so, EA gobbled up Playfish, Chillingo and Firemint (and probably a few more I don’t know of). Zynga, even hungrier, absorbed XPD Media, Challenge Games, Conduit Labs, Dextrose, Bonfire Studios, Newtoy, Area/Code and Floodgate Entertainment. So what is right?

According to Wikipedia, a videogame publisher is (was?) someone who

publishes video games that they have either developed internally or have had developed by a […] developer. […] They usually finance the development […]. The large video game publishers also distribute the games they publish, while some smaller publishers instead hire distribution companies (or larger video game publishers) to distribute the games they publish.

Other functions usually performed by the publisher include deciding on and paying for any license that a game may utilize; paying for localization; layout, printing and possibly writing of the user manual; and the creation of graphic design elements such as the box design.

Pretty old-school stuff, you say? Erm, yes. Broken down from its beautifully naive pseudo-scientific language, we arrive at the following:

  1. Publishers pay for development (i.e. absorb the development risk). This could also be classed as project finance.
  2. Publishers pay for licenses, another case of project finance – unless of course they pretty much own (legally or, through long-term licensing relationships, factually) certain IP.
  3. Publishers provide a bit of gloss and lots of marketing around a title to help it on the way.
  4. Publishers – sometimes – distribute.

Is the Same in the Digital Realm?

Now, the Wikipedia definition pretty much focuses on traditional console and PC publishing, it seems (box art anyone?). And this is where the new world sharply departs. No box art, no Walmart or GameStop deals are required if digital distribution is in place. How difficult can it be then for the more modern, more evolved (?) world of digitally distributed and, perhaps (but only perhaps) even more specifically for mobile games?

Nos. 1 and 2 above are pretty much arbitrary parts of the puzzle: you can get money from many places (or not of course) but it is a financing game, and video games could be called a specific (because intrinsically hit-driven) asset class. That is to say, these are not unique attributes.

No. 3 is a combination of money, know-how, experience and network. The more complex the landscape the higher the value of a specialist in the field.

No. 4 is, well, arguably a much easier game when you can feed your distribution channels from your own desk – via the Internet. However, again, the more channels you need to serve, the more complex the landscape, the higher the value of someone "who knows".

Nos. 3 and 4 are – arguably – what made Chillingo (based in the same honest North-West English town as I am) what it is (or, prior to its acquisition by EA, was): Chillingo seems to have had a knack of identifying good or at least decent games and promote them effectively across digital channels. Alas, their biggest hit, Rovio’s Angry Birds had not much good to say about them in terms of support. And indeed, if one looks at what Rovio did with its hit title outside of the Chillingo relationship, one can argue about the value add it had received from its publisher. But then again, Angry Birds seems to have been one of a kind, and there are other titles Chillingo brought to reasonable success that may not have had the same success – be it for lack of a Mighty Eagle such as the fearless and tireless Peter Vesterbacka or otherwise.

Changed Metrics

Chillingo, alas, is not where it’s at, I think. The war is being fought over those (in)famous MAUs – or monthly active users. You see, if you can command those hundreds of millions and parade your own wares by them, the likelihood of your next game becoming a success rises: Digital connectivity solves the dilemma of publishing of old, and that was to attract the attention of the gamer (your customer!) for your next release.

In a box-product world, you had to shout again, and very loudly, in order to have your customer part with his hard-earnd monies for the benefit of your title rather than your competitors’. This is – arguably – why EA Sports sponsors UK football (scil. soccer) broadcasts: "please, God, let people not defect to Konami’s PES from my very own EA FIFA".

Now, Zynga laughs all the way to the bank on this: if you played FarmVille, you will not have come around of realizing that CityVille was out. And you would also get additional points if you also played Zynga Poker. The result? Well, check the top-10 games charts for Facebook games for yourself. Suffice to say that Zynga is – according to the second market – worth more than Electronic Arts… Why is that? Eyeballs, addressable users, dollars spent per acquired user. That the business model is a little different for console games than it is online, doesn’t really matter for the argument here: you can drastically reduce the user acquisition costs if you play it smartly, so no need to take in $39.99 per game in order to break even. $1 or $5 will be just fine, thank you very much.

The above is also the reason for the spending spree of the publishers, I would suggest: if you can buy eyeballs and get a studio with proven skills (just check out either of Newtoy or Firemint on the mobile end), and you can combine it with a mechanism to attract people to future releases, there is a much better chance you can recoup your investment on that future release (effectively de-risking nos. 1 and 2 from the above list).

And now for Mobile!?

Zynga, EA’s Playfish and Crowdstar have shown that you can tweak the fortunes your way if you smartly combine game releases, updates and promotions to work with each other. But how is it for mobile? Backflip Studios, which rose to fame with a simple but well-executed game ("Paper Toss"), claimed to have had racked up more than 2m daily active users and 50m total downloads, mostly driven through promotion of its own titles inside, well, its own titles. Did it have a publisher? No. Does it have a very smart CEO who solved nos. 1 and 2 above and knows how to play no. 3 itself? Yes. So what about no. 4, distribution? Well, on iOS, that is a non-issue: one distribution channel to bind them all. However, on Android, it still falls short of a copycat, "Toss It", who were there earlier, are as ingenious and still rule. And elsewhere? Not much.

But we don’t have to rely on one case alone, and one by a small – though incredibly smart – studio no less. Look at Zynga’s performance on mobile. It is mediocre at best. EA though? Not so bad. What do they do? Well, apply the good old publishing principles learned in the olden world.

And this is where the specific complexities of mobile come into play: mobile is fiendishly complex. On the OS side, there is iOS, Android (in an increasing number of iterations), Windows Phone 7 (with some added spice since the announcement of their Nokia partnership), Blackberry, Samsung’s bada, and then maybe BREW, perhaps still a little bit of Symbian and J2ME. But then there are also the still mighty gatekeepers, the mobile operators. And then you will see that users tend to want to have it their specific way, ideally localized. The plethora of channels thus created makes it tough on a developer to maneuver its way through…

There are tools that can aid progress (and, yes, our very own Scoreloop provides some of them) but it is important to recognize the complexity of it all. Reaching users and convincing them with compelling offers is key to success in any world. It is important to bear that in mind in mobile, too. And if you think you cannot walk it on your own, a publisher might just be the right partner for you.

Changed Weighting

Since 1. and 2. above might not be such a big thing anymore (mobile titles can be developed for less – and, yes, I know this does not necessarily apply to the likes of "Galaxy on Fire" or "Real Racing") and 3. might be manageable but 4. might (not: always is) still be a key reason to part with some share in order to reach the user, convince the user, be able to bill the user.

The New Mobile Apps: Head in the Cloud!?

Everyone with an iPhone will by now have seen and “played” them: the first generation of multi-player games where most of the computing is done in the cloud, relieving the handset from such labourious tasks. This, according to new report, will soon (well, by 2014) be the norm and will in fact erase downloadable apps (games and other) as we know them today.

The huge advantage of this approach is that it would largely do away with the fragmentation nightmare of the handset market: multiple operating systems, a plethora of screen sizes, all sorts of “interesting” middle-ware solution imposed by either carriers (Sprint anyone?) or OEM to “tweak” an OS to their specs, with the sole result of making things even more cumbersome for developers. It is one reason why the Apple iPhone ecosystem thrives as it does: one OS, one model, one distribution channel, worldwide deployment. If the heavy-lifting is done in the cloud rather than on the handset, one can – presumably – do away with less complex front-ends reducing the work necessary to port the app to various handsets (and, no, please do not choose iMob as the benchmark!). Coding for the cloud would resemble web development rather than today’s mass market application development with armies of post-production and QA engineers filling offices (and overall development costs).

Another, easily overlooked, advantage is battery life: the more (and more complex) processes are computed on the phone hardware, the more the device will consume of the precious and scarce juice; battery life is better with cloud computing!

The obvious downside of mobile cloud computing is a blue sky: no cloud, no app. In posh tech lingo: intermittent network availability, which is to say that the app won’t work if you have no coverage (so no displacing downloadable apps in Oklahoma or on the Scottish isles then…). The aforementioned report suggests HTML 5 and its more sophisticated caching options as the solutions but I am fairly skeptical in that respect: you will not bring about the “unprecedented” sophistication with a little bit of cached data.

Anyway, the more likely scenario is an abundance of network availability by 2014 anyway: by then, large parts of our computing will be done over the air and LTE (and further evolved) networks will surely rule good parts of the world.

So, will it work? The report points out iPhone apps for the likes of Amazon, eBay, etc and, yes, for such apps I am sure it will work: they basically extend a front-end of a web service to a mobile device. The “app” is basically a client that facilitates input and serves as a crutch for the smaller screen where it is necessary to optimise the available data so as not to overburden the little available space with non-core information.

Will it work for more complex apps, in particular games? It will depend. On what? On the type of game of course! How many online racing games do you know? I mean really good ones. None? Ah… Why is that? Because not even the abundance of bandwidth and computing power available today gets to a game experience even close to the 50+ frames per second that the top iPhone racing games can do today (check out Firemint’s Real Racing!). The experience on next-gen consoles is even more astonishing. Need for Speed: Under Cover on XBox 360 or PS3? Woah! All these games require very serious hardware acceleration to convert the high-end graphics into smooth, fast, flowing action. And broadband networks aren’t good enough for that. Period.

For other games, turn-based card games, board games, the Sims, or indeed full-blown MMO, this is another story. These games may require a lot of data but the speed is not as important for good gameplay. So for this group (which is arguably the larger one), cloud computing will probably be the way forward. The opportunity exists in particular (and will be largely sufficient) for all “serious” business applications: these feed for the most part off server-side data sets already and a light mobile client (or browser?) is all they need to provide serious productivity boosts to the corporate world.

So will these run in a (mobile-optimised) browser or via (lighter) downloadable front-end apps? Due to the constraints of the small screen, I believe it will remain very beneficial to the UI and playability to have a specific front-end (and core graphics and processes) on your handset because it will optimise the user experience on a mobile device. To keep this bit as generic and light will be key. Otherwise, it would be porting hell all over again.

But we’ll get there! Just watch out!

Powered by WordPress & Theme by Anders Norén