# How to Publish an App on App Store and Google Play Yourself > Publish an app yourself: the exact App Store Connect and Play Console steps, Google's closed-test rule, the web-link route, and where solo publishing stops. _Source: https://professionalstoolkit.com/articles/how-to-publish-an-app — The Professional's Toolkit · updated November 2026_ _Part of: [Make an app without writing code](https://professionalstoolkit.com/solutions/make-an-app-without-coding) — the guide, the do-it-yourself version and the tools that do it_ --- To publish an app on App Store and Google Play without a developer, you need a finished native build of the app, your own developer account with each store, a complete store listing, and a pass through each store's review. Apple's route runs through App Store Connect and a paid Apple Developer Program membership. Google's runs through Play Console after a one-time registration fee. If your app is really a web app, you may not need a store at all. **12 testers, 14 days** — The closed test new personal Google Play accounts must run before Production opens - **3 routes** — Web link, App Store, Google Play - **2 clicks** — Add for Review, then Submit for Review in App Store Connect - **Nov 13, 2023** — Google Play personal accounts opened after this date face the test rule ## First, decide whether you need a store at all Plenty of first apps never belong in a store. An internal tool, a booking page or a client portal works as a web link that people open on any phone. If you have not scoped the first version yet, start with [how to make an app](/articles/how-to-make-an-app) and come back once you know what you are shipping. Stores make sense when strangers must find you there, when you need device features a browser cannot reach, or when buyers expect an icon from Apple or Google. The web route is fast and skips the stores. You publish the app at a URL and send the link. On an iPhone, the visitor opens the link in Safari, taps Share, chooses Add to Home Screen, turns on Open as Web App, and taps Add. Apple says the icon then opens the site just like an app, and the web app can send notifications [1]. On Android, the browser menu offers a similar add or install option. **No review, no developer account, and every update reaches everyone at once.** > 💡 **Ship the web link first:** Publish the app at a URL and let early users add it to their home screen. You learn what people use before you spend weeks on store builds and reviews. ## What you need before either store will take your app A store does not accept a link. It accepts a compiled build: for iPhone, an iOS build uploaded to App Store Connect; for Android, an Android App Bundle uploaded to Play Console. A website, a chat canvas or a design file is not that. Something has to turn your app into a signed native package first, and that step is where most solo builders stall. Then come the accounts. Apple requires a paid Apple Developer Program membership. Google charges a one-time registration fee for a Play Console account. Each store also wants a listing: name, description, screenshots, a privacy policy, and contact details. Prepare these before you start the forms. Plan for the reviewer too. Someone at Apple or Google will open your app cold. If it needs a sign-in, give them a working demo account and short notes. If a screen is empty or still says placeholder text, expect a rejection. Treat the review like a stranger testing your app on day one, because that is exactly what it is. ### A quick readiness checklist 1. A native build file for each platform you target. 2. A developer account with Apple, Google, or both, in your own name or your company's. 3. A privacy policy page at a stable URL. 4. Screenshots and a short description for each listing. 5. A demo login for reviewers if the app has accounts. ## How to publish an app on App Store Connect, step by step Before you submit, Apple asks you to provide the required metadata and choose the build for the version. Only the Account Holder, an Admin or an App Manager can do the submission [2]. 1. **Have a build ready** in App Store Connect to choose for the version. 2. **Provide the required metadata** for the version. 3. In Apps, **select the app**, then click the app version you want to submit in the sidebar. 4. Scroll to the **Build section** and check that the right build is attached to the version. 5. Click **Add for Review** and choose an existing draft submission or a new one. The status changes to Ready for Review, but nothing has gone to Apple yet. 6. Click **Submit for Review**. When review starts, the status changes to In Review. The easy mistake is stopping at step 5. Ready for Review sounds final. It is not. Apple's own page says the submission is not sent until you click Submit for Review. After approval, the version can go live on the App Store. > ⚠ **Ready for Review is not submitted:** In App Store Connect, Add for Review only moves the version to Ready for Review. Nothing reaches Apple until you click Submit for Review. ## Publish an app on Google Play: closed test, then rollout Google adds one gate Apple does not have. If you opened a personal developer account after November 13, 2023, Production stays disabled until you run a closed test with at least 12 testers who stay opted in continuously for at least 14 days [3]. Only then can you apply for production access from the Dashboard, answering questions about your testing, your app and its readiness. Testers who drop out early do not count. Organization accounts and older personal accounts are outside this rule. Once production access is open, the release steps are short [4]: 1. Sign in to Play Console, select your app and go to Test and release, then Production. 2. Click **Create new release**. If the button is disabled, finish the setup tasks listed on your Dashboard. 3. On a first release, follow the prompts to configure **Play App Signing**. 4. Add your **app bundles**, give the release a name (only you see it) and enter release notes. 5. Click Save as draft, then Next to reach Preview and confirm. 6. If an Errors summary appears, open it and fix every error. You cannot publish until they are resolved. 7. Click **Start rollout to production**. On a first production release, this publishes the app to all Google Play users in the countries and regions you chose. Two details catch people later. Staged rollout percentages are not available on a first release, only on updates. And Google warns that once you publish to an open track, the signing key is fixed, so keep that key safe. ## The threshold where publishing it yourself stops working The forms are not the hard part. The build is. If your app lives as a website, a no-code page or a vibe-coded prototype in a chat window, nothing above helps until someone produces the iOS build and the Android App Bundle. That usually means native tooling, signing certificates and a computer set up for it. **For a non-developer working alone, this is where the homemade route breaks.** It keeps breaking after launch. Every change to the native shell means a new build and another trip through review. Testers have to be recruited and kept opted in for Google. Apple and Google each change their rules on their own schedule, and you are the developer of record for both. One person can do this once. Doing it monthly, across two stores, on top of the actual app is a different job. The web route has its own ceiling. A home-screen web app is not found in store search. It may not reach every device feature a native app can. If your buyers expect to download you from the App Store, a link will feel like a workaround. > 💡 **Recruit testers before you need them:** Google counts only testers who stay opted in continuously for 14 days. Line up more than 12 people so a few dropouts do not reset your timeline. ## Builders that handle the store build for you Some app builders close the gap between a working app and a store-ready package. They do it in different ways, and the difference matters for what you can sell and what you still do by hand. Bubble builds native iOS and Android apps and submits them [straight from the editor](/articles/bubble-mobile-app-builder). That removes the native tooling and the computer set up for it, the exact point where the section above says the homemade route breaks, for both stores at once. ### Bubble — both stores submitted from the editor Builds native iOS and Android apps on React Native from the same project as your web app, then builds and submits them to the stores from the editor, with no Mac or Xcode. Text, design and workflow changes go out without a new store review. - Where it stops: Native mobile is labeled beta (November 2026) and has no offline mode; you pay Apple and Google directly and are the developer of record. - Plan: A paid plan on the Mobile or Web & Mobile tab (Starter and up) - [Bubble's native app steps](https://professionalstoolkit.com/articles/bubble-mobile-app-builder) · [Bubble](https://professionalstoolkit.com/tools/bubble) Replit covers the Apple half of this guide: its Launch tool replaces the local build and sends the app through [TestFlight to App Store review](/articles/replit-mobile-apps). The Google half, closed test included, still has to happen some other way. ### Replit — the Apple half, built in the cloud The Agent builds an Expo mobile app next to your web app; the Launch tool compiles the iPhone build in the cloud and sends it to App Store Connect, TestFlight first, then App Store review. - Where it stops: Google Play publishing is not supported yet; you need your own Apple Developer Program membership, and the bundle ID is permanent after the first build. - [Replit's App Store steps](https://professionalstoolkit.com/articles/replit-mobile-apps) · [Replit](https://professionalstoolkit.com/tools/replit) Base44 takes a different path: it generates a [store-ready wrapper](/articles/base44-mobile-apps) around your published web app. That suits the reader from the first section whose app really is a web app, but whose buyers still expect an icon from Apple or Google. ### Base44 — store wrapper around your web app Generates signed store-ready files (IPA for iOS, AAB for Google Play) that wrap your published web app, plus a store readiness scan; you submit them through your own Apple and Google developer accounts. - Where it stops: A wrapper, not a fully native app; digital goods cannot be sold through in-app purchase. - Plan: Builder and up - [Base44's store wrapper explained](https://professionalstoolkit.com/articles/base44-mobile-apps) · [Base44](https://professionalstoolkit.com/tools/base44) Bolt.new also builds mobile apps with Expo, but the store submission happens outside Bolt, on your own computer and accounts. Lovable, Softr and Glide (both GlideOS and Glide Classic) produce no App Store or Google Play apps at all; they fit the web and home-screen route above. Our guide to choosing a [no-code app builder](/articles/no-code-app-builder) maps which builder covers data, sign-in, mobile and publishing. ## FAQ **How do I put an app on the App Store without a Mac?** Apple's submission happens in App Store Connect in a browser, but the iOS build itself has to come from somewhere. Builders such as Bubble and Replit compile the build for you, so you do not need a Mac or Xcode for that step. **Can I publish an app on Google Play with a personal account?** Yes. If the account was created after November 13, 2023, you first run a closed test with at least 12 testers opted in for 14 days in a row, then apply for production access from the Play Console Dashboard. **Do I need to resubmit to the stores for every update?** Changes to the native app need a new build and another review. Builders that push content and design changes over the air, such as Bubble, or that wrap a web app, such as Base44, avoid a new store build for many everyday edits. **Is a home-screen web app good enough instead of a store app?** For internal tools, client portals and early versions, often yes: no review, no developer account, and updates reach everyone at once. It will not appear in store search, so a consumer app that must be found there needs the store route. ## Submit for Review, a closed test, or a home-screen link With the pieces in hand, doing it yourself follows a clear process. You need a native build, a developer account with each store, a complete listing and a reviewer-ready version. Apple's path ends with Submit for Review in App Store Connect. Google's starts, for new personal accounts, with a closed test before Production opens. If you have no native build and no developer time, the web link and home-screen install skip store review and ship today. When you truly need the stores, a builder that produces the store build is usually the shorter road than learning native tooling alone. ## Sources [1] Apple Support — https://support.apple.com/guide/iphone/open-as-web-app-iphea86e5236/ios (Nov 2026) [2] Apple Developer — https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-app (Nov 2026) [3] Google Play Console Help — https://support.google.com/googleplay/android-developer/answer/14151465?hl=en (Nov 2026) [4] Google Play Console Help — https://support.google.com/googleplay/android-developer/answer/9859348?hl=en (Nov 2026)