Skip to content
Primio Docs

Pre-Submission Checklist

Use this checklist before hitting “Submit for Review” on either store. Every item links to the relevant guide for details.

Account & setup

Section titled “Account & setup”
  • Google Play Developer account created and verified ($25 one-time fee) — Sign up
  • Decided: personal or organization account — Organization accounts skip the 14-day closed testing requirement. If you have a registered business, use an organization account. More info

Build

Section titled “Build”
  • AAB built in Primio — AAB is required for Google Play (not APK). Android Builds
  • Custom app icon set — Replace the default template icon before building. Google rejects apps with default or placeholder icons. App Icon
  • Tested on a real Android device — Install the APK on a physical device and walk through every screen. The web preview does not catch device-specific issues. Testing Guide

Store listing

Section titled “Store listing”
  • App name filled in (max 30 characters)
  • Short description filled in (max 80 characters)
  • Full description filled in (max 4,000 characters) — ASO guide
  • Screenshots uploaded — At least 2 phone screenshots; recommended 4-8. Screenshot guide
  • Feature graphic uploaded — 1024x500px banner image. Required for Google Play.
  • App icon — 512x512px. Set automatically from your Primio project icon.

Compliance

Section titled “Compliance”
  • Privacy policy URL entered and working — Test in an incognito browser window. Privacy guide
  • Privacy policy accessible inside the app — Settings screen with a working link
  • Data Safety form completed — Policy → App content → Data safety. Declare all data your app collects including from SDKs like Firebase Analytics and AdMob. Data Safety walkthrough
  • Content rating completed — Answer the IARC questionnaire under App content → Content rating. Content rating guide
  • Pricing and distribution set — Free or paid, target countries selected

Testing (personal accounts only)

Section titled “Testing (personal accounts only)”
  • Closed testing track created with at least 12 testers who have opted in and installed the app
  • 14 continuous days of closed testing completed
  • Production access applied for after the testing period

Release

Section titled “Release”
  • Release notes written — Summarize what your app does for the first release
  • AAB uploaded to the Production track (or promoted from testing)

Top rejection reasons to double-check

Section titled “Top rejection reasons to double-check”

These are the most common reasons first-time submissions get rejected. A quick pass through this list can save you days.

  1. Missing or broken privacy policy URL — Both stores. Test the link in an incognito window.
  2. App crashes — Both stores. Test on a real device, not just the web preview.
  3. Placeholder or test content — Apple especially. “Lorem ipsum,” default images, “TODO” text.
  4. Missing demo credentials — Apple. If your app has login, put test credentials in “Notes for Review.”
  5. App too simple — Apple Guideline 4.2. Single-screen apps or website wrappers get rejected. Your app needs multiple screens with meaningful interaction.
  6. Misleading metadata — Both stores. Your description, screenshots, and name must match what the app actually does.
  7. Missing Data Safety / App Privacy declarations — Both stores. You must complete these forms even if your app collects no data.
  8. Default or missing app icon — Google Play. You must set a custom icon that reflects your actual app.

Next steps

Section titled “Next steps”

Once you’ve checked everything, follow the submission guide for your platform: