.gif)
J2ME or Java Micro Edition (also known as JavaME) can be said to be phenomenally successful. It has been shipped across major manufacturers’ devices (100+million I think). It has enjoyed popularity for almost 3 years now, in existence for around 5 years.
But J2ME doesn’t exactly reflect the vision of the Java Platform in the true sense .As someone said, Write once, compile once, run anywhere is anything but a bad joke in J2ME. And for those who tried writing J2ME applications, tool support, productivity and user interfaces that get generated isn’t exactly even close to exciting. Most rich mobile applications are built on custom UI’s that are built specifically for applications. Mophun & BREW 3D apps are overshadowing J2ME’s own JSR 184 API for Mobile 3D graphics.
Once an application is written, it has to be ported onto various devices, tested, sometimes but not always certified to be published, making a the product development lifecycle a long process. This isn’t exactly the time to market of what most media and business imagine it to be.
Adobe recently released Flash 2.0 a follow up to Flash Lite1.1. Flash Lite1.1 was good but had limited features, where as Flash 2.0 seems to be playing catch-up with J2ME, but still got a long way to go. In features, functionality and it seems to be ahead of J2ME in rich mobile applications development.
Also to note, one of the biggest advantages will be the fact that Flash Lite being proprietary technology is a subject of frequent reviews, upgrades and will consequently add more features to it in comparison to J2ME, whose’ development has slowed down and the features aren’t exactly moving in pace with the industry. With Sun at helm, many within the industry feel that J2ME & Sun are loosing or lack leadership and will soon loose its dominant position in the mobile solutions market.
The PC based Flash player, has massive uptake with presence on 98% + of all computers connected to the Internet, across major OS’es & Operating systems.
Taking that trend down to mobile phones isn’t exactly going to be easy. These are the challenges
· Matching features with J2ME (this will increase the memory footprint of the player)
· Larger device compatibility - is still the biggest issue.
· Lack of great click and drag GUI environment for designing good applications (like the new Adobe Flex for RIA) - This should also be available for Flash Lite which can accelerate application development and increase acceptance in developer community.
If Adobe can address these issues, it will can see an upward trend in the adoption of Flash Lite and this might just overshadow J2ME at least in infotainment segment, which - which also happens to be the largest.
Asif Ali
Actually, you're quite wrong.
1. There are more than 1 billion devices that have MIDP (1 or 2) in the field right now.
2. Flashlite has not even overshadowed Java in Japan and Korea, where Flashlite has been entrenched for awhile. Meanwhile, Java ME has become near-ubiquitous everywhere else and almost anything of note is done in Java ME. For example, Google Maps Mobile or Opera Mini (the latter having had several millions downloads in just a couple months).
3. Incompatibilities in flashlite is already showing up even though it's deployed in only a handful of devices. The problem is that this is NOT the desktop browser market, where only 1-2 environments are in play.
4. Microsoft developers are continuing to embrace Java ME. I have met quite a number of Windows developers who are entering the mobile market via Java ME. This is a huge developer base that never got into applets in browsers.
5. SVG APIs have moved into Java ME (take a look at the newest Java Wireless Toolkit), which means developers can now use vector graphics, in addition to 2D and 3D graphics in java.
6. The mobile environment is what java was first produced for...the diversity of devices, the fragmentation betweebn different manufactuerrs...this was what java was made to play. The situation is entireley different than in the browser arena in the late 1990s, when Sun deliberately ignored the browser market to focu on where the money is - servers on the server-side.
7. Flashlite developers are complaining already because in order for a user to even see their work the user usually has to PAY for the flashlite download and install into phone.