Play Store Assets & Publishing Checklist

Store artwork

Prepare the assets required by the current Google Play listing requirements. Google can change dimensions, file limits, screenshot counts, and testing requirements, so verify the Play Console checklist for the date of submission.

At minimum, plan for:

• A 512×512 Play listing icon.
• A 1024×500 feature graphic where required by the listing.
• Phone screenshots, plus tablet screenshots when targeting tablets.
• Store title, short/full descriptions, category, content rating, privacy policy, and Data safety declarations.

These listing assets are separate from the binary assets configured in mobile-app/app.config.ts. Use the assets guide for the app icon, adaptive icon, splash, and notification icon.

Configure the Expo app

Before building, verify the Android package and adaptive icon:

android: {
  package: 'com.example.yourapp',
  adaptiveIcon: {
    foregroundImage: './assets/images/adaptive-icon.png',
    backgroundColor: '#ffffff',
  },
}

Use a unique package name and register the same identifier in Firebase, Google Sign-In, and Play Console.

Build an Android App Bundle

From mobile-app/:

pnpm install
eas build --platform android --profile production

The production profile in eas.json creates the release build configuration. The preview profile is configured as an APK for device/internal testing. Review every EAS profile's environment values: the template includes a demo API URL that must be replaced for your app.

EAS can manage Android signing credentials, or you can supply an existing keystore. Keep signing credentials and the package name stable after the first public release.

Submission checklist

• Replace demo name, slug, package, API URL, RevenueCat keys, and AdMob IDs.
• Configure Firebase files for the final Android package.
• Configure Google/Apple sign-in and deep-link scheme.
• Test Account login, Guest startup (if shipping Guest behavior), purchases, restore, ads, notifications, deep links, and account deletion.
• Run pnpm check and npx expo-doctor.
• Build and install the production-like APK/AAB on physical devices.
• Complete Play Console App content, Data safety, content rating, target API, privacy policy, and tester requirements.
• Upload the AAB to an internal/closed testing track before production rollout.
• Review crash, ANR, permission, and pre-launch reports.

Release hygiene

Keep EXPO_PUBLIC_ADMOB_ENABLED=false until every production app/ad-unit ID is configured and consent behavior is reviewed. Never ship seeded backend credentials or development API hosts in a release build.