APK Delivery Guide
How to keep downloads live
The website now prefers an environment-configured APK URL, falls back to a local APK file when available, and otherwise uses the default GitHub release:
NEXT_PUBLIC_ANDROID_APK_URL -> custom public APK URL
Fallback 1: public/downloads/loom.apk
Fallback 2: GitHub release APK URL1. Build or get your APK
Export a signed release APK from Android Studio or your app build system and keep the version number updated for each release.
2. Upload it to GitHub Releases
Attach the latest APK to your GitHub release and copy the public asset URL so the website can send users straight to the newest build.
3. Set the website download URL
Set NEXT_PUBLIC_ANDROID_APK_URL to the GitHub release asset URL in your project environment variables when you want production to override the built-in release link.
4. Keep the local fallback if needed
If you ever want to ship the APK from the repo instead, place it at public/downloads/loom.apk and redeploy. The site will use that when no environment URL is configured.