How to Publish a No-Code App to the App Store (Adalo, Bubble, Glide & FlutterFlow)
You built an app without writing code. The hard part is supposedly over — and then you open App Store Connect, or the Google Play Console, and hit a wall of screenshot specs, privacy questionnaires, data-safety forms, and metadata fields. This is where most no-code makers stall for weeks.
This guide walks the entire submission, start to finish, in the order you should actually do it. It applies whether you built your app in Adalo, Bubble, Glide, or FlutterFlow — the platform you built in changes how your app gets packaged, but the store requirements are the same for everyone.
Before you start: what publishing actually requires
There are two separate stores, each with its own account, its own review, and its own asset requirements. Apple's App Store is stricter and slower (a human reviews every app, usually in 24–48 hours). Google Play is faster but has tightened its own review considerably. You'll need the same core assets for both: a packaged app build, a set of screenshots at exact dimensions, a privacy policy hosted on a public URL, and a complete store listing.
Here's the sequence that avoids rework: get your developer accounts first, prepare your assets while your build compiles, then submit. Doing assets last is the classic mistake — you finish the app, feel done, and then discover you need eight perfectly-sized screenshots and a legal document before you can ship.
Step 1 — Get your developer accounts
For Apple, enroll in the Apple Developer Program. It costs 99 US dollars per year and enrollment can take a day or two to verify, so start it now. For Google, register for a Google Play Developer account — a one-time 25 US dollar fee, plus, for newer personal accounts, a testing requirement before you can publish publicly.
If you're on Adalo or FlutterFlow, these platforms can handle much of the build-and-upload step for you once your accounts exist. Bubble and Glide apps are typically wrapped (via their native offerings or a wrapper) before submission. Whichever route you're on, the accounts above are the non-negotiable prerequisite.
Step 2 — Create store-ready screenshots
Screenshots are the single biggest lever on your download rate — they're the first thing a potential user sees, and most no-code apps get them wrong by uploading raw, unframed phone captures. The stores also enforce exact pixel dimensions and will reject anything that doesn't match.
For the Apple App Store in 2026, the primary required size is 1320 × 2868 (the 6.9-inch iPhone). It's wise to also provide 1290 × 2796 (6.7-inch) for broad compatibility. For Google Play, phone screenshots should be 1080 × 1920. You'll want at least three per store, and ideally the full set, each with a short caption that sells one benefit.
This is exactly the problem Adalo Studio was built to solve. You paste your app's live share link, capture any screen in one click (or drag in screenshots you already have — no app URL required, which is how Bubble, Glide, and FlutterFlow makers use it), then drop them into one of eight templates and export PNGs at the precise store dimensions. No Figma, no Photoshop, no designer.
Step 3 — Write a privacy policy and answer the data-safety questions
Both stores require a privacy policy hosted at a public URL, and both now require you to declare what data your app collects and how it's used — Apple through the App Privacy section (the "nutrition label"), Google through the Data Safety form.
Do not skip or guess here. Mismatches between what your policy says, what your data-safety answers claim, and what your app actually does are a common rejection and, worse, a compliance risk. If your no-code app uses authentication, analytics, or any third-party integration, it almost certainly collects data you need to declare.
Adalo Studio generates a ready-to-publish Privacy Policy and Terms of Service from a few questions, plus pre-filled App Store and Google Play data-safety answers you can copy field by field — which removes the most tedious and error-prone part of this step.
Step 4 — Fill in your store listing (this is ASO)
Your listing is your app's storefront and its search-ranking surface — this is App Store Optimization (ASO). You'll need an app name, a subtitle or short description, a longer description, and a keyword set. Write the name and subtitle for humans and for search: lead with what the app does, not clever branding. Front-load your most important keyword.
Each store has its own fields and character limits — App Store Connect and Google Play Console ask for slightly different things (Apple has a dedicated keyword field; Google folds keywords into the description). Adalo Studio pre-fills all of these — app name, subtitle, keywords, long and short descriptions, age rating, and a submission checklist — so you're editing generated copy rather than staring at a blank form.
Step 5 — Submit, and survive review
Upload your build, attach your screenshots, paste your listing and privacy answers, set your age rating and pricing, and submit. Apple's review typically lands within a day or two; Google's can be similar for established accounts and longer for brand-new ones.
The mistakes that get no-code apps rejected
A few rejection reasons come up again and again, and nearly all are avoidable. Screenshots that don't match the required dimensions, or that show placeholder or "lorem ipsum" content, get bounced immediately. A privacy policy that's missing, unreachable, or contradicts your data-safety answers is one of the most frequent rejections. Apple's "minimum functionality" guideline (4.2) catches apps that feel too thin or too much like a repackaged website — make sure your app does something genuinely app-like. And broken links, login credentials the reviewer can't use, or incomplete metadata will stall you. Give Apple a working demo account if your app is gated.
A realistic timeline
If your accounts are already approved and your assets are ready, you can submit to both stores in an afternoon. The parts that eat time are the ones this guide front-loads: account verification (days), and asset creation (screenshots, policy, listing) if you're doing it by hand. Tooling that generates the assets — screenshots at exact sizes, a compliant policy, and pre-filled listing fields — collapses that from a weekend into about an hour, which is the whole reason Adalo Studio exists.
Build wherever you like. When it's time to publish, get your accounts started today, prepare your assets before you need them, and treat the privacy and screenshot requirements as first-class work rather than an afterthought — that's the difference between shipping this week and stalling for a month.