It has helped the organization to reduce the turnaround time and improve productivity as it equipped us to churn out cross-platform applications faster (Android/iOS).
It's helped us to handle end-to-end lifecycle for enterprise mobility solutions.
IPA/APK file sizes are very large compared to builds generated using other technologies.
It needs more control on gestures and animations.
While taking iOS builds using JDeveloper, sometimes it fails. To debug, we have to use Xcode.
Also, the IDE gets slower while connecting to subversion.
Also, build generation time is longer comparing to other technologies.
It's stable now, but there are the issues described above.
We have had no issues scaling it for our needs.
Forums and groups are not very active, and we were not able to find answers for our queries by searching documentation.
The initial steps are a little bit complex because a lot of the dependency is related to Java JDeveloper, Android, and iOS versions.
We implemented it in-house. Oracle MAF is evolving as of now, but there are some limitations that we came across.
The only challenge with MAF is that the forum support is not up to mark and it sometimes gets difficult to resolve issues/limitations while implementing mobile app solutions.
I would highly recommend Oracle MAF as it is: