SYS-CON MEDIA Authors: Chris Pollach, Kevin Remde, Peter Silva

Related Topics: Wireless, Java, Adobe Flex, Symbian, SYS-CON MEDIA, iPhone

Wireless: Article

Java ME Is Dead, Long Live Java ME

Java ME is going to keep on chugging, maybe even seeing a rebirth
By Barbara Ballard
Article Rating:
February 15, 2008 08:15 AM EST
Reads:
 13,859

In this "year of the mobile web" where pundits everywhere are talking about how "the web is the platform" ....

In this time of "let's get a good enough browser and then mobile will take off" ...

In this time of "Java ME is dead" ...

4 of our 6 first quarter projects have major components in Java ME. These are new applications, from companies who understand the porting issues and the complexities.

Why are they using Java ME?

  • Because they need to store some of their application logic and/or data locally
  • Because the app or data needs to be available without the network
  • Because the application would be dreadfully slow as a web app
  • Because they are creating a push messaging client that needs more rich interaction than simple SMS (and better interoperability than MMS)

This quarter is not particularly different from other quarters: we get far more work designing applications than designing web sites.

Java has lots and lots of problems. You know what they are. I think they are fixable, and the good news is that we can use the platform now. So many of the browser and widget platform possibilities keep being "just around the corner" and the opportunity is now.

Java ME is going to keep on chugging, maybe even seeing a rebirth, for quite a while yet. SavaJe doesn't spell the death of Java ME either.

Published February 15, 2008 – Reads 13,859
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.

More Stories By Barbara Ballard

Barbara Ballard is President and Founder of Little Springs Design. She's a wireless industry expert in product and user experience design and a developer of mobile user interface patterns. As an evangelist for improved mobile product development process, incorporating device proliferation and user experience, her experience includes phone user interfaces, Java ME, uiOne, mobile web, mobile payments, widgets, NFC, and location services. She is the author of 'Designing the Mobile User Experience' (Wiley 2007) and blogs actively at www.littlespringsdesign.com.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Most Recent Comments
Ali Kianzadeh 03/10/08 04:51:05 PM EDT

The problem with j2me is diffrent implemntaion by vendors and restriction on accessing to the api.
For example if you want to make a phone call useing j2me. user have to answer to phone warning 4 to 5 times. And some phone don't allow you to access thier phone book if your application doesn't have certification, of cource you have to buy a 500$ per year licnece from Verisign to solve this problem.
This is too much, sorry!