How to Publish Your App on the App Store and Google Play

To publish an app on the App Store and Google Play, you enroll in the Apple Developer Program and register a Google Play Console account, build release files (an IPA for iOS, an Android App Bundle for Android), and test them through TestFlight and Play's testing tracks. Then you fill in each store listing with screenshots, a description, a privacy policy link and the privacy questionnaires, and submit for review. Reviewers at Apple and Google check the app against their guidelines and either approve it, ask questions or reject it with a reason you can fix.

The code is rarely what slows beginners down. It's the accounts, the paperwork and the waiting. Here's the process in the order that wastes the least time, written for someone publishing from the Philippines.

What do you need before you can publish an app?

You need four things ready before you touch either console.

• A finished, small app. No placeholder text, no "coming soon" buttons, no screens that crash. Reviewers tap everything.
• Developer accounts on both platforms. Start these first, because identity verification can take days.
• A public privacy policy page. Both stores ask for a link, even if your app collects nothing.
• Store assets: a 1024 x 1024 icon with no transparency, screenshots with realistic data, a short and a full description, a support email, and for Google Play a feature graphic.

A bundle identifier (iOS) or package name (Android) is your app's permanent internal ID, usually written like a reversed domain: com.juandelacruz.hatian. Pick it carefully. Once you publish, changing it means publishing a brand new app with zero reviews.

If you haven't built the app yet, start with our guide on how to build your first mobile app as a beginner, then come back here.

How do you get Apple and Google developer accounts from the Philippines?

Both platforms charge a fee: Apple's Developer Program is a yearly membership and Google Play Console has a one-time registration fee. The amounts, accepted cards and verification steps change, so confirm everything on developer.apple.com and play.google.com/console before you pay. Don't trust the number in a two-year-old YouTube video.

A few things that trip up Filipino developers:

• Payment. You need a card that works for international online payments. A bank debit card with online transactions turned on, or a card linked to your e-wallet, usually works. Check the international setting first and keep enough balance for the fee plus your bank's conversion charges.
• Individual vs organization. If you don't have a registered business, enroll as an individual. On Apple, an individual account shows your legal name as the seller. Organization accounts on both platforms need a D-U-N-S number and extra verification, which takes longer.
• Your name must match your ID. Use your legal name exactly as it appears on your government ID. Nicknames and missing middle names cause verification delays.
• Google shows some details publicly. Your developer name and contact info may appear on your store listing. Read what becomes public before submitting.

Freelancers: publish client apps under the client's own developer account, not yours.

How to publish an app on the App Store, step by step

You don't strictly need a Mac anymore. If you build with Expo, EAS Build creates the iOS file in the cloud. If you build with Swift in Xcode, you do need a Mac. Here's the path with Expo, which is what most beginners use:

1. With your Apple Developer Program membership active, set the app name, version, icon, splash screen and ios.bundleIdentifier in app.json.
2. Install the EAS command line tool, log in, and run eas build --platform ios --profile production. Let EAS create your certificates and provisioning profile unless you have a reason not to.
3. Run eas submit --platform ios to upload the build to App Store Connect. If the app record doesn't exist yet, create it in App Store Connect with the same bundle identifier.
4. Open TestFlight in App Store Connect. Once processing finishes, answer the export compliance question honestly, add yourself as an internal tester and install the build from the TestFlight app on a real iPhone.
5. Test from a fresh install. Delete the app, reinstall, and use it like a stranger would.
6. Fill in the listing: screenshots, description, keywords, support URL, privacy policy URL, category and age rating.
7. Complete the App Privacy section. This is the "privacy nutrition label" shown on your store page, and your answers must match what the app and your privacy policy actually say.
8. Create a version, attach your build, click Add for Review, then submit.

TestFlight is Apple's beta testing app. Internal testers on your own team can install right away. Inviting external testers by email or public link needs a lighter beta review from Apple first.

How to publish an app on Google Play, step by step

Google Play's flow has one step that surprises almost everyone: newer personal developer accounts must run a closed test with a minimum number of testers, who stay opted in for a minimum number of days, before Google grants access to production. Google has changed these numbers before, so read the current requirement on your Play Console dashboard. Start this early.

