This is a draft of a feature that is work in progress. If you have questions or suggestions, please leave a comment on the Android forum thread!

• Install Android SDK 2.2 or better.
• Install jMonkeyEngine SDK
• (Optional) Install NBAndroid in the jMonkeyEngine SDK:
  1. Go to Tools→Plugins→Available Plugins.
  2. Install the "Android" plugin.

• Android 2.2 device or better
• Graphic card that supports OpenGL ES 2.0 or better
• Does my phone meet the requirements necessary to run jMonkeyEngine 3?

• Android touch events are translated into mouse events.
• No more unhandled exceptions (i.e. no more black screens)
• Lifecycle management
  • Leaving the activity with the Back key destroys the app (quit).
  • Leaving the activity with the Home key freezes the app in the background. When you return, the app is in the same state as when you left it (pause).
• Currently supports all jmetests except:
  • Framebuffers - WIP
  • Shadows - WIP
  • Water - not tested yet

Mobile deployment is a "one-click" option next to Desktop/WebStart/Applet deployment in the jMonkeyEngine SDK.

• Automatic creation of Android harness and settings.
• Ant script build target creates APK file.
• Ant script run target executes APK on Android Emulator or mobile device.

1. Make sure you have installed the Android Project Support into the jMonkeyEngine SDK.
2. Open the jMonkeyEngine SDK Options>Mobile and enter the path to your Android SDK directory, and click OK. E.g. /opt/android-sdk

1. Open an existing JME3 project, or create a new JME3 project.
2. Right-click the project node in the Projects Window and open the Properties.
3. In the Application>Mobile Properties, enable Mobile Deployment, and select an Android target.
   This creates a "mobile" folder in your projects directory. This folder contains a complete android project with correct settings to run the application using the AndroidHarness.
4. (Restart the jMonkeyEngine)
5. A Mobile Files node appears in the Project window.
   It lets you edit the MainActivitity.java, the AndroidManifest.xml, and build.properties.

The Android deployment option creates a separate sub-project for android and makes the main project and associated libraries available to the sub-project as libraries. The sub-project can be edited using NBAndroid (see below) or using Eclipse or any other IDE that supports standard android projects. Normally you do not need to edit the android project files. Exceptions are described further below. The libraries are first added to the android sub-project when the main project is built for the first time.

Open your game project in the jMonkeyEngine SDK.

Building

1. Right-click the project node to build your project.
   An APK file is created in the "dist" folder.

Running

1. Right-click the project node and choose Set Main Project.
2. Select the "Android Device" build configuration next to the Run toolbar button.
3. Make sure "Compile on Save" is disabled in your project preferences.
4. Run the application on a connected phone by right-clicking it and selecting "Run" or press the "Play" button in the toolbar.
5. The application will run and output its log to the "Output" window of the SDK.
6. When finished testing, click the "x" next to the run status in the lower right to quit the logging output.

The default android run target uses the default device set in the Android configuration utility. If you set that to a phone you can run the application directly on your phone, the emulator does not support OpenGLES 2.0 and cannot run the engine.

Optionally, download Jme3Beta1Demo.apk

During build, the libraries and main jar file from the main project are copied to the android project libs folder for access. During this operation the desktop-specific libraries are replaced with android specific JARs.

Be aware that logging has been identified as having a significant performance hit in Android applications. If getting poor performance please try turning logging either down or off and retesting.

Activating the nbandroid plugin in the jMonkeyEngine SDK is optional, but recommended. You do not need the nbandroid plugin for Android support to work, however nbandroid will not interfere and will in fact allow you to edit the android source files and project more conveniently. To be able to edit, extend and code android-specific code in Android projects, install NBAndroid from the update center:

1. Open Tools→Plugins→Settings
2. Go to Tools→Plugins→Available Plugins.
3. Install the NbAndroid plugin. (Will show up as Android)

• The package name parameter is only used when creating the project and only sets the android MainActivity package name
• The needed android.jar comes with the plugin and is automatically added to the android build
• All non-android project libraries are automatically excluded from the android build. This is currently hard-coded in the build script, check nbproject/mobile-impl.xml for the details.
• The main application class parameter for the AndroidHarness is taken from the jme3 project settings when enabling android deployment. Currently it is not updated when you change the main class package or name.
• When you disable the mobile deployment option, the whole “mobile” folder is deleted.
• The "errors" shown in the MainActivity are wrongly displayed only in the editor and will disappear when you install NBAndroid (see below).
• To sign your application, edit the mobile/build.properties file to point at valid keystore files.

You can use the jMonkeyEngine SDK to save (theoretically) any jMonkeyEngine app as Android app. But the application has to be prepared for the fact that Android devices have a smaller screen resolution, touchscreens instead of mouse buttons, and (typically) no keyboards.

• Inputs: Devise an alternate control scheme that works for Android users (e.g. using com.jme3.input.controls.TouchListener). This mobile scheme is likely quite different from the desktop scheme.
• Effects: Android devices do no support 3D features as well as PCs – or even not at all. This restriction includes post-processor filters (depth-of-field blur, bloom, light scattering, cartoon, etc), drop shadows, water effects, 3D Audio. Be prepared that these effects will (at best) slow down the application or (in the worst case) not work at all. Provide the option to switch to a low-fi equivalent!
• Nifty GUI: Use different base UI layout XML files for the mobile version of your app to account for a different screen resolution.

Best Practice: Ideally, you write the core application code in a way that it checks for the environment it's being run on, and automatically adapts the device's limitations by switching off effects, changing input mechanisms etc. Learn how to read graphic card capabilites here.

As described above, you should always try to design your application as platform independent as possible. If your game becomes a sudden hit on android, why not release it on Facebook as an applet as well? When your application is designed in a platform independent way, you don't have to do much more but check a checkbox to deploy your application as an applet. But what if you want to for example access the camera of an android device? Inevitably you will have to use android specific api to access the camera.

Since the main project is not configured to access the android api directly, you have to install NBAndroid (see above) to be able to edit the created android project in the SDK. After installing, click the "open project" button and navigate to the "mobile" folder inside the main project folder (it should show up with an android "a" icon) and open it.

Although you will use android specific api, using a camera is not exactly android specific and so you should try to design this part of the application as platform independent as possible as well. As an example, if you want to use the phones camera as an image input stream for a texture, you can create e.g. the AppState that manages the image and makes it available to the application inside the main project (no android code is needed). Then in the android part of the code you make a connection to the camera and update the image in the AppState. This also allows you to easily support cameras on other platforms in the same way or fallback to something else in case the platform doesn't support a camera.

Note that you have to build the whole project once to make (new) classes in the main project available to the android part.

The SDK will later provide tools to adapt the material and other graphics settings of the Android deployment version automatically.

• Android Forum Thread (beta)
• Android Forum Thread (alpha)