What I like very much is the following:

  • It uses native UI controls, so you do not suffer from FireMonkey restrictions about Unicode/RTL languages and such, and have a native look and fill;
  • It consists in a set of Java classes, used as glue to the Android platform, accessed via JNI from a FPC-compiled library;
  • It creates very small application files (great for downloading) - the FPC compiler generates a .so binary library which compresses to a bit more than 100 KB;
  • There is some nice low-level units in JNI for bridging the object pascal code to Java;
  • Most of the logic is written in Java itself, so you do not have to fight with event or low-level Java structures translations in object pascal code;
  • Framework code is still readable and does not suffer from multi-platform targeting;
  • You can re-use you own existing object pascal code, with no problem of restrictions/regressions due to Delphi NextGen compiler;
  • As a result, you are encouraged to separate your business logic from your UI code - which is a good idea;
  • Sounds to be stable in practice, even in early stage - its "glued" design sounds easier to debug than the huge FireMonkey, if you are able to read some limited Java code;
  • You have a sibling Native iOS Controls project using FPC available to target also iPhone/iPad devices;
  • It is Open and expandable, so you are able to fork the project if needed.
Drawback is that:
  • It is more like a proof-of-concept than a whole framework, in its current stage;
  • It is not well known nor supported by a big company (worth a new tag in Stack Overflow?);
  • It is free so you won't give away your money to Embarcadero.
It is definitively one step forward for pushing us in direction to FPC full support for mORMot!