Other programming languages • I have been working on an open-source project called APK Workbench

I have been working on an open-source project called APK Workbench:

https://github.com/Denuo-Web/APK-Workbench

It is a Linux ARM64-focused Android development workbench built mostly in Rust, with a GTK4 UI, CLI tools, and gRPC services for toolchain management, builds, device/target handling, job progress, logs, and support/evidence bundle exports.

The main reason I built it is that Android development on ARM64 Linux hosts is still awkward compared with x86_64 desktops. APK Workbench is not intended to clone Android Studio. It is more of an ARM64-first tooling layer for Android build workflows, especially on Debian-based ARM64 systems.

The currently validated path is Debian 13 on Linux ARM64, and Raspberry Pi OS 64-bit is included in that path. The repository also has Cuttlefish-related target handling, toolchain catalog support, Gradle wrapper helpers, and a service-oriented architecture where the GTK UI and CLI are thin clients over local services.

A few relevant details:

* Host target: Linux ARM64 / aarch64
* Primary distro path: Debian 13 ARM64, including Raspberry Pi OS 64-bit
* Main language: Rust
* UI: GTK4
* Architecture: local gRPC services plus CLI/GUI clients
* Purpose: Android SDK/NDK/toolchain/build workflow support on ARM64 hosts

I would be interested in feedback from Raspberry Pi users who have tried to do Android development, Android builds, or ARM64 toolchain work directly on a Pi or another ARM64 Linux machine.

In particular, I am interested in:

1. Whether the setup/build instructions are clear enough for Raspberry Pi OS 64-bit users.
2. Whether the project direction makes sense for people doing Android-related work on ARM64 hardware.
3. Whether there are common Pi-specific constraints I should account for, such as memory limits, storage layout, GPU/graphics behavior, or packaging expectations.
4. Whether a Debian package, tarball release, or source-build workflow is the most useful installation path for this audience.

This is still early, so I am not presenting it as a polished replacement for established Android tooling. I am mainly looking for technical feedback.

Statistics: Posted by denuoweb — Sun May 31, 2026 12:41 am

---