Android: App distribution

Technical specification for distributing the PestControlOS Android app via Firebase App Distribution.

Method

Firebase App Distribution: The Android app is distributed via Firebase App Distribution (not the public Google Play Store). Builds (APK or AAB) are uploaded to App Distribution; testers and technicians are invited via email or added to groups.
Access control: Distribution is managed from the Firebase console. Only invited users (or members of designated groups) can see and install builds. No public listing; reduces exposure and ensures only your organisation receives builds.

Build: Produce release or pre-release build (e.g. ./gradlew bundleRelease or assembleRelease). Sign with your keystore; version code/name set in build.gradle.
Upload: Use Firebase Console (App Distribution) or gradle firebaseAppDistributionUpload (if configured) to upload the build. Assign to groups (e.g. "Technicians", "Testers") or individual testers.
Install: Testers receive email link or open the App Distribution link; install the APK (unknown sources must be allowed on device for non-Play installs). No FCM or Play Store dependency for distribution itself.
Updates: New builds can be distributed to the same or different groups; version code must increase. Users can be notified of new builds via email (App Distribution feature).

Builds are served over HTTPS; only authenticated/invited users can access. Aligns with controlled delivery and avoids public store listing. Suitable for internal or B2B distribution where Play Store publication is not required.

Each Firebase project has its own App Distribution; per-company Firebase projects imply per-company distribution lists and build history. No cross-tenant sharing of builds.