Felipe Andrade – Mobile Developer Cross-platform development: WRT | Flash Lite | Python | Symbian | Qt | Maemo | Meego

Working with 3D Graphics in Flash Lite and in Java ME

This post introduces a discussion over the Mobile 3D features for the Java 2 Micro Edition (JSR 184) and Adobe Flash Lite. First of all, I need to explain that 3D graphics is not necessarily for games, it can be used for the user interfaces, becoming unique and providing new ways to design more intuitive interfaces.

Some time ago I made a TicTacToe Java 3D game. You can download the source code and executable here:

[Jad - Jar - Source Code]

In this post I will not talk in-depth features of each one, some time ago I wrote a small introduction to the Java JSR 184 specification and there are a lot of openly information available:

Java ME

Getting Started With the Mobile 3D Graphics API for J2ME
3D graphics for Java mobile devices, Part 1: M3G's immediate mode
3D graphics for Java mobile devices, Part 1: M3G's retained mode

Mobile 3D Developer Resources - Sony Ericsson Developer

Khronos Group - Open GL ES

Flash

Kirupa

PaperVision 3D - [Blog - Site]

While the Mobile 3D Graphics API is an optional package in Java ME devices, Flash Lite doesn't have no low level 3D graphics API for them so how can you choose among them?

If you choose Flash Lite you can avoid fragmentation with vectors graphics, or use a sequence of images exported from a 3D tool. Remember that it's not an ideal approach.

In Java ME you can consider use the Mobile 3D Graphics 1.0 (JSR-184) or Mobile 3D Graphics 2.0 (JSR-297). The JSR 239 API unites the performance of OpenGL ES with the portability of Java.

Some points to consider while choosing for a 3D mobile platform:

- Fragmentation
- Complexity (Learn curve)
- Native 3D Support
- Power Intensive

In my point of view if I choose to make a hardcore 3D game, without doubts I will choose Java ME platform, but if I choose to make a 3D graphical interface, Flash Lite is the key platform.