I think it would be nice if we can add mobile targets like android in the targets section in documents.
Today, I started to just learn heaps and was not successful to deploy it on android as there is no guide for that.
It would also nice to add guides and tutorials about touch handling and also guides to extend the engine using some plugins to add native utils like purchase, admob, sensors and so on.

However yes, I should try to spent some time looking at what it involves exactly. I don’t do mobile dev on daily basis so the mobile port was not by playdigious for Evoland 2 Android/iOS which runs well using Heaps + HashLink/C.

Maybe a bash script can be added and can automate the stuff that we have it in lime, in the engines that use lime, like HaxeFlixel, you just need to to type lime test android. As heaps can deploy on top of HashLink, it is possible too.
However, the stable version of Haxe is 3.4+ and running heaps with HashLink gives error of incompatible HashLink binary.
I can also help if I pass these steps before destroying my Arch linux

The main thing with a mobile build environment is – it has to be kept up to date (and ideally with historical support) as XCode and Android Studio are versioned. That’s a tedious job that ideally would be maintained jointly by community members who use it regularly (e.g. for their jobs.)

Even lime’s build system seems to be running behind at times.

While using AIR isn’t ideal for performance, it does have four incredible features:

it’s free,

it’s maintained by Adobe,

it’s entirely command-line / scriptable, and

it supports iOS builds entirely from Windows (and Linux via wine.) – or at least it used to / is designed to… times may have changed.

Just to inform you that I have started working on a Heaps/HashLink/Android project setup that does not require anything to download (apart Android Studio + NDK). It’s not yet ready - it just compiles hashlink but does not yet start the SDL window - and I will announce it when it’s completed, but you can watch changes here:

So you took the CMake route to do that. Sounds like a good plan to have something up and running quickly. We can later come up with some Haxe scripts to generate the project files and stuff like that pretty much like Lime does.