Android App Build

The Android build is a standard signed app, but the details decide whether it can be updated later. Use your own package name, signing key and Play Console account from the first release.

Before you build

• Android Studio and a supported JDK installed.
• The customer, vendor and rider source projects from your package.
• A unique package ID you control, such as com.yourbrand.customer.
• The production API URL and HTTPS certificate ready.
• A Firebase project with the Android package registered.
• A Google Play developer account and a privacy policy URL.

Configure

1. Change the application ID and app name in the Gradle and manifest files.
2. Set the API/base URL to your production domain.
3. Add the google-services.json file from Firebase.
4. Replace the icon, splash screen and colours.
5. Check map, payment and push keys for the production environment.
6. Confirm the app uses HTTPS and does not allow cleartext traffic.

Signing

Create a release keystore and store it outside the repository with its passwords in a password manager. Losing the key makes it impossible to update the app under the same listing unless Play App Signing is configured and can recover it. Enrol in Play App Signing and keep the upload key backed up.

keytool -genkeypair -v -keystore upload-keystore.jks \
  -alias upload -keyalg RSA -keysize 2048 -validity 10000

Build and test

1. Build a signed release AAB, not only a debug APK.
2. Install on a clean device and complete a real order in sandbox mode.
3. Test push, maps, payment redirect, deep links and offline behaviour.
4. Check the app on a small screen and a current Android version.
5. Upload to the Play Console internal testing track first.

Store listing

Prepare screenshots, a short and full description, the feature graphic, the privacy policy and the data-safety form. Declare location, payment and personal data accurately. A rejected data-safety form can delay a launch more than a code bug.