Potential task for Wine + Box86/64 developer

[typingmaster12]

We are looking for someone with experience in Wine + Box64 + Android/ARM64 for a potential commercial project.

We have an existing Windows desktop application and are investigating whether it can be packaged into an Android application using Wine + Box86.

The idea would be:

Android ARM64
Wine + Box86 bundled inside the application
Our existing Windows application running locally
No root or Termux required
Potentially distributed through Google Play

We are initially looking for someone who could help with a technical proof of concept, rather than committing to the complete product immediately.

If you have experience with Wine/Box64 on Android, particularly with Winlator or similar projects, please contact me. We can provide the Windows application for testing.

[ptitSeb]

While I can help on the box64 and some wine integration if needed, I cannot help on the specific Android parts. There are part of the software stack there I don't own (like the X11/Wayland layer)

[typingmaster12]

Thanks. The goal would be a self-contained Android APK that bundles Box64 + Wine (64bit with WoW64) + our 32-bit TypingMaster.exe, similar in concept to Winlator, but without needing a general-purpose Windows environment.

Could you determine whether our 32-bit Delphi/VCL EXE can run using Box64 + Wine/Wine-WOW64, and what Wine components are required?

Do you think the missing Android/X11/Wayland layer (is it required?) is a major technical obstacle, or mainly something that needs an Android-specific developer to integrate?

[typingmaster12]

We could test a few different versions of TypingMaster to find the one that is most compatible, modern, and stable for the Android/Wine setup. To get started, it would be easiest to test a very old version first:
https://www.typingmaster.com/TypingMasterCharity6.exe

After starting the installer, please choose:
Standard Install → TUTOR ONLY
Once we know that this version runs successfully, we can move on to newer versions and identify the best version to use.

You can install it e.g. to: C:\tmaster

After installation, you should be able to deploy/copy the entire C:\tmaster folder to the test environment rather than running the installer there. This should make it easier to test different TypingMaster versions quickly. Let's make tmaster.exe to auto-start.