BowlerKitBowlerKit

Play Store Assets & Publishing Checklist

10/11/2026

Prepare Flutter launcher assets, an Android App Bundle, and the Google Play listing.

Store artwork

Follow the current Google Play listing requirements. Dimensions, file limits, screenshot counts, and testing gates can change; verify the Play Console checklist when submitting.

Plan for the listing icon, feature graphic (where required), phone/tablet screenshots, title/description, category, content rating, privacy policy, and Data safety declarations. These listing assets are separate from Flutter binary assets generated by flutter_launcher_icons and flutter_native_splash.

Configure the Flutter app

Before building, verify the final Android application ID and Firebase registration. The current template uses com.soewidiputra.flonlate.mobile and generated flutter_launcher_icons.yaml/flutter_native_splash.yaml assets. Replace template artwork and identifiers before release.

Build an Android App Bundle

From mobile-app/:

flutter pub get
dart run build_runner build --delete-conflicting-outputs
flutter build appbundle --release

Use flutter build apk --release for direct device/internal APK testing. Pass platform RevenueCat keys with --dart-define and ensure Firebase options, AdMob IDs, signing, and the final API_BASE_URL are configured.

Submission checklist

  • Replace demo name, package/bundle IDs, API host, Firebase options, RevenueCat keys, and AdMob IDs.
  • Regenerate launcher/splash assets and native projects after identifier changes.
  • Test Account login, Guest startup (if shipping Guest), purchases/restore, ads, notifications, deep links, and account deletion.
  • Run flutter analyze, flutter test, and a release-like flutter build appbundle.
  • Install the release-like build on physical Android devices.
  • Complete Play Console App content, Data safety, content rating, target API, privacy policy, and tester requirements.
  • Upload the AAB to internal/closed testing before production rollout.
  • Review crash, ANR, permission, and pre-launch reports.

Store policies are external and time-sensitive. Do not copy a fixed tester count or waiting period from an old guide; follow the current Play Console instructions for the account type.

Release hygiene

Keep AdMob IDs and RevenueCat keys in the build configuration, not source control. Never ship seeded backend credentials or demo API hosts.