|
ExEn®
and J2ME are not so different
and ExEn® paves the way to a Java
language based standard.
The
main difference is that ExEn® has
been optimised for advanced game features.
Every
non-ExEn® phone manufacturer has
its own specific Gaming API (even on top of MIDP 1.0, the mobile
phone profile of J2ME) which induces
developers to produce specific code and intensive tests for every
manufacturer J2ME implementation.
Today, ExEn®
enables game inter-operability and deployment on operators networks,
whatever mobile phone brand. It allows a true multi-vendor phones
support.
This
simplifies development, broad deployment, and execution of mobile
games.
The
future MIDP 2.0 standard defines
a minimum set of game functions to be available in future phones.
Even with MIDP 2.0, advanced and
rich games will require new Game APIs that ExEn®
can provide.
Today,
consistent with its strategy of moving towards J2ME
standards, standard classes of ExEn®
Version 2 are set in conformity with MIDP/CLDC (Mobile Information
Device Profile / Connected Limited Device Configuration), which
addresses issues such as user interface, persistence storage, networking,
and application model.
The
ExEn® roadmap will feature new advanced
game capabilities and future MIDP
2.0 Game API compatibility.
|