Just finished two days at the Exhibition of the GSM Asia conference in Macau. After ten years or so of attending the major European event for the mobile industry, I thought I should checkout the Asian equivalent. I wrote a list of what I wanted to see before I got there and hoped to find ideas to help me to point my business Dialogue Communications further in the right direction.
So what did I find?
Application Companies
Java client on the handset.
Smart server either inside our outside the carrier's own IT environment.
Challenges to Client/Server application providers.
- Supporting multiple client platforms. In order to have a 'whole market offering' one must support the following environments: Symbian (various flavours for different Nokia series and Sony Ericsson), J2ME for the non-symbian phones from the far east (e.g. Samsung), Blackberry (increasing its market share at the expense of Nokia at the moment), iPhone (again increasing market share at the expense of Nokia), Windows Mobile (big in the states), Android (will be big and has Motorola support). Plus there are many carrier specific implementations of these environments. It is almost impossible to keep up with the demands of providing applications for all these handsets unless you are very well funded and/or can sell a huge number of applications. Therefore we have to consider how happy the carriers will be when the real world fact of patchy market coverage hits home. I may be very wrong about this. I do remember that in 1997 I thought ringtones wouldn't take off because they sounded rubbish and only worked on Nokia phones. So beware my advice!
- Servers that must be bought and hosted by carriers. Admittedly not all are in this camp, but several are. At the present time carriers are not too keen to find CAPEX so this is a bit of a challenge.
- Servers that must be populated with information from the carriers closely guarded databases. This is a bit of a challenge too, but if you want to do the best job of ad-serving then you want to get hold of this sort of thing.
So faced with these challenges I ask myself why these companies would not simplify things a little in order to help things along?
Simplifying the product set.
- The first thing I would do is to do away with the handset application. The iPhone webapps style of working is the way I'd go. Build a mobile web site which is very optimised to different handsets. In the case of the iPhone it is difficult to know which is a webapp and which is an iPhone app in some cases. The advantages of this is that it is easy to develop, deploy, maintain and delete. The disadvantage is that it needs mobile web access and may not look as good as an 'on device application'. But I can live with that.
- The second thing I would do is to remove the need for CAPEX and installation at the carriers premises. These are two things which will ensure there are no quick sales. So I'd either work with 3rd parties who are already well embedded with the carrier, or have a standalone operating model of the server side which can give the carrier 75% of the functionality out of the box.
- The third thing I'd do is to come up with some very flexible pricing models to suit the carriers view of the world. I won't go into too much of the detail here, but if you get it right you'll make sales and then make money.







