Since the Android SDK came out last week, I've been toying with the idea of porting ME4SE into Android as to make it as easy as possible to port over current JavaME code. With ME4Android, I wanted the porting to be done automatically so no lines of JavaME code would need to be modified but only the build scripts, so targeting Android would only require a rebuild of current JavaME code.

On my first pass at ME4Android, I used our rather large JavaME app called FlyerApp as the test app. This code is done completely on top of Canvas so it only uses JavaME's low level user interface libraries. The code uses a few threads, supports animations and does networking. I figured if ME4Android can run FlyerApp, it will be able to run a lot of Java games too.
...
:arrow: Read his full article.

tberthel wrote:Well my games are J2ME and run on Android and J2SE, but I use emulation.

So you can have multi-platform support, but developing a new project for each OS is an alternative.

I conclude you can do either and they both have merit.

tberthel wrote:Well MicroEmulator supports all of J2ME not just a single API. The Bridge pattern often used to do emulation should be only about 10 percent overhead just like virtualization.

So your are correct in some cases, but my games perform fine on all three platforms and more than 20 operating systems. My little action games show it is possible. Although, it did take some performance improvements and forethought.

tberthel wrote:You are wrong about support for OpenGL ES and M3G.

tberthel wrote:Because those implementations do exist.