Development on Android phones only, connected to GitHub CI

At Mick Lab, app development is completed using only an Android smartphone. A Linux environment runs inside Userland / Termux, implementation work is done with Copilot CLI, and scripted operations connect the workflow to GitHub CI.

Development stack

• Device: Android smartphone
• Environment: Userland / Termux (Linux user space)
• Implementation support: Copilot CLI (terminal-based development)
• Operational scripts: android_base.sh / push.sh

Role of the scripts

• android_base.sh: given <ProjectName> <GitHubRepo> [public|private], it generates the Android project skeleton, Gradle settings, Manifest, MainActivity, and CI workflow.
• It creates .github/workflows/android.yml, including Gradle 8.2.1 setup, assembleDebug, and APK artifact upload.
• push.sh: operational helper that runs git add/commit/push and triggers GitHub Actions.
• Initial setup also executes gh repo create ... --push so repository creation and the first push are automated.

CI flow (summary)

1. Generate the project and CI definition with android_base.sh
2. Implement and revise code on Android + Userland / Termux with Copilot CLI
3. Push changes with push.sh
4. Let GitHub Actions run the Android CI / Hosting workflows

Why this setup exists

The goal is a reproducible workflow that removes the PC requirement and keeps continuous development possible on a mobile device alone. Mick Lab apps are improved on top of this operating foundation.