1. In Play Console, create your app: store name, default language, app or game, and free or paid. A free app can't later be switched to paid.
2. Build an Android App Bundle (AAB). With Expo: eas build --platform android --profile production, and let EAS generate the upload key. Google's Play App Signing then manages the key that signs what users download.
3. Go to Testing, then Internal testing. Create a release and upload the AAB. For a brand new app, Google may require the first upload by hand in the console before automated uploads with eas submit work.
4. Add yourself as an internal tester, open the opt-in link on an Android phone and install from Play.
5. Complete the App content section: privacy policy URL, ads declaration, content rating questionnaire, target audience, the Data safety form, and app access (login details for reviewers if your app needs sign-in).
6. Set up the main store listing: short description, full description, icon, feature graphic and phone screenshots.
7. Create a closed testing release and recruit testers who have Android phones: family, classmates, friends from your org. Swapping testing with other beginners works well.
8. When your test meets the requirement, apply for production access and answer Google's questions about your testing.
9. Create a production release and send it for review.

Google also requires apps to target a recent Android API level. Expo SDK updates usually handle this, but check Play Console's warnings before every upload.

Why do apps get rejected, and what should you do?

Rejection is normal, even for experienced developers. Common reasons for a first app:

• Crashes or broken buttons on a device you didn't test.
• Placeholder content: lorem ipsum, "test test" items, empty screens.
• A privacy policy link that doesn't load, or one that describes data the app doesn't collect (or misses data it does).
• A login with no demo account for reviewers. Also, if your app lets people create an account, Apple requires a way to delete that account inside the app.
• Misleading metadata: screenshots of features that don't exist, or brand names stuffed into the title.
• Too little functionality, like a website wrapped in an app with nothing extra.

When it happens, read the whole message. Apple cites a guideline number you can look up in the App Review Guidelines. Fix the actual issue, then reply briefly in App Store Connect (or follow the steps in your Play Console inbox): what you changed and where to find it. Don't argue, and don't resubmit the same build hoping for a nicer reviewer.

Doing all of this alone is completely possible. The cost is usually one or two extra review cycles from things you couldn't see in your own work. In the App Builder Track, your week 3 assignment is a full store listing kit (icon, screenshots, descriptions, privacy policy, bundle ID), and a coach marks up anything a reviewer would likely flag before you build. You can see how it's laid out in the free App Builder preview lessons.

How do you update an app after it's published?

There are two ways, and picking the wrong one causes trouble. If you only changed JavaScript, text, styles or images in an Expo app, you can push an over-the-air update with EAS Update, and users get it the next time they open the app. If you added a native package (camera, notifications), changed the icon or permissions, or upgraded your Expo SDK, you need a new store build and a new review.

Every upload also needs a higher internal build number than the last one (buildNumber on iOS, versionCode on Android). EAS can auto-increment these for you.

Is publishing worth it for your career?

Yes, if you're aiming for mobile or front-end roles. A recruiter who installs your app sees proof that you finish things and can pass someone else's quality bar. Put the store links under Projects on your resume and LinkedIn (our LinkedIn tips for IT jobs show where), and link the source in a clean repo, as covered in what recruiters check on your GitHub. If you want the full 4-week path from idea to both stores, the App Builder Track page shows what each week covers.

Frequently asked questions

Do I need a Mac to publish an iPhone app?

Not if you build with Expo or another tool that compiles iOS apps in the cloud, such as EAS Build. You do need a Mac if you build natively with Swift and Xcode. Either way, test on a real iPhone through TestFlight before submitting.

How much does it cost to publish an app on the App Store and Google Play?

Apple charges a yearly Developer Program membership and Google charges a one-time Play Console registration fee. The exact amounts change, so check developer.apple.com and play.google.com/console for current pricing before you pay.

How long does app review take?

It varies from hours to several days, and it depends on the platform, the app and the time of year. Google's closed testing requirement for newer personal accounts adds a waiting period of its own, so start testing as early as you can.

Do I need a privacy policy if my app doesn't collect any data?

Yes. Both stores ask for a privacy policy link, and it should honestly say what the app stores, where, and how users can delete it. A short, true policy hosted on Google Sites or GitHub Pages is better than a long copied template.

Why did Google Play ask me to run a closed test first?

Google requires newer personal developer accounts to run a closed test with a minimum number of opted-in testers for a set period before applying for production access. Check your Play Console dashboard for the current numbers, since Google has changed them before.