This is a great direction. I've long noticed that Android development on ARM64 under Linux is almost never properly addressed. On Raspberry Pi OS 64-bit, all these "minor inconveniences" are especially noticeable compared to x86.
Regarding your questions:
Instructions. Honestly, it's always useful to have a separate "Raspberry Pi-specific" section for Pi OS, because package versions and paths are often slightly different from pure Debian 13. It would be great to add a minimal build example guaranteed to work on a fresh Pi OS—that would immediately resolve 90% of the initial issues users might have.
Project direction. I completely agree that the idea of not cloning Android Studio, but creating a "workflow layer," is the right one. On ARM64, people often want to compile, run, and get results, rather than have a full-fledged IDE. The service architecture with CLI/GUI clients seems logical and flexible.
Pi-specific aspects. In practice, the most common issues are:
limited RAM (especially on a 4–8 GB Pi) → Gradle and dexing may crash, so consider swap/zRAM;
SD cards quickly die during large builds → SSDs over USB are better;
throttling during long builds;
GTK4 on Pi sometimes behaves strangely on Wayland/X11;
NDK/tools may be x86-specific – this should be clearly stated in the instructions.
Installation format. The ARM community favors a mix: tarball + a simple script for quick start, and .deb for those who want a stable, clean path. Source-build is useful, but more for advanced users.
Overall, the idea seems really useful. It would be cool to see a small “reference setup” for the Pi with minimum requirements and estimated build times – that would greatly lower the entry barrier.
Regarding your questions:
Instructions. Honestly, it's always useful to have a separate "Raspberry Pi-specific" section for Pi OS, because package versions and paths are often slightly different from pure Debian 13. It would be great to add a minimal build example guaranteed to work on a fresh Pi OS—that would immediately resolve 90% of the initial issues users might have.
Project direction. I completely agree that the idea of not cloning Android Studio, but creating a "workflow layer," is the right one. On ARM64, people often want to compile, run, and get results, rather than have a full-fledged IDE. The service architecture with CLI/GUI clients seems logical and flexible.
Pi-specific aspects. In practice, the most common issues are:
limited RAM (especially on a 4–8 GB Pi) → Gradle and dexing may crash, so consider swap/zRAM;
SD cards quickly die during large builds → SSDs over USB are better;
throttling during long builds;
GTK4 on Pi sometimes behaves strangely on Wayland/X11;
NDK/tools may be x86-specific – this should be clearly stated in the instructions.
Installation format. The ARM community favors a mix: tarball + a simple script for quick start, and .deb for those who want a stable, clean path. Source-build is useful, but more for advanced users.
Overall, the idea seems really useful. It would be cool to see a small “reference setup” for the Pi with minimum requirements and estimated build times – that would greatly lower the entry barrier.
Statistics: Posted by Knerve — Thu Jun 04, 2026 1:19 am
/fit-in/580x348/filters:format(webp)/english-betterindia/media/media_files/2026/08/04/1-2026-08-04-18-09-35.png)
/pic9729642.png)
