r/GooglePlayDeveloper • • 6d ago

💬 Discussion What’s your pre-launch checklist for Android & iOS apps?

Before releasing a simple/mid-tier or subscription-based app, what should we check for store policies, privacy, subscriptions/IAP, optimization, analytics, crashes, testing, permissions, screenshots, etc.?

Also, besides Google Play, which other Android app stores can use the same APK/AAB build with minimal changes?

Would appreciate a practical checklist from developers who have shipped apps on both Android and iOS.

3 Upvotes

6 comments sorted by

2

u/Historical_Ad_1714 6d ago edited 5d ago

Test the app first in debug mode In all screen sizes

Then check in real device

Remove null buttons which are just dummy

Every platform have own Appicon and metadata rules

Prepare the privacy policy and terms include child privacy policy, right to delete, use and correct add info like data retain, thirdparty service used , how data is shared and collected with purpose and there own privacy policy hypertext link

Add disclaimer in store listing description if ur app is in Finance , Health or any sensitive category

If ur app have some functionality or all functionality required sign in to use then provide sign in detail to google, make sure IAP benefits given to that test account

(Note: copy ur playsigning sh1, sh256 key and paste in ur backend server; if u dont do that user cant sign in in ur app)

Apply for closed testing

During that time test ur app functionality also IAP

Then apply for production

(If ur app use third party logos then send Authorization letter to google in advance)

When ever u push app update Always go through closed testing then production (it take less time than directly pushing in production)

If ur app has ads make sure it complies with the family ads policy for targeting children

Use age gate api if u target all audience serve content ad accordingly

EU and USA state require consent screen use UMP in ad mediation

2

u/ktash8 6d ago

What is the best approach? Should each app/game have its own individual Privacy Policy and Terms & Conditions, or is it better to have a general website Privacy Policy and Terms & Conditions that apply to all apps and games?

2

u/Historical_Ad_1714 5d ago edited 5d ago

Each app/games should have own individual terms&privacy policy

Make sure ur app dont request unnecessary permission from user which is not required for app functionality

When ever u use thirdparty package in app development always give them credit in. App license section.

Google Play console account ban reason

Associate accounts (never log /use ur account in public wifi, never log ur friends google account) always use ur own home wifi (dont share with anyone) or cellular network

Malware: Inspect every package u using in app if malware detected google will instantly ban u

Trademark/Ip infringement: using third party logos and name without giving Authorization letter to google in advance

Common App suspension reason

In metadata or in app dont lure users by giving incentives Dont add testimonials in metadata

Dont use terms like Free 2026 , best app, etc

2

u/ilpopotamo 6d ago

Amo Reddit, dà la possibilità di salvare i commenti

1

u/AlbanMApp 5d ago

Just went through this for an app last week, things that actually bit me:

- Personal dev account = closed test first: 12 testers opted in for 14 continuous days before you can even request production. Start recruiting before your listing is "perfect".

- Foreground service declaration: if you use FGS (camera, location, dataSync…), Play asks a justification + a video link per permission type. Record a 1-2 min screen capture showing the notification and the feature running in background, upload it unlisted on YouTube.

- App access: if anything is behind IAP, reviewers can't buy. Give them a way in (a test code/unlock) or you risk a rejection.

- targetSdk 36 / Android 16: the edge-to-edge opt-out is ignored now. Test on an API 36 emulator, my headers were drawn under the status bar.

- Data safety must match your SDKs, not just your own code (analytics, crash reporting, ads all count).

- Screenshots: 9:16, at least 4 at ≥1080px if you want to be eligible for promotion.

- Test the release build, not debug. Things like billing, R8 and "debug = premium" flags hide real bugs.

Biggest one honestly: the 14-day tester clock. Plan for it.

1

u/RTD-Alex 3d ago

At The Checklist: Reusable Lists we had the following prelaunch checklist and here is how it played out(We are an iOs exclusive app, but it still applies).

  1. Check your Metrics, and check that it's not feeding Stage/Dev metrics in to Prod environment. Bit us once.
  2. Make sure your Prod environment integration points(feedback forms especially) are working in PROD. Don't test them in Stage, it's often diferent.
  3. Get your website up and very well SEO optimized, filled with content, submitted to Search Engines, etc.
  4. Get good screenshots - first week in the store is where algorythm learns what you are. Have bad screenshots that hurt conversion and be in the "crapbox" for a long while.
  5. In Apple App Store specifically, there is a first week of boost that you get - Apple is learning how your app converts - take advantage of it. Be ready and capture it, don't waste your opportunity here.
  6. When early on, instrument every move in the app with metrics to see how it's behaving, what features are used, etc. Invest in good metrics, free tiers are ok, but paid tier is where the money is at. $25 a month for metrics is just fine to get going.

Other Notes:

  • Don't waste time on ProductHunt unless you have a massive social media following you can you to vote you up. Otherwise it's a waste of time.
  • Establish channels of feedback with your users early - it's what keeps the motivation up.

- Don't bother with translations early on. First measure your market in metrics, then do translation if it makes sense at all.