How do I move my FlutterFlow app to a developer without starting over?
Short answer: You do not have to start over. FlutterFlow, a visual builder that generates a Flutter mobile app (Flutter is Google's toolkit for building phone apps from one codebase), can hand your code to a developer through a code download or a push to GitHub. The big catch is that the link is one way: FlutterFlow's docs warn that changes made directly on its GitHub branch are overwritten by the next push. So decide first whether the developer works inside FlutterFlow or leaves it for good.
You built an app in FlutterFlow, it has reached the limit of what you can do in it, and you need a developer to take over without throwing the work away.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Handing over a FlutterFlow app goes well when you make one decision early: will the developer keep using FlutterFlow, or will the exported code become the main version? Everything else follows from that. This page explains the export, what a cleanup pass includes, how to think about cost, and what to ask any developer before you sign.
What you can export
FlutterFlow's pricing page lists code download on the Basic, Pro and Max plans, and not on the Free plan. As of November 2026 the page shows Basic at $39 a month ($29 a month billed yearly), Pro at $80 a month ($60 billed yearly) and Max at $150 a month ($113 billed yearly). Push to GitHub, which connects your project to a code repository (a shared store of code with full history), is listed for Pro and Max only. App store deployment from FlutterFlow is listed for Basic and up. Check the pricing page before you pay for a month just to export, since plans change.
So the minimum plan for a hand-off by code download is Basic, and for a clean repository your developer can work from, Pro. If you only need the files once, one month on a paid plan may be enough.
The one-way catch
FlutterFlow's push-to-GitHub guide says pushes land in a branch called flutterflow, and warns: avoid making direct changes to this branch, because your changes will be overwritten by the next push from FlutterFlow Studio. Their suggested pattern is to make custom changes on a separate branch (for example develop) created from flutterflow, and merge updates through pull requests.
In plain words: the documented pattern moves FlutterFlow's updates into the developer's branch by pull request, never the other way. That gives you two sensible ways to work, plus a third that costs more.
| Option | What it means | Pick it when |
|---|---|---|
| Stay in FlutterFlow, developer adds custom pieces | The developer works in the visual builder and adds custom code where FlutterFlow allows it | The app mostly works and you need a few things it cannot do |
| Leave FlutterFlow for good | Export once, then the code on GitHub is the only version. You stop editing in FlutterFlow | You are fighting the tool, need deep native features, or want full ownership |
| Run both (merge between branches) | The developer keeps merging FlutterFlow pushes into their own branch | Rare. It works but costs developer time on every merge. Avoid it unless you have a reason |
What the exported code looks like
It is a real Flutter project, so any Flutter developer can open it. It is also machine-written. Expect long files, generated names, and structure that follows FlutterFlow's way of working, not a hand-built design. That is not a defect. It does mean a developer will want an hour or two to read it before quoting, and you should let them.
What a cleanup pass includes
- Get it running on a clean machine. A fresh computer, no FlutterFlow, just the repository. If it will not build, you now know the real starting state.
- Move every account into your name. The Apple Developer account (Apple's program page lists $99 USD per membership year), the Google Play account, Firebase or Supabase, the domain, any payment or email service. If these are on a freelancer's account, you cannot move without them.
- Move secrets out of the code. API keys belong in environment settings, not pasted into files.
- Check the backend rules. Many FlutterFlow apps rely on Firebase or Supabase. Open the security rules. Apps built quickly can leave them wide open, so any user can read any record.
- Remove dead pages and unused packages. Prototype screens, test data and leftover libraries slow the build and confuse the next person.
- Add error handling and crash reporting. Without crash reporting you will not see failures that happen on users' phones, so a developer should add it.
- Set up repeatable builds. Flutter's own iOS release guide describes the steps: a Mac with Xcode, an enrolled Apple Developer account, a registered bundle ID, a unique build number for each upload, then upload through Apple's upload app, the command line or Xcode. It also mentions Codemagic's command line tools as a way to automate signing and upload. A cloud build service such as Codemagic can do this so releases do not depend on one person's laptop.
- Write a short README. How to build it, where the accounts are, how to release.
Rewrite or keep?
Keep the app and clean it up when the screens match what users need, the data model makes sense and the problems are bugs, speed and release setup. Rewrite when the data structure is wrong (so every new feature fights it), when you need features the generated code cannot reach, or when cleanup quotes approach rebuild quotes. A fair developer will tell you which one after reading the code, not before.
The wider picture of prototyping in a builder and finishing with a developer is in prototype with AI, finish with a developer. For the general case of getting code out of a builder and owning it, see how to export code from an AI app builder. If your app is on Bubble instead, Bubble agency versus custom code covers the same decision.
How to think about cost
Cleanup scope varies too much for a single average, so here is a worked example with stated assumptions. All figures are made up to show the arithmetic.
- Assume a freelance developer charges $60 an hour.
- Reading the code and writing a short report: 4 hours, $240.
- Cleanup items 1 to 6 on a small app: 20 to 30 hours, $1,200 to $1,800.
- Release setup and README: 6 to 10 hours, $360 to $600.
- Total in this example: about $1,800 to $2,640.
Replace the rate and hours with the numbers in the quotes you receive. The useful habit is to pay for the first step (reading the code and writing a report) separately, so you learn the real scope before committing to the rest. Blur Studio fixes and finishes start around $1,500, and for a wider view of build costs see AI app development cost.
A sample brief to send a developer
- What the app does, in three sentences, and who uses it.
- Link to the FlutterFlow project (view access) and, if you have one, the GitHub repository.
- Which backend it uses (Firebase, Supabase, other).
- A list of what is broken, ranked by how much it hurts.
- Whether the app is live in the stores, and which accounts it sits under.
- What you want at the end: a working release, a clean repository, a README, and all accounts in your name.
What to ask before you hire
- "Will you work in FlutterFlow or in exported code, and why?"
- "What do I own at the end, and where will it live?"
- "Can I pay for a review first?"
- "How will you check the backend security rules?"
- "What happens when I want a small change in six months?"
Red flags: a flat price without reading the code, a developer who keeps the accounts, and anyone who says the only answer is a full rewrite before seeing the app. If you are weighing a freelancer against a team, see fractional CTO versus development agency. If the app is already out and failing, is your AI-built app ready for production gives a checklist.
How I'd approach this
I would take the decision between staying and leaving FlutterFlow first, because it changes the whole scope. If the app works and you only need a few gaps filled, stay and add custom pieces. If you are hitting the same walls every month, leave once, cleanly, and treat the repository as the only truth from then on.
Before any code work, I would move every account into your name and get the app building from a clean checkout. Those two steps are cheap and they remove the biggest risks: being locked out, and not knowing whether the app can be rebuilt at all. Then fix what hurts users, then add automatic builds. Resist new features until that is done.
Questions people ask
Can I export my FlutterFlow app code?
Yes. FlutterFlow's pricing page lists code download on the Basic, Pro and Max plans and push to GitHub on Pro and Max, as of November 2026. See how to export code from an AI app builder for what to check about ownership.
Can I keep editing in FlutterFlow after a developer changes the code?
Not safely in the same branch. FlutterFlow's docs say changes made directly to the flutterflow branch are overwritten by the next push. Developers make their changes on a separate branch and merge, which costs time on every merge. Most hand-offs pick one home for the app.
How much does it cost to hire a FlutterFlow developer?
It depends on scope and the developer's rate, so ask for a paid review first. Multiply their hours by their rate for each cleanup item, as in the worked example above. Rough build cost ranges are in AI app development cost.
My FlutterFlow app is not working. Where do I start?
Find out whether the problem is in the app (a bug), the backend (Firebase or Supabase rules, quotas) or the release (signing, build numbers). A developer can usually tell in a short review. If it only breaks in production, how to move an AI-built app to production covers the usual causes.
Do I need Codemagic?
Not to start. Flutter's iOS guide shows how to build and upload from a Mac with Xcode. A cloud build service such as Codemagic helps once you release often or do not want releases to depend on one person's computer.
Should I rewrite the app instead?
Rewrite if the data structure is wrong or you need features the generated code cannot reach, or if cleanup quotes come close to rebuild quotes. Otherwise a cleanup is cheaper. See prototype with AI, finish with a developer.
More in this topic: Problem solving: AI-built and no-code apps (26 guides) →