Three Reasons Why Your Next Java ME Mobile Application Should Include JavaFX Mobile
By Christine Dorffi on Feb 06, 2009
Let's assume that you're in the middle of your development cycle, and you realize that your mobile application needs to perform some very important but non-GUI-related operations such as:
- Discover a local Bluetooth device in the vicinity
- Communicate with a SIP registrar or proxy
- Determine your geo-location via a GPS device
So now what do you do? You want to write your killer-app using great declarative syntax of JavaFX, but you also realize that the Java standard specifications for Bluetooth wireless technology (JSR-82), SIP communication (JSR-180), and location-based application development (JSR-179) and are available as Java ME APIs.
Fortunately, the JavaFX runtime is completely dependent upon (and compatible with) the Java virtual machine (JVM). Simply stated, it means the following:
- Your JavaFX Mobile application has no restrictions on calling any class bundled in the JAR or any JSR API library that's present on the handset.
- Your JavaFX Desktop application will work seamlessly upon any deployment platform that has the current version of the JRE:
- For Windows machines, this will be Java 6, update 11 (or later)
- For Mac OS X machines, this will be Java 5, update 13 (or later)
Independent of the operating system, your JavaFX Desktop application will also be able to call any class that's bundled in the JAR package for your desktop application. Note: On the Windows desktop, JavaFX runs on Java 5 and it degrades gracefully (for example, the Drag2Install feature does not work) — that is, it does not break your application.