The complete beginner's guide to publishing a mobile app to the App Store and Google Play. Covers developer accounts, code signing, store listings, compliance, and submission — with tips to avoid the most common rejection reasons.
Quick Answer: Publishing a mobile app requires five things: (1) a developer account on Apple or Google, (2) a correctly signed and packaged build, (3) a store listing with metadata and screenshots, (4) a privacy policy and permission declarations, and (5) submission for review. Each step has specific requirements that trip up first-time publishers. This guide covers all of them.
You've built your app. Now you need to get it into the hands of real users — which means navigating Apple's App Store Connect or Google's Play Console, or both. If you've never done this before, the process is more involved than most people expect.
This guide covers every step in plain language, with no assumptions about your technical background.
What You Need Before You Start
- A completed, testable mobile app (built with any tool)
- An Apple Developer account ($99/year) for App Store publishing
- A Google Play Developer account ($25 one-time fee) for Play Store publishing
- A privacy policy hosted at a publicly accessible URL
- App screenshots in the correct dimensions for each device type
- An app icon: 1024×1024 px for iOS, 512×512 px for Android
The Full Process at a Glance
- Set up your developer account
- Prepare and sign your app build — iOS: certificate + provisioning profile / Android: keystore file
- Create your store listing — title, description, screenshots, icon
- Complete compliance declarations — permissions, data safety, age rating
- Upload your build
- Submit for review
- Handle the outcome — Approved → app goes live / Rejected → fix the issue, resubmit
Step 1: Set Up Your Developer Account
For the App Store, go to developer.apple.com and enroll in the Apple Developer Program. The annual fee is $99. You'll need a valid Apple ID, personal or business information, and a payment method. Approval usually takes 24–48 hours.
For Google Play, go to play.google.com/console and sign up with a Google account. The one-time registration fee is $25. Access is typically granted within minutes.
Step 2: Prepare and Sign Your Build
This step is more complex on iOS than Android. Here's what each platform requires:
| iOS (App Store) | Android (Google Play) | |
|---|---|---|
| Build format | .ipa file | .aab (Android App Bundle) |
| Signing requirement | Distribution certificate + provisioning profile | Keystore file |
| Where configured | Apple Developer Portal + Xcode | Android Studio or build tool |
| Most common mistake | Wrong certificate type or expired provisioning profile | Losing the keystore file — makes future updates impossible |
The iOS code-signing process is where most first-time publishers get stuck. It involves three separate elements — an App ID, a distribution certificate, and a provisioning profile — that must all match correctly. Getting any one wrong causes the build to fail.
Step 3: Create Your Store Listing
Your store listing is what users see when they find your app. It directly affects discoverability and conversion. Here's what to prepare:
- App name: Up to 30 characters (iOS) or 50 characters (Android). Include your primary keyword.
- Subtitle / Short description: 30 characters (iOS) or 80 characters (Android). The second most important field for search.
- Full description: Up to 4,000 characters. Write for humans first, include key terms naturally.
- Keywords (iOS only): A separate 100-character field that affects search ranking but doesn't appear publicly.
- Screenshots: Required for every supported device size. These are your strongest conversion tool.
- App icon: 1024×1024 PNG with no transparency (iOS); 512×512 PNG (Android).
Step 4: Complete Compliance Declarations
Both platforms require you to answer compliance questions before submission. This is where many apps get rejected. You need to:
- Declare every permission your app uses and explain why (camera, location, contacts, etc.)
- Complete the Data Safety form (Google) or Privacy Nutrition Label (Apple)
- Set your age rating by answering a content questionnaire
- Declare whether your app contains ads, in-app purchases, or subscriptions
- Provide a valid, accessible privacy policy URL
Critical Warning: Your permission declarations must exactly match the permissions your app actually requests in its code. If your app asks for camera access but you haven't explained why in your data safety form, Google will flag it for policy violation. This is one of the most common rejection reasons for AI-generated and no-code apps.
Step 5: Upload Your Build
For iOS, upload your .ipa file using Xcode or Apple's Transporter app. The build processes in App Store Connect — this takes 15–30 minutes. You then select that build for your submission.
For Android, upload your .aab file directly through Play Console. Google recommends the App Bundle format over the older .apk because it optimizes download size per device.
Step 6: Submit for Review
Before submitting, run through a final check: every required field is complete, your screenshots are the right dimensions, and your build passes the platform's pre-submission checks. Missing even one required field prevents submission entirely.
Apple's review typically takes 1–3 business days for first submissions. Google Play is usually faster — often a few hours to one business day.
Step 7: Handle the Review Outcome
If approved: your app goes live at the scheduled time. Share the link, announce it, and celebrate.
If rejected: read the rejection reason before doing anything else. Apple and Google provide a specific rejection code and explanation. Don't resubmit immediately with the same build — understand and fix the issue first, or you'll likely be rejected again.
Common Rejection Reasons and How to Avoid Them
| Rejection Reason | How to Avoid |
|---|---|
| App crashes or has major bugs | Test on a real physical device before submitting — not just a simulator |
| Missing or broken privacy policy | Host a valid, accessible privacy policy before you start the submission |
| Misleading metadata | Screenshots and description must accurately match the current app UI |
| Incomplete permission justification | Clearly explain every permission in your data safety / privacy label |
| Placeholder or test content in app | Remove all test data, debug logs, and placeholder screens before submitting |
| UI doesn't follow platform guidelines | Review Apple's HIG and Google's Material Design guidelines before final build |
How Froxi AI Makes This Easier
Every step above has sub-steps, edge cases, and gotchas this guide can't fully cover in a single article. Froxi AI fills that gap with a personalized publishing guide built for your specific app. Answer a few questions about your platform, app type, permissions, and region — and Froxi AI generates a precise, step-by-step path through the entire process.
The on-page AI assistant answers questions in context. If you're on the code-signing step and don't understand what a provisioning profile is, you get an explanation that's relevant to what you're doing right now — not a generic definition. And if your app gets rejected, the Rejection Resolver tells you exactly what to fix.
Froxi AI's guarantee: if your app doesn't go live, you get a full refund.
