The short answer: To publish a no-code app, you need an Apple Developer account ($99/year) and a Google Play Console account ($25 one-time), store listing assets, a hosted privacy policy, and a completed binary. Most first-time rejections are caused by missing privacy policy links, incomplete metadata, or locked demo credentials — not the app itself.
Publishing a no-code app to the App Store and Google Play means completing five things in sequence: creating developer accounts, assembling store assets, writing a privacy policy, submitting a working binary, and clearing review. Most first-time rejections have nothing to do with the app’s code — they’re caused by a missing privacy policy link, broken demo credentials, or an incomplete metadata field in the listing.
Here’s where no-code platforms change the equation: a good one handles the build, the binary packaging, and the submission mechanics. What you still own is the store accounts, the listing copy, the screenshots, and the privacy policy. Nobody can create those on your behalf without your Apple ID or Google account. Plan for roughly 1–3 hours of setup work on your side before the platform touches anything.
What do you need before you start?
Before you open a single submission form, have these ready:
- A finished, fully tested version of your app
- An Apple Developer Program membership ($99/year) and a Google Play Console account ($25 one-time registration fee)
- A publicly accessible privacy policy URL
- Screenshots sized to each store’s current specifications
- An app icon at 1024×1024 px (App Store) and 512×512 px (Google Play)
- A working set of demo login credentials if your app requires a sign-in to use
If your no-code platform handles submission for you — as Buildfire does — you’ll also need to add that platform as a team member on your Apple Developer account and authorize it to manage your app on the Play Console. Do this before anything else; approval of that access sometimes takes a business day.
Step 1: Create your developer accounts
Developer accounts are the prerequisite everything else depends on. You need both if you’re shipping to both platforms — there’s no shortcut.
Apple Developer Program
Go to developer.apple.com/programs and enroll. Individual accounts require an Apple ID tied to your legal name. Business accounts require a D-U-N-S number, which is free to obtain through Dun & Bradstreet but can take up to 5 business days to process if you don’t already have one. The annual membership fee is $99. Apple processes enrollment within 24–48 hours once your payment clears.
Done state: you can log into App Store Connect at appstoreconnect.apple.com and see the “My Apps” dashboard.
Google Play Console
Go to play.google.com/console and sign in with a Google account. The one-time registration fee is $25. Account setup is usually approved within 48 hours, though Google has been extending new developer review periods in 2025 and 2026 for fraud prevention — plan for up to 7 days if your account is brand new.
Done state: you can access the Google Play Console and see “Create app” in the top right.
Step 2: Set up your store listings
The store listing is the page a user sees before they download. Both stores require you to fill it out before you can submit a binary for review.
What both stores require
| Field | App Store | Google Play |
|---|---|---|
| App name | Up to 30 characters | Up to 30 characters |
| Short description / subtitle | 30 characters (subtitle) | 80 characters |
| Full description | 4,000 characters | 4,000 characters |
| App icon | 1024×1024 px, PNG, no alpha | 512×512 px, PNG or JPEG |
| Screenshots | At least 1 per device type | At least 2 phone screenshots |
| Privacy policy URL | Required for all apps | Required for all apps |
| Category | Primary + optional secondary | Application category required |
| Age rating / content rating | Set during submission | Complete the rating questionnaire |
Screenshots are the most underestimated asset. Both stores accept device-framed or frameless images; the App Store requires separate screenshot sets for different screen sizes (6.7″ and 6.5″ are the two most commonly required as of 2026). Use real screens from your app, not generic marketing images — reviewers check, and users convert better when they see the actual interface.
Done state: both store listings show no red validation errors and your privacy policy URL returns a 200 response when you paste it into a browser.
Step 3: Write and host your privacy policy
A privacy policy is not optional on either platform. Apple requires it for any app that collects any personal data or is targeted to users under 13. Google requires it for any app that accesses sensitive permissions or personal data — which in practice covers almost every app, because push notifications and user accounts both count.
Your privacy policy must be hosted at a stable public URL — not a Google Doc link, not a PDF behind a login. It needs to disclose: what data you collect, how you use it, whether you share it with third parties, and how users can request deletion.
If your no-code platform collects analytics or sends push notifications on your behalf, your privacy policy must disclose that too. The platform can tell you exactly what data it processes so you can list it accurately.
Services like Termly, iubenda, or a one-page policy written by your attorney all work. The content matters more than the format.
Done state: your privacy policy is live at a public URL, lists all data your app touches, and you’ve pasted that URL into both store listings.
Step 4: Complete Apple’s App Privacy disclosures (App Store only)
Apple requires you to complete a “Privacy Nutrition Label” in App Store Connect before submission. This is separate from your privacy policy URL. You self-report which data types your app collects (name, email, location, device ID, etc.) and declare whether each is linked to the user’s identity and used for tracking.
Answer based on what the app actually does, including what your no-code platform does on your behalf. If your platform collects crash analytics or device identifiers, declare them. Mismatches between your declared labels and what the app actually does are a common rejection trigger starting in 2021 and still the top policy-related rejection reason Apple cites in developer communications.
Done state: the “App Privacy” section in App Store Connect shows a completed questionnaire with no blank required fields.
Step 5: Build and upload your binary
The “binary” is the compiled app file — an .ipa for iOS and an .aab (Android App Bundle) for Google Play. This is the step where no-code platforms do the heaviest lifting.
If your platform submits for you
With a platform like Buildfire, you trigger the build from the control panel and the platform generates the binary, signs it with your certificates, and uploads it directly to App Store Connect or the Play Console. You still need to have granted the platform access to your accounts (Step 1). You then go into the store consoles to complete any metadata fields the platform can’t fill on your behalf and click submit.
If you’re uploading manually
For iOS: download Transporter (free on the Mac App Store) or use Xcode’s Organizer to upload your .ipa to App Store Connect. For Android: log into the Play Console, go to your app’s “Release” section, create a new release in the production track, and upload the .aab file.
Done state: App Store Connect shows your build in “Processing” or “Ready to Submit.” The Play Console shows your release in “Review” or listed as the current production release.
Step 6: Submit for review
Once the binary is uploaded and all listing fields are complete, you submit for review.
In App Store Connect: go to your app version, confirm all fields, and click “Submit for Review.” You’ll be asked whether your app uses the Advertising Identifier (IDFA) — answer accurately. Review times as of mid-2026 average 24–48 hours for most submissions, though complex apps or first-time accounts sometimes take longer.
In the Play Console: go to “Production,” confirm your release, and click “Send X changes for review.” Google’s review times average 3–7 days for a first release on a new account, and typically 1–3 days for updates on established accounts.
If your app requires a user account to function, fill in the “App Review Information” / “Review credentials” section with a working demo username and password. Missing demo credentials are one of the most common causes of rejection on both platforms — reviewers can’t test an app they can’t log into.
Done state: both stores show your submission status as “In Review.”
What are the most common rejection reasons — and how do you fix them?
Most first-time rejections fall into a short list of fixable problems. None of them require rebuilding the app.
| Rejection reason | Which store | Fix |
|---|---|---|
| Missing or broken privacy policy URL | Both | Confirm the URL is public, not behind a login, and returns a live page |
| No demo credentials for login-required app | Both | Add a working test account to the review notes section |
| Privacy Nutrition Label mismatch | App Store | Update your declared data types to match what the app and platform actually collect |
| Incomplete or inaccurate metadata | Both | Review every required field; description must accurately describe the app’s actual functionality |
| App crashes or has major bugs during review | Both | Test the specific device/OS configuration reviewers use (iPhone with latest iOS, Pixel with latest Android) |
| Content rating mismatch | Google Play | Re-complete the content rating questionnaire accurately |
| Guideline 4.0 — Design (minimal functionality) | App Store | Ensure the app offers meaningful functionality beyond a website wrapper; add at least one native feature |
If you’re rejected, Apple sends a resolution center message and Google sends an email with the specific policy violation cited. Read it literally — the fix is almost always in the first sentence. Respond with what you changed, not with an argument about the policy.
What happens after your app is approved?
Approval is the start, not the finish. Once your app is live, the work shifts to visibility and retention.
App Store Optimization (ASO) — the keywords in your title, subtitle, and keyword field on iOS, and your title and description on Android — directly affects how often your app appears in store search results. Most no-code apps leave this completely unoptimized at launch. Spending two hours on keyword research before you submit is easier than trying to improve ranking from zero downloads.
Push notifications are typically the highest-ROI channel for bringing users back after install. Buildfire includes push notifications, segmentation, and automatic re-engagement in every app, so you can start re-engagement campaigns on day one rather than building the infrastructure after the fact.
Tracking what users do inside the app tells you which features are driving sessions and which are dead weight. Buildfire’s built-in app analytics give you the data to make those calls without guessing.
And if your goal is to build a community, recurring revenue, or loyalty program around your app, those features are worth configuring before launch too — your first users are the easiest to onboard into a habit. A loyalty plugin built into the app from day one converts better than one bolted on six months later.
If the submission process above looks like more than you want to manage, Buildfire’s publishing team handles it — store account setup, submission, and resubmission if something comes back rejected. That’s what the App Store Publishing Service looks like in practice.
Frequently asked questions
How much does it cost to publish an app to the App Store and Google Play?
Publishing to the App Store requires an Apple Developer Program membership at $99 per year. Publishing to Google Play requires a one-time Google Play Console registration fee of $25. These are the only mandatory publishing fees — neither store takes a cut of app downloads unless your app sells in-app purchases or subscriptions, in which case store commission rates apply.
How long does app review take on the App Store vs. Google Play?
App Store review times average 24–48 hours for most submissions as of mid-2026, though first-time accounts or apps with complex functionality can take longer. Google Play’s review process averages 3–7 days for a first release on a new developer account, and typically 1–3 days for updates on established accounts. Neither timeline is guaranteed.
Do I need a privacy policy to publish a no-code app?
Yes. Both Apple and Google require a publicly accessible privacy policy URL for virtually any app — and any no-code app that uses push notifications, user accounts, or analytics will trigger this requirement. The policy must accurately describe what data the app collects, how it’s used, and how users can request deletion.
What does a no-code platform handle in the submission process, and what do I still own?
A no-code platform typically handles building the binary, signing it with the right certificates, and uploading it to the store consoles. What you still own: the developer accounts (both require your personal or business credentials), the store listing copy and screenshots, the privacy policy, and the final submit action. No one can create an Apple Developer account or Google Play Console account on your behalf.
Why do apps get rejected after using a no-code builder?
The most common rejection reasons are not related to no-code tools at all: a missing or broken privacy policy link, no demo credentials provided for a login-required app, an App Store Privacy Nutrition Label that doesn’t match what the app actually collects, or a description that doesn’t accurately reflect the app’s functionality. These are listing and metadata problems, not build problems — and they’re all fixable without touching the app itself.
Can I publish to both the App Store and Google Play at the same time?
You can submit to both stores simultaneously, but the review timelines differ — Google Play typically takes longer for a first release. It’s common to receive App Store approval first. Both submissions require separate accounts, separate binaries, and separate listing assets, even if the underlying app is the same.
What screenshots do I need to publish an app to the App Store?
The App Store requires screenshots for specific device screen sizes. As of 2026, the 6.7-inch (iPhone 15 Pro Max) and 6.5-inch (iPhone 14 Plus) sizes are the most commonly required, and screenshots from those sizes populate other device sizes automatically. You’ll also need iPad screenshots if your app supports iPadOS. Google Play requires at least 2 phone screenshots with no maximum dimension requirements beyond file size limits.