libgdx

At least one team at Google has used libGDX (on top of RoboVM): Ingress uses libGDX for their iOS and Android clients.

I moved from J2ObjC to libGDX because of the ui layer, which is fully integrated in libGDX.

PlayN is more of a 2D engine, whereas libGDX is a framework you pick and chose functionality from.

We've been using a similar approach for libGDX [1] with great success for the past 3 years.

It seems to me that RoboVM+libgdx is utilized heavily for the game industry.

I've done pooled versus non-pooled tests of objects like Vector3's in libgdx and the difference in memory pressure is fairly huge.

Great news overall, I can finally add a proper Windows Phone/10 target for libGDX.

Funnily enough it's a different matter for games, see Unity, UE4, libGDX, Cocos2D-x etc.

Mario Zechner's Book mentions the early version of libGDX, I have used it.

I've used libgdx[1] before, it's still fully supported and is being developed further.

RoboVM really is killer, and libGDX is too.

I've done this successfully with libGDX/RoboVM for my game Feldspar.

Mario's not hiding any "well, kinda" bits when he says libGDX will run everywhere he mentioned--there are no second-class citizens in their world and it really benefits from that approach.

Unfortunately, some game engines just give you the Camera and basic stuff, and you must implement scrolling yourself while wondering, "Am I doing this right?" (mostly I use LibGDX).