To publish an app: create developer accounts (Google Play Console, with a one-time fee; Apple Developer Program, with a yearly fee), prepare store listings (icon, screenshots, description, privacy policy, data-safety details), upload a signed build, pass review and release. Plan 1–2 weeks for verification and reviews, and always publish under your own accounts.
Step 1: Create developer accounts (under your business)
| Store | Account | Fee (approx., Sept 2026) | Notes |
|---|---|---|---|
| Google Play | Play Console | One-time registration | Organisation accounts need verification (for example a D-U-N-S number) |
| Apple App Store | Apple Developer Program | About ₹8,200/yr in India | Organisation enrolment needs a D-U-N-S number and legal entity details |
Start early. Organisation verification can take days.
Step 2: Prepare store listing assets
- App name and a short description
- Full description: benefits first, features next, keywords used naturally
- Icon: simple and recognisable at small sizes
- Screenshots: phone (and tablet if supported); show the core value in the first two
- Feature graphic (Play Store)
- Privacy policy URL: required
- Support contact: email and website
- Category and content rating questionnaire
Step 3: Privacy and data declarations
- Google Play Data safety form: what data you collect, why, and whether it's shared
- Apple privacy "nutrition labels": similar disclosures
- Permissions: request only what you need, with clear explanations in the app
- Account deletion: apps with account creation must offer a way to delete the account
Step 4: Build and upload
- Android: upload a signed Android App Bundle to Play Console; use internal and closed testing tracks first
- iOS: archive and upload via Xcode or CI; test via TestFlight
- Increment version numbers for every release
Step 5: Review, and common rejection reasons
Apple (stricter):
- Crashes or broken features
- Placeholder content
- Missing demo login for reviewers
- Unclear purpose or minimal functionality
- In-app purchase rules not followed for digital goods
Google Play:
- Policy violations in the listing or content
- Incorrect data-safety declarations
- Permission misuse
- Required testing or track rules for new developer accounts
Step 6: Launch smart
- Staged rollout on Play Store (for example 10% → 50% → 100%)
- Phased release on App Store
- Monitor crashes and reviews in the first week
- App Store Optimisation (ASO): iterate on screenshots and description
Post-launch checklist
- Crash reporting and analytics connected
- Reply to reviews (especially negative ones)
- Plan regular updates for OS changes
- Promote: website banner, WhatsApp broadcast to opted-in customers, social media
How does RapBooster help?
RapBooster's app development tiers (Starter from ₹1,50,000, Professional from ₹5,00,000, Enterprise from ₹15,00,000; excl. GST) include store submission support under your accounts, with 100% source code ownership. See app development cost.
App Store Optimisation (ASO) basics
Getting approved is step one; getting found is step two.
- Title and subtitle: include your brand plus a key benefit ("Glow: Skincare Shopping")
- Keywords: research what users search for, and use them naturally in the description and (on iOS) the keyword field
- First two screenshots: show the core value immediately, with short captions
- Preview video: a 15–30 second demo of the main flow
- Ratings and reviews: prompt happy users in-app at the right moment (after a successful order, not at first launch)
- Localisation: Hindi or regional listings for Indian audiences, Arabic for GCC markets
Timeline planning
| Task | Typical time |
|---|---|
| Developer account setup and verification | Several days to 2 weeks |
| Store listing assets | 2–3 days |
| Internal testing (TestFlight, internal track) | 1 week |
| Closed testing for new Play accounts (where required) | Plan extra time |
| Store review | Hours to a few days |
| Staged rollout | 1–2 weeks |
Start the accounts on day one of development, not the week before launch.
Common publishing mistakes
- Publishing under the agency's account (you lose control)
- Forgetting a demo login for reviewers
- Placeholder text or broken links in the app
- A privacy policy that doesn't match the app's actual data use
- Requesting permissions the app doesn't need
- No crash reporting at launch
Keeping your app healthy after launch
- Update for new OS versions each year
- Keep libraries and SDKs current (stores enforce minimum target versions)
- Respond to reviews and fix recurring complaints
- Track crash-free sessions and fix top crashes first
The bottom line
Publishing is mostly preparation: accounts, assets, privacy declarations and a stable build. Start verification early, give reviewers what they need, roll out gradually and keep improving after launch.




