When JavaFX Script was released, the mobile component was an important part. It was also one of the reasons many people and analysts believed in JavaFX as a real cross-platform client-side framework. For a number of reasons, JavaFX on mobile disappeared from the official Java roadmap. Fortunately, the OpenJFX team at Oracle made all the required sources available, and the JavaFXPorts initiative worked on providing JavaFX SDK's for the mobile platforms. In this session, we will show the current state of JavaFX on Mobile. We will show how to create a real cross-platform JavaFX Application using an IDE, and how easy it actually is to deploy that application on Android and iOS devices. We will show some of the features and limitations, and talk about the eco-system that is starting to take shape.

2. JavaFX Mobile
Johan Vos
Co-Founder and CTO, Cloud Products

3. Java on the client
• Java started on the client
3

4. Java on the client
• Targeting Set-Top Boxes, Video On Demand
– Premature busines models
– Cable providers wanted all control
• Targeting the Internet
– Applet in a sandbox
– Browser wars
– Security concerns
4

5. Then came the server
• Java programming language turned out to be very suited
for enterprise/backend development
– J2EE API’s
– Third party frameworks (Hibernate/Spring/…)
– IDE’s, devops
• Mature business model
• Controlled environments
• Known customers
5

6. What happened to the client?
• Desktop: Swing
• Mobile/PDA:
– KVM/CVM
– CDC/CLDC
– MIDP/PDA/Foundation
– Personal/RMI
6

7. What happened to the client
• Fragmentation
• No way to easily deploy to end consumers
7

8. And then there was JavaFX
• Java Client, rebooted
• Fragmentation?
– Take advantage of hardware evolutions
– Much cleaner high-level API’s
• Deployment?
– Appstores (AppStore and Play Store)
– Developers (or Android/Apple) in control, not the telco
8

9. JavaFX on mobile
• Feb 2009: JavaFX Script 1.1 released, with a mobile
component
• Oct 2011: official support for mobile dropped! (code
being developed)
• JavaOne 2012: hope for mobile…
• JavaOne 2013: hope for mobile…
• Devoxx 2013: kick-off for JavaFXPorts.
9

10. The time is now
• Mobile devices get more powerful
• Standardization
• Growing number of mobile devices
• Business transactions originate from mobile devices
• On mobile devices, apps are preferred over Web
• Appstore maintainers (Google/Apple) make it easy to
distribute apps
10

11. The time is now
11

12. The time is now
12

13. JavaFXPorts
• Use the code in OpenJFX repo
• Apply some Android/iOS specific changes
• Release JavaFX SDK for mobile
• Create a gradle plugin for easy packaging/deployment
on Android/iOS
13

14. JavaFXPorts jfxmobile gradle
plugin
• Both Android and iOS have specific build tools and
require a number of steps in order to create native apps
• Jfxmobile gradle plugin provides tasks that leverage
those build tools
• Android: Android SDK is used
• iOS: RoboVM AOT is used to bundle your JavaFX
Application with JavaFX mobile SDK and core classes
14

15. Gluon
• It’s not just spare time
• Provide commercial support for JavaFX on Mobile
• Provide services and products on top of JavaFX
• eco-system:
– Open source component need commercial support
– Commercial company relies on open source component
• Gluon co-funds JavaFXPorts, other companies invited as
well.
15

16. Gluon
• Free tools:
– Scene Builder
– JavaFX SDK’s
– IDE Plugin’s
• Commercial tools
– Charm (client library, Material Design controls)
– Gluon Cloud (data persistence/synchronization and access to
legacy/cloud systems)
16

17. How hard is it?
• Using IDE (NetBeans/IntelliJ): install plugin
• Download sample and modify
17

18. Links
http://javafxports.org
http://gluonhq.com
https://bitbucket.org/gluon-oss/
johan.vos@gluonhq.com
http://twitter.com/johanvos
18

19. Thanks For Attending
Any Questions?