LinkedIn only a little bit mobile...

And here's a somewhat disappointing mobile debut: business network superstars LinkedIn announced the launch of their (beta) mobile "application". However, the app is a mere WAP site with, alas, all the downsides of that: latency, onerous navigation and the whole info from the website only toned down in graphical appeal.

Now, whilst I am big fan of LinkedIn, this is sub-par. Have a look at what Facebook did for the Blackberry: a small downloadable app (yes, I know, it's painful but probably for the time being the only way to enhance the user experience on mobile), information reduced to the key things one might want when accessing this from a mobile device and then the option (sic!) to access the full monty via WAP. The one piece of information I couldn't access on the LinkedIn WAP site was the contact info. Hmm. Wouldn't that arguably one of the key pieces of information I would want to have when I'm on the road ("well, I'm in London. Why don't I drop John Doe a line. Don't have him in my address book as we haven't spoken in a while but we're still 'linkedIn'. Doesn't work. Doh!").

With all due respect, dear LinkedIn friends, you've got work to do!

New Phone flies with Nintendo Games

Little-known handset manufacturer Fly has announced its new MC100 handset which features both Java MIDP2.0 / CLDC1.1. as well as - and that is the cracker - support for Nintendo NES, SNES, Gameboy and Gameboy Colour game formats. There are some neat dedicated gaming buttons and a rather useful-looking "D-pad".

The handset is powered by a Yamaha chip and also has an MP3-player. Whilst Fly seems to be mainly active in Eastern Europe (that's at least the only region where they have service centres), the handset is retails at the not too shabby price of $270 a pop; where it goes on sale, remains a miracle: the currency would suggest the US but perhaps it is Russia after all?

Also, the issue if these games are legit remains a bit in the dark. Fly only says that "games (nes/smc/gb/gbc) can be freely downloaded from the Internet and set up in your Fly MC100".
This would suggest that Nintendo is not involved in this, and there is indeed no active (or passive for that matter) endorsement from Nintendo anywhere to be seen. So this would almost certainly exclude any "proper" Nintendo games from being included (unless Fly wants to risk a visit from Nintendo's legal eagles). All a bit odd really but, boy, would it be cool were it legit...

How many handsets does a game need to support?

GDC Mobile co-founder and, I am honoured to say, my good friend Robert Tercek, came out with all guns blazing against the carriers' demand for maximum handset coverage for mobile games that they allow to publish through their deck. Tercek called it a "lie" that operators basically insinuate that a game will run equally well on every handset, and he called mobile games publishers hypocrites as they moaned and whined about it but still play ball... Well, what else are they to do? Stop publishing games?

Since I still work in this industry, I would not perhaps put it that harshly as Rob did but the question is indeed if the network operators' rationale ("we need to provide for the best possible user experience for every one of our users") stands true when it comes to this. After all: if you offer a full music track for download, your phone needs to be able to support MP3; an old battered brick that only plays monophonic ringtones won't do. To put it into slightly starker contrast still: it would be like an ISP would prevent a web publisher from putting a site live only because there are a lot of PCs out there that do not have the right software support. Or if the Germans would not allow any car to be imported into Germany unless its engine software was geared to allowing a top speed of min 200 mph because otherwise the user could be disappointed with the driving experience on the Autobahn.

Is the assumption that someone who has an old T610 would actually expect to be able to play a modern-day 3D racing game on his battered old handset really correct? If I drive a 10-year-old little Twingo, I know that I will not go 200 mph, Autobahn or not. And I will certainly not blame it on the operator of those roads.

If I want Vista Premium or Leopard, I need the machine to support it. And that is an informed decision I need to make. The operators' approach may have been understandable a few years ago: mobile was a very, very new platform and people had not actually got round to the idea that one could actually do more with one's mobile phone than making phone calls when away from a fixed-line phone. However, this has changed very quickly very much: even my 80-year-old neighbours now communicate via SMS with their kin. I believe it is safe to assume that the consumers of the year 2008 can very well distinguish between a low-end and a high-end phone and will actually appreciate the difference in performance without blaming their operator for a sub-par one when their phone happens to be a sub-par one. Time for change then, folks!

The constraints of having to support hundreds of handsets impacts the mobile games sector manifold: it makes it prohibitively expensive to develop and publish games with porting costs often being equal or even higher than the actual development. The effect is less innovation (how can you dare trying something new if you have to expend so much money before you even get it in front of a consumer?) but also less usage: it is often more of the same as developers try to minimize their cost by re-using engines (Gameloft has used the same basic side-scrolling engine for at least 20 games to date; highly polished and constantly evolving though, to be perfectly fair to them) and running risk-averse design philosophies where they try to stay as close to a proven hit as possible. This will however not drive consumers to get back for more.

I am however doubtful if operators will come to terms with this in the near term, and, let's face it, they are not the originators of this platform mess: isn't it more often the handset manufacturers that fiddle around with screen sizes that differ for more or less every device, that take great pride in running a gazillion different operating systems only to be slightly different to the other guy, that allocate soft keys rather randomly and occasionally swap the green and red call/end call keys from one side of the keypad to the other? Just imagine this last bit on a computer keyboard: is now on your left... try get going with that... Add to that the - yes, they're here still - operators and their specific demands for this, that and the other, and the fragmentation does indeed create an economic landscape that is very hard to navigate.

This is one to the OEMs and the operators alike: get down to business, compete on the strengths of your devices and services and not on some OS and other software tweaks where the upside to the consumer is, if distinguishable at all, minimal.

In the interim, it would indeed be upon the operators to start trusting the good judgment of their customers in the hardware they hold in their hands better and start dropping those old devices from their requirements that will manage to screw up even the best game.

The prosecution rests... ;-)