Building the app is only half the work. Before customers can download it, your app has to pass review on Google Play and the Apple App Store, comply with their privacy and content rules, and present itself well enough that people actually tap "Install".
Launch problems are frustrating because they are rarely technical. A missing privacy disclosure, a reviewer who cannot log in or a vague permission request can delay a launch by days. This checklist helps you avoid those delays.
1. Accounts and ownership
Get this right first - it is the hardest thing to fix later.
- Google Play Console account created as an organisation, in your company's legal name
- Apple Developer Program account enrolled as an organisation (Apple requires a D-U-N-S number for organisations)
- Business details verified on both, with official contact email and phone
- Your agency or developers added as users with appropriate roles, not as account owners
- App signing keys and certificates stored securely, with you holding access
- Payment and payout profiles set up if you sell digital goods or subscriptions
Account verification can take time on both platforms, so start early. Google Play also has additional testing requirements for some newly created personal developer accounts before production access - check the current rules in Play Console when you create the account.
2. Privacy and data disclosures
Both stores ask you to declare exactly what data your app collects and why.
Google Play
- Complete the Data safety section - data collected, shared, purpose, encryption in transit and deletion options
- Declare use of sensitive permissions - location, contacts, SMS, call logs, camera and so on - and justify them where required
- Complete the content rating questionnaire and target audience section
Apple App Store
- Fill in App Privacy details ("privacy nutrition labels")
- Provide purpose strings that explain clearly why each permission is needed
- If the app tracks users across other companies' apps or websites, implement App Tracking Transparency
Both
- A privacy policy URL that accurately describes your practices
- An account deletion option inside the app and a way to request it from outside the app, if users can create accounts
- Third-party SDKs (analytics, ads, crash reporting, chat) declared - they collect data too
- Alignment with India's DPDP Act 2023: clear consent, purpose limitation and a way for users to raise data requests
3. Permissions
Ask for as little as possible, as late as possible.
| Permission | Good practice |
|---|---|
| Location | Ask only when the user opens a feature that needs it; prefer "while using the app" |
| Notifications | Explain the benefit before the system prompt appears |
| Camera and photos | Request at the moment of upload; use the system photo picker where available |
| Contacts | Avoid unless essential to the core feature |
| SMS and call logs | Heavily restricted on Google Play - use alternatives such as OTP auto-read APIs |
Unnecessary permissions are a common cause of rejections and also put off potential users at install time.
4. Quality and stability
Reviewers use your app. If it crashes or confuses them, it will be rejected.
- Test on several real Android devices, including low and mid-range phones, and on supported iPhone models
- Test on slow and unstable networks, and with the app opened from a fresh install
- Check every screen in both light and dark mode if you support both
- Confirm crash reporting and analytics are working
- Remove test data, placeholder text and "coming soon" buttons
- Make sure the app meets the stores' current target platform version requirements
5. Reviewer access
- Provide a demo account with login details in the review notes
- If login uses OTP, give reviewers a test number or bypass that works reliably
- Explain any feature that needs special hardware, a location or a specific account type
- If parts of the app are for registered businesses only, explain how reviewers can see them
6. Payments
- Physical goods and real-world services (food, retail, bookings, travel) can use your own payment gateway - UPI, cards and wallets through providers such as Razorpay
- Digital goods and subscriptions consumed inside the app generally fall under each store's in-app billing rules, with some regional and category-specific exceptions - confirm the current rules for your case before you build
- Test success, failure, pending and refund flows
7. Store listing
Your listing is your app's landing page. Prepare:
- App name - clear and specific; avoid keyword stuffing
- Short description (Google Play) and subtitle (App Store)
- Full description - what the app does, who it is for, key features, in plain language
- Screenshots for required device sizes, showing real screens with short captions
- App icon - simple and recognisable at small sizes
- Feature graphic (Google Play) and optional preview video
- Category, contact email, website and support URL
- Localised listings in Hindi or regional languages if your audience needs them
| Listing element | Common mistake | Better approach |
|---|---|---|
| Screenshots | Raw screens with no context | Captioned screens showing key benefits |
| Description | Long feature list | Benefit-led opening, then features |
| Name | Stuffed with keywords | Brand plus a short descriptor |
| Support details | Personal email | Business support email and website |
8. Testing tracks and staged rollout
- Use Google Play internal and closed testing and Apple TestFlight for team and beta testers
- Collect feedback and fix issues before production
- On Google Play, consider a staged rollout to a percentage of users first, then expand once crash rates look healthy
- On the App Store, consider phased release for automatic updates
9. Backend and launch readiness
- Production servers sized for launch traffic, with monitoring and alerts
- APIs secured - authentication, rate limiting and no sensitive data in responses that the app does not need. A pre-launch security review is worth it for apps handling payments or personal data
- Backups configured and tested
- Admin panel ready for your team, with real content and products loaded
- Push notification certificates and keys configured for production
10. Launch day and the first weeks
- Submit for review with enough buffer before any announced date
- Prepare announcement content - website banner, WhatsApp message to customers, social posts, email
- Add store badges and links on your website
- Monitor crashes, reviews and support messages daily
- Reply to reviews politely and fix reported issues quickly
- Plan your first update - real users always find something
Common rejection reasons and quick fixes
| Rejection reason | Typical fix |
|---|---|
| App crashes or shows errors during review | Test release builds on real devices; check crash reports before submitting |
| Reviewer cannot sign in | Provide working demo credentials and OTP instructions in review notes |
| Privacy details do not match app behaviour | Update the Data safety or App Privacy answers, including third-party SDKs |
| Permission requested without clear reason | Remove it, or explain it in the purpose text and request it only in context |
| No account deletion option | Add in-app deletion and a web request option |
| Placeholder or incomplete content | Remove test screens and "coming soon" features |
| Misleading screenshots or description | Show real screens and describe actual features |
| Digital purchases outside store billing | Review store payment rules for your category and region |
Read the rejection message carefully, fix the specific issue and reply to the reviewer with a short explanation of what changed. Polite, precise responses usually lead to faster approvals.
After the first release: keep the listing alive
Store listings are not set-and-forget. Refresh screenshots when the design changes, update the description when you add important features, write clear release notes for each update, and keep an eye on reviews for recurring complaints that point to bugs or confusing flows.
Key takeaways
- Create store accounts as an organisation in your company's name and start verification early.
- Complete Data safety and App Privacy details accurately, with a matching privacy policy and account deletion.
- Ask for minimal permissions at the moment they are needed.
- Give reviewers a working demo login and clear notes.
- Treat the store listing as a landing page and use staged rollouts.
- Monitor closely after launch and ship a quick first update.
Need help getting your app live?
From store account set-up to listings, compliance and post-launch support, our team in Jaipur handles the full launch process. Book a free consultation or explore our mobile app development and UI/UX design services. You will get a clear plan and written quote before work begins.
