Conclusions

In this article I’ve explained the good, bad, and just plain ugly features of Java ME.

First, we saw that "the good” included:

• Core features for interacting with devices
• Easy to develop, and existing Java skills can be leveraged
• Wide ranging availability
• Package portability across different devices
• Deployment is trivial
• Tools are abundant and of an excellent caliber

Next, I explained how "the bad” concerned problems of API versioning and fragmentation, and the associated difficulties of configuring mobile phones for internet access. Finally, we saw how "the ugly” usually concerned the runtime environment (devices and carriers) and centered on security certificates, locked-out functionality and Java verification.

In my opinion the “good” of Java ME far outweighs both the bad and the ugly. There are alternatives to Java ME, but if you want to deliver robust applications to the widest possible mobile phone audience, it’s the best technology to go with. The Java ME community is active and exciting. Furthermore, it’s a technology that is both a de-facto standard and rewarding to work with.

Java ME – a little bit of bad, a touch of ugly, but mostly good.