Blog

Thoughts on JavaFX for Android and iOS

So the big news is out: Oracle will provide the sources of their Android and iOS prototypes. While I agree this is great the announcement leaves me with many questions and doubts. What Richard is telling us is that they release their (prototype?) code for iOS/Android, not more not less. This means the community has to put a lot of effort to turn this into something one can use to write and package iOS and Android applications - at least this is how I read Richards announcement. Having the prototype code makes it easier to start because we can see how Oracle approached this but one has to have a lot of knowledge about the inners of the JavaFX' Glass and Prism code, OpenGL-ES and iOS/Android. Gaining this knowledge will take time and is probably not something one can do on evenings / weekends. Another uncertainty is "JavaSE Embedded for iOS/Android". What is it? Does it provide us AOT compilation? In case it does not this is one more thing to be solved by the community so that at least performance critical parts of your application can be AOT compiled. There are solutions to this like Avian or xmlvm but one has to make things work. There is a reason Codenameone provides this as a cloud service for their platform! The last thing to consider is that only having JavaFX on the system is not really enough. You need to interface with platform services and sensors without them you can't write useful applications, so we'd need a cross-platform API for this to develop useful apps. To round up this short post. Yes it's good news but still leaves me with many questions/doubts.

published on
Previous
Experimenting with TextFlow from JavaFX8