Publishing a FlutterFlow app takes about a week: set up developer accounts in your name, prepare the listing assets, generate signed iOS and Android builds, then submit. Apple review usually takes one to three days and Google Play a few hours to a day. The build being finished is not the finish line. The store process has its own checklist, and missing one item stalls the whole submission.
Step 1: Developer accounts
You need two, both in your name, not an agency's:
- Apple Developer Program, $99 a year. Enrolment can take a day or two, and a company enrolment needs a D-U-N-S number, so start this early.
- Google Play Console, a one-off $25. Newer developer accounts sometimes face additional identity checks and a testing requirement before the first public release.
If someone else sets these up, get them transferred to you before launch. Your app should not live in another company's store account.
Step 2: Store listing assets
Both stores need:
- App icon at the required sizes
- Screenshots for the device sizes each store asks for, showing real screens, not marketing mockups
- Title, subtitle, description and keywords
- A privacy policy URL that actually loads
- Category and content rating
Apple additionally needs a privacy nutrition label: a form describing every type of data the app collects and why. Google has an equivalent Data safety section. Fill these in honestly. Mismatches between what you declare and what the app does are a common rejection reason.
Step 3: Signed builds
From FlutterFlow you generate:
- An iOS build with the correct bundle identifier, signing certificate and provisioning profile, uploaded to App Store Connect
- An Android build as a signed app bundle, uploaded to Play Console
Each platform has its own signing setup. Getting the identifiers and certificates right the first time avoids a frustrating loop of failed uploads.
Step 4: Submit and respond to review
Once the build is uploaded and the listing is complete, you submit.
- Apple reviews manually. One to three days is typical. If your app has a login, provide a working demo account in the review notes, or it will be rejected for being incomplete.
- Google is mostly automated for a new app and usually clears in hours to a day, though a new developer account can take longer.
If Apple rejects, they tell you why. Most first-time rejections are small: a missing privacy disclosure, a demo account not provided, a screenshot that does not match the app. Fix and resubmit.
Step 5: Live, then updates
Once approved, the app is live. Future updates go through the same review, though repeat submissions are usually faster. Keep the signing keys safe: losing the Android signing key means you cannot update the app under the same listing.
What we do
At MarkLogix, FlutterFlow builds include store setup: we create both accounts in your name, prepare the listings, generate the signed builds, complete the questionnaires and manage the review process to approval, Apple review notes included. If you have a finished or nearly finished FlutterFlow app that needs to reach the stores, tell us where it is and we will scope the launch, or start a project for the full build.