The Register on I-mode
October 27, 2005 | CommentsEl Reg on I-mode: "There's no denying that i-mode is great. I love the way it works, the selection of content, the pricing structure, the speed of access and the bundled push email. Unfortunately, the NEC N411i just feels a little behind the times in today's world of super stylish and fully featured mobiles. NEC should be congratulated for getting i-mode handsets out so quickly, but something tells me that we'll be seeing far better examples in the near future."
What can I say, other than +1
Cool Hunting: Flirtomatic
October 26, 2005 | CommentsFlirtomatic launches: "When it comes to anything mobile Europe has always been ahead of the U.S. For example, there have been mobile dating/mating applications over there for years. Flirtomatic, the latest player, launched yesterday and promises to be the new industry leader. It's very well designed, simple to use online or on your mobile phone and makes it easy to connect with people by introducing those who have similar interests."
And more here.
Flash Lite 2.0
October 25, 2005 | CommentsA preview of Flash Lite 2.0.
Work work work
October 24, 2005 | CommentsTwo work-related announcements:
- Flirtomatic has entered its public beta - go peek! We've been working on this service for almost a year now, there's a lot to it. I'm going to write more about this in the coming months.
- For local folks, we're running a competition for this years dScape event: "send words, pictures and video clips from your mobile phone that represent 'your Brighton' to 07811 407 760". "We're going to need a montage..."
Bad Long Tails
October 24, 2005 | CommentsJoel on Software - Monday, October 24, 2005: "This is where Google is actually hurt by the long tail world of millions of small sites."
This long tail thing - it's not all good, y'know. I was thinking about this the other day whilst chancing across some stats analysis we were running for a client.
We do a lot of porting work - taking mobile applications that we (or others) have written and converting them to work on new mobile phones. This is an inherent part of our business right now and whilst it's not as obviously rewarding as developing scratch, like it or not it's very necessary. There are porting frameworks which aim to help you get around this problem (in fact we wrote a rather snazzy one ourselves which we use internally) but they don't get away from the need to build and test your apps on real devices.
So which handsets do you port to? Well... there are a few biggies, a few which obviously stand out when you look at who's trying to use your service - and you should look at who the prospective audience is, up front, because different audiences will have tendencies towards ownership of different handsets. But there are a few up the top - Nokia Series 40, high-end Sony Ericssons, etc. - which are a no-brainer. But then look at the rest of them - the graph below shows the number of unsupported customers we've had for about 127 handsets which our service doesn't currently support (it has been explicitly ported to just over 40 more popular devices, of course!):
Oooh, it's a long tail - the top 19 out of 127 handsets (15% of them) which we don't currently support make up 50% of traffic. But look at the other 50% - to support these we'll incur incremental costs testing and development, so they become commercially unfeasible.
The morals of this tale?
- "Write once, run everywhere". Stare into the mirror and say it's name three times - it doesn't appear, it's just a fairytale.
- You need to look at your audience before you decide which devices to port to.
- Porting costs are a matter of economics: the more you spend, the wider your audience. But it may not be commercially viable for you to widen your audience beyond a certain point.