As some of you may already know, MIDP 3.0 is going public. While smartphones have taken their own route with respect to the runtime environment, I expect feature phones to adopt MIDP 3.0; to be seen is the adoption by device manufacturers. But that said, FYI, the list of new features is very good (and many of my wishes were satisfied); to mention a few:

  • Backgrounds MIDlets (i.e. services) and auto-launched MIDlets
  • Enhanced storage management w/ support for record tagging/labels and support for external, secure storage
  • Access to unique device IDs such as UUIDs and IMEI (to better manage deployment instances)
  • New UI functionality such as support for splash, idle screen and screenisavers, text input into Canvas elements, tables, tabbed panes, splash screen, scalable images and animated GIF, menus and form layouts, other
  • Support for libraries — now you can decouple common infrastructure components from the app and into libraries that can be shared across apps
  • MIDlet concurrency and inter-MIDlet communication
  • Support for application and system eventing (from the system events such as low-battery, etc)
  • HTTP support for PUT and DELETE in support for REST-like web services
  • IPv6 URLs, file selectors, and other
  • Migration path to CDC
  • A number of clarifications that I hope helps reduce ambiguities that previously permitted inconsistent implementations
  • …and other

Related to this see JSR 271: Mobile Information Device Profile 3 – Proposed Final Draft.

ceo

Disclaimer: I was a member of the expert group that defined MIDP 3.0, so I am obviously a bit biased to see this succeed and at the same time very pleased with the set of features that made it to the next generation of the Mobile Information Device Profile (Java ME).

Tagged on:             

3 thoughts on “What is new in MIDP 3.0 – a quick summary

  • June 4, 2009 at 2:00 pm
    Permalink

    When will be?
    Motorola is out?
    JBlen will build RI and TCK?
    Whats going on?

  • June 4, 2009 at 4:31 pm
    Permalink

    Miko,

    Moto has completely committed to Android. It seems Moto is out or on the way out of the JCP, based on the recent announcements that Moto is giving away / transferring both the Bluetooth API and MIDP 2.x. Once MIDP3 spec is completed I will assume it also will go to Aplix (or other); i.e. note that the JCP doesn’t allow the transfer of a spec that hasn’t been completed.

    Yes, probably Aplix will do the RI and TCKs.

    ceo

  • Pingback: McGuire’s Law » Blog Archive » Observations: Applications - June 6, 2009

Comments are closed.