Barbara on “Java ME is dead. Long live Java ME.” (and indirectly on the future of mobile apps.)
Barbara writes “Java ME is dead. Long live Java ME.“, about how the word out there is about mobile web, but what her customers are ordering are Java mobile applications…
Why local applications? Barbara explains it well on her blog post. Indirectly, this same explanation also shows that once the browser-runtime of the “future” gets to provide access to offline behavior and local functionality to web-based applications on the handset, that a new era and kinds of mobile applications will take place.
Why Java ME (MIDP)? Because it is the most predominant mobile platform for local applications, today…
In any case, Barbara’s essay is about rich mobile applications today, and the future is wide-open.
ceo
1. Updated on February 19, 2008: added the “indirect and future mobile apps” pieces.
Hi,
I am new in J2ME development. I am developing one application which launches when a perticular sms comes. If you have some sample program or any solution about it
please reply…
Yes, click at “Mobile Java” on the top of this page, and look under the messaging section.
Whilst Chief Architect at Motorola spending all day long working with hundreds of operators and mobile app vendors, I hardly ever saw a service/product that used the browser as the primary UI. The reason is simple – the richness of experience isn’t there. It needn’t be this way and I was working hard to change it with various browser innovations. Offline browsing is only one of the tricks. The integration of real-time comms and other mobility attributes, like the address book, into the browser model needs solving. Don’t forget that for this to work on the same grand scale as the global GSM standard, this needs open and interoperable specs, not Google Gears.