Android quickstart

📘

Note

Verify you completed the mobile SDK quickstart before completing the Android quickstart.

Configure the following before deploying your Commerce App to the Google Play Store:

• Android SDK components – Choose whether to use Visual Studio Code or Android Studio. Optimizely recommends using Android Studio before doing any deployment. Depending on your local setup, Android Studio may prompt you to install additional required tools and components to build and run the app properly.
• pubspec.yaml – Update the version to 1.0.0+1 or higher.
• Application ID – Go to android/app/build.gradle and update the applicationId to your desired ID. For example, change com.dxp.commerce to com.insitesoft.commercemobile.
• AndroidManifest.xml – Go to android/app/src/main/AndroidManifest.xml and update adroid:label, which is the text displayed after users install the app.
• App icon – Go to android/app/src/main/res to update the app icons.
• Logo inside the app – Update assets/images/logo.png.
• Keystore File

Notes on app signing and keystore ownership

Every Android app published to Google Play must be signed with a keystore.

Optimizely encourages all partners and customers to generate and manage their own keystore. This ensures full control over app publishing and long-term security.

If you need to change or update the keystore used for your app, the Google Play account owner can request an upload key reset directly in Play Console. Once reset, you can start using your own keystore to sign and upload updates, while Google Play ensures users continue to receive app updates without disruption (through Play App Signing).

🚧

Important

Do not lose your keystore or its passwords. Store it in a secure location (such as a company password manager or secure vault). If it is lost or compromised, you may face delays while requesting another reset from Google.