CTO Abid Maqbool

Hello Johan 👋
Really appreciate your work and Gluon efforts in keeping JavaFX alive and bringing it to mobile 🚀
GluonFX + GraalVM is truly impressive.

I have a technical question:
With modern GluonFX builds, Android apps seem to support only **arm64-v8a** ABI.

Previously, with JavaFXPorts (javafxmobile plugin), both **armeabi-v7a** and **arm64-v8a** were supported.

@johanvos #JavaFX #Gluon #JavaFXMobile #GluonFX #SubstrateVM #dalvik #AndroidDev #GraalVM

Mar 26 at 3:30pmWeb
Show threadCTO Abid MaqboolMar 26

@johanvos

Is this limitation due to GraalVM/native-image or Android NDK changes?

Many devices (especially in regions like South Asia) still rely on **armeabi-v7a**, and apps built with GluonFX don’t run on them.

Is there any workaround, roadmap, or possible way to support **32-bit ARM (armeabi-v7a)** again?

Would really appreciate your guidance.
Thanks again for your great contributions 🙏

Show threadjohanvosMar 28
@ctoabidmaqbool GraalVM doesn't support ARM32. Best chance I see is the alignment with OpenJDK we're basing on now. OpenJDK still has ARM32, but there is still work as that doesn't mean armeabi-v7a is supported.
I wish there was more support for this.
Show threadCTO Abid MaqboolApr 6

@johanvos

Thanks for the clarification, Johan 🙏

That explains the limitation well. Even partial or experimental ARM32 (armeabi-v7a) support would be very valuable, especially for regions where 32-bit devices are still common.

If there’s ever a prototype or community effort around this, I’d be interested to explore and contribute.

Appreciate your transparency and great work 🚀