James Rosewell writes:
Anyone involved in the mobile industry will have hardly failed to notice the hype surrounding mobile application stores - led by Apple. Application stores provide a really simple way for consumers to install applications on their mobile phones. They’re so simple I heard Iain Graham had used one the other week.
However they don’t solve the fundamental problem of handset compatibility. Anyone wishing to develop a native application for mobile phones needs to consider the handsets they wish to target and in which order. There’s Apple, Web OS, Nokia S40/S60, Windows, Android to name but five. For years, providers of consumer applications have only needed to worry about Microsoft and Apple with many choosing to ignore Apple. Unless today's application creator has deep pockets and makes many versions they’ll need to make some tough choices about where to start.
However the big drawback of web browsers is their insistence in having a constant connection to the internet, something that is not always possible in the vague world of mobile data connections.
Solving this problem represents an opportunity for mobile browser manufacturers. Allowing their web browser to operate partially independent of the internet would allow application creators to build their solutions confident they’ll work on many handsets. This approach won’t work for all application types, those that need to control the handset or use specific features of a phone, but will help many that provide discrete services such as games, social networking and content. Google have made some big advances in this area with their Google Gears and now Wave technology.
In summary, before reaching for an Apple iPhone Developer to create your latest application, consider the alternatives. There’s no harm in creating a “lowest common denominator” for the web browser to quickly and cheaply get started before expanding to other platforms once you know which handsets are actually being used.