Avoid the 9 Common Flaws of Unportable Mobile Java Apps
Portability is a huge concern, especially in wireless development, but developers who fail to incorporate portability concerns into their app design from the outset are doomed to repeat the same dumb mistakes over and over. Find out the nine most common design flaws in J2ME applications and get your apps out of the quicksand and into the air.
by Simon Keogh
March 9, 2004
ith an estimated 100 million Java-enabled handsets on the market todaya number projected to grow to 1 billion by 2006it's clear that the opportunity for wireless developers is enormous. However, since there are more than 200 different Java-enabled mobile handsets and an international market requiring multiple language support and mobile operator specific customizations, developers are finding the time commitment and total cost of deploying applications to be a huge hurdle to overcomeall but eliminating the benefits of having such a large potential market for their applications in the first place.
One of the issues that causes such a sinkhole for wireless application development is portability. With over 200 different types of devices, writing one program that works on each one seems a daunting task indeed. A common mistake is for developers to write an application for one device, and afterwards to attempt to tailor the original code to each device as needed.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!