How to Publish Your App on Google Play and the App Store from India (2026 Checklist)

Your app is finished – now comes the part that surprises most first-time founders: getting it published on Google Play and the App Store. Store rules have become much stricter, and most launch delays we see are caused by missing accounts, forms or policies rather than code. This checklist walks through every step for businesses in India, based on the apps RelieveX Labs publishes for clients – including DVM, Parozo and the Krishna School app.

Step 1: Create the developer accounts (do this first)

Google Play Console

• One-time registration fee of US$25.
• Choose personal or organisation. Organisation accounts need a D-U-N-S number (free, but it can take days or weeks) and verified business details.
• Identity verification is mandatory – keep PAN/Aadhaar or business documents ready.

Apple Developer Program

• US$99 per year.
• Organisations also need a D-U-N-S number and a business website.
• Enable two-factor authentication on the Apple ID.

Tip: open the accounts in your company's name. You should own your store listings – not your developer.

Step 2: Plan Google Play's closed testing

Since November 2023, new personal developer accounts must run a closed test with at least 12 testers who stay opted in for 14 consecutive days before applying for production access. Plan this into your timeline – ask staff, family or loyal customers to install the test version and actually use it. Organisation accounts are exempt, which is another reason businesses should register as an organisation.

Step 3: Privacy policy and account deletion

• Privacy policy: both stores require a public URL that explains what you collect, why, and how users can contact you.
• Account deletion: if users can sign up, they must be able to delete their account from inside the app. Google Play also requires a web page where users can request deletion without the app.

Every project page on our site can host both – see the privacy policy and delete-account links on the BAGALEPA community app page, for example.

Step 4: Data safety (Google) and privacy details (Apple)

You must declare every type of data the app collects (name, phone, location, photos, payment info), whether it is shared, and whether it is encrypted in transit. Include data collected by SDKs such as Firebase or analytics tools. Inconsistencies between this form, your privacy policy and the app's behaviour are a common reason for rejection.

Step 5: Store listing assets

Write descriptions for people first, but include the words they search – "school app", "restaurant billing", "clinic management".

Step 6: Technical requirements

• Target API level: Google raises the minimum target Android version every year. Apps that fall behind cannot publish updates – a yearly maintenance plan avoids this.
• App signing: Play App Signing and Android App Bundles (AAB).
• iOS builds uploaded through Xcode or EAS (for Expo/React Native apps) to App Store Connect.
• Permissions: request only what you use, with a clear reason (camera, location, notifications).

Step 7: Review notes and test accounts

If your app needs a login, give reviewers a working demo account and short instructions. Apple reviewers especially need to reach every feature. Missing demo access is one of the most common rejection reasons.

Step 8: Launch and after-launch

1. Release to a small percentage first (staged rollout on Google Play).
2. Watch crash reports and reviews for the first week.
3. Reply to reviews – it builds trust and ranking.
4. Link your website to the store listings and vice versa.

Full checklist

• ☐ Google Play account (organisation + D-U-N-S recommended)
• ☐ Apple Developer Program membership
• ☐ Closed test with 12+ testers for 14 days (new personal Play accounts)
• ☐ Privacy policy URL
• ☐ In-app account deletion + web deletion page
• ☐ Data safety form / App privacy details
• ☐ Icon, screenshots, feature graphic, descriptions
• ☐ Demo account for reviewers
• ☐ Current target API level, signed AAB, iOS build
• ☐ Maintenance plan for yearly policy updates

Common rejection reasons (and how to avoid them)

Keeping your app compliant every year

Publishing is not a one-time job. Google updates its target API level requirement every year, Apple introduces new privacy rules and SDKs need updates. Apps that are not updated can be hidden from new users or blocked from publishing updates. A small yearly maintenance plan keeps your app visible, secure and compatible with new phones.

Budgeting for your app? Read our app development cost guide. Want a team that handles development and store publishing end-to-end? Talk to RelieveX Labs in Himatnagar – we have published apps on both stores for clients across Gujarat and India.