This all isn't worth it.
If you want to create Android apps you either have to do it in Java or in Kotlin.
All other attempts will just translate the final code to the android java version.
In that process a lot is lost - mainly capability and performance.
Apologies on disagreeing, but from what I've read it appears things are changing or have changed. Definitively not saying there is anything wrong with Java, just that it appears not the only way to go. Companies are using JavaScript (not to be confused with Java) and C# to build applications for use on multiple OSes. For JavaScript there is Electron, Proton Native, Titanium, PhoneGap, Ionic, etc... "Write in JavaScript, run native everywhere". And C#, with Xamarin, has the weight and muscle of Microsoft behind it. Microsoft is making a hard and consistent push of their .NET framework on Android, iOS, Linux, and macOS.
Just finished reading the thesis of a college student who ported his .NET application over to Android last year.
https://www.researchgate.net/publicatio ... Mobile_App
AHK would have to be rewritten from scratch - different instruction - different paradigm (OOP only) - and different focus (can't focus on hotkeys on android can you)?
So in the end we would get a product that has nothing to do with AHK in the slightest.
What you suggest is not a feature but switching to a new language and developing that language for you.
I think that was the point of IronAHK. To port the AutoHotkey language so that it could be used on other platforms. Polythene was on to something. Let's for a second imagine if he completed the project, it would have opened the door of AHK programmers riding the wave of .NET and Microsoft into Android, iOS, Linux, and Macs. IronAHK and AutoHotkey would have been joined in terms of concept and commonality of language and syntax. Finding ways to do things easier or faster through automation, macros, or shortcuts. And Android does have a scripting layer that several other languages have joined the party on like Python, Lua, Perl, JavaScript, etc...
https://en.wikipedia.org/wiki/Scripting ... or_Android
@SOTE:
It's incredibly different to target multiple desktop and window managers. We just barely manage to target the windows window manager.
Doing that requires access to low level instructions and low level interaction with the OS - specific too the OS.
C# and Java are both made to create code that runs on the system by only scratching the surface and never going deep into the OS.
The only way to circumvent that is using specific libraries written in C that this language would wrap around.
However when you have a langauge that already wraps around this library in a good way - why even use AutoHotkey anymore when you can use the language it is written in?
Regardless languages like Java and C# are a dead end for AutoHotkey and you might as well just develop in C/C++ rather than developing only parts in C/C++ and create multiple releases for multiple OSes.
The point of IronAHK seems to have been: 1) expand the user base. Users not just on Windows, but on other OSes. "AHK Forever!" OK, maybe I got a little bit carried away, but you get my point. 2) To be able to put the AutoHotkey language and automation abilities to where it's needed. How many of us
have Android phones and iPhones? In fact, if Google plays it's cards right, it might be able to
eat up Microsoft market share on desktops too. Android tablets, laptops, and desktops are very viable options, which is probably why Microsoft has put MS Office on the Android and is giving away Visual Studio (Community version) and Xamarin to get more .NET developers. 3) Making a more useful tool. If the problem is solved with AutoHotkey, then it's as good as any other language that can be used. AutoHotkey has it's lane where it can be advantageous by it being strong in automation, macros, and shortcuts.