Guide
FlutterFlow vs a Flutter boilerplate: which to start with
Both get a Flutter app with sign-in and payments running faster than an empty project. They suit different teams. Here's how they differ on code ownership, custom code, AI coding agents and cost, with each FlutterFlow fact taken from its own docs and pricing page. If you're looking for a FlutterFlow alternative, the last sections are for you.
Updated
The short version
- Choose FlutterFlow if the people building the app want to design screens visually, and most of the logic fits its actions, integrations and custom-code slots.
- Choose a boilerplate if developers will write most of the app, you want normal code review and Git history from day one, or you build with an AI coding agent.
- Plan for code to flow one way. FlutterFlow's GitHub docs describe pushing from FlutterFlow to your repository. They don't describe bringing your own code changes back into the editor, so assume a handwritten change stays outside it.
What each one is
FlutterFlow is a visual development environment. You build screens and logic in its editor and it generates the Flutter code. A boilerplate (or starter kit) is a Flutter project you download: the code is the product, already set up with things most apps need, such as sign-in, subscriptions, push notifications and theming. You open it in your editor and change it like any other codebase.
Side by side
| FlutterFlow | A Flutter boilerplate | |
|---|---|---|
| How you build | Visual editor that generates Flutter code | Write and edit Flutter code in your own editor |
| Code access | Download from the Basic plan; GitHub push from Growth | The code is what you get, from day one |
| Editing outside the tool | Keep it on a separate branch and merge each FlutterFlow push | Normal Git workflow |
| Custom code | Custom functions, actions, widgets, code files and pub packages, within limits | Anything Flutter can do |
| AI coding agents | On exported code or custom code files | On the whole repository |
| Cost | From $39/month (Basic); team plans charge per seat | Free to about $455 once, or a subscription for some kits |
Owning the code
FlutterFlow's pricing page lists code download from the Basic plan and GitHub integration from Growth. It doesn't list either for the free plan.
The GitHub docs say FlutterFlow "always pushes changes to a branch named flutterflow" and warn that direct changes to that branch "will be overwritten by the next push". The recommended setup is a develop branch for your own changes, with pull requests from flutterflow into it. That works, but every FlutterFlow push is now a merge you review, and the docs don't describe your code changes flowing back into the editor.
With a boilerplate there's nothing to sync. The repository is the source of truth from the first commit, and what you review is what you wrote.
Custom code
FlutterFlow has defined slots for code: custom functions, custom actions, custom widgets, code files and native configuration files (docs). You can add pub.dev packages, and use them from custom actions and widgets. Some limits the docs list: custom functions can't add imports, custom widgets can't return a value, and packages should support web to run in the editor's Run and Test modes.
In a boilerplate, custom code is just code. You pick the state management, add any package and restructure freely. The trade-off is that you also own every decision a visual tool would have made for you.
Building with an AI coding agent
Agents such as Claude Code, Codex and Cursor work on files in a repository. They read the code, make changes and run flutter analyze and flutter test. That fits a boilerplate directly. With FlutterFlow, an agent can work on exported code or on custom code files. Screens built in the visual editor live in FlutterFlow, not in files the agent edits, and generated code that FlutterFlow will overwrite is a poor place for an agent's changes.
Whichever starter you pick, give the agent a brief. An AGENTS.md at the repo root that lists the project's conventions, commands and "never do" rules keeps it from inventing new patterns. Template369 ships one, along with six step-by-step skills; see Build with an AI agent.
Cost
FlutterFlow is a subscription: at monthly prices, Basic is $39, Growth is $80 for the first seat and $55 for a second, and Business is $150 for the first seat and $85 each for seats two to five. Yearly billing saves about 25%. Boilerplates range from free and open source to one-time payments of roughly $60 to $455, and a few, Template369 included, are sold by subscription. See Flutter boilerplates compared for current prices. Either way, the bigger cost is usually the hours you spend after the starter, so pick the one your team will be fastest in.
Where FlutterFlow is the better choice
- Designers or product people need to build and change screens without writing Dart.
- You want a visual editor, live preview and built-in integrations more than full control of the code.
- The app is mostly standard screens, forms and lists, with little custom logic.
Looking for a FlutterFlow alternative?
If you've outgrown the visual editor, there are two common routes. Export your FlutterFlow code and keep working on it as a normal Flutter project, accepting that the editor is no longer the source of truth. Or start from a boilerplate and rebuild the screens, which often goes faster than expected because sign-in, payments and settings are already done. Either way, compare kits on what they include and what they cost, not just their feature list: see Flutter boilerplates compared.
Questions to decide it
- Who builds the screens? Designers or non-developers point to FlutterFlow; developers point to a boilerplate.
- How much logic sits outside standard actions? The more custom code, the more a boilerplate's freedom matters.
- Do you need code review and Git history from the start? That's native to a boilerplate and a merge workflow on FlutterFlow.
- Will an AI agent write much of the code? Agents work best on a plain repository with written conventions.
- How many people edit the app? FlutterFlow charges per editor seat; boilerplate licences vary, so check each one.
Common questions
Can I export my code from FlutterFlow?
Yes, on a paid plan. The pricing page lists code download from Basic and GitHub integration from Growth. The exported project is ordinary Flutter code you can open in any editor.
Is FlutterFlow free?
There's a $0 plan for building in the editor. The pricing page doesn't list code download or GitHub integration for it, so plan on a paid plan if you want the code.
Can I use Claude Code, Cursor or VS Code on a FlutterFlow project?
On the exported code, yes. Follow FlutterFlow's GitHub setup: make your changes on your own branch, such as develop, not on the flutterflow branch, which the next push overwrites.
How do I move from FlutterFlow to a boilerplate?
There's no converter. Rebuild the screens in the boilerplate, using your FlutterFlow app as the reference, and copy over any custom functions and widgets, which are already plain Dart. Start with the screens the kit doesn't already have; sign-in, settings and payments are usually done.
How we checked
FlutterFlow facts come from the plan feature lists on its pricing page and its docs on custom code and GitHub, read on 18 October 2026. Plans and prices change, so check the pricing page before you buy. We make Template369, a Flutter boilerplate, so read this with that in mind; we've tried to say plainly where FlutterFlow is the better fit.