FlutterFlow or Exepad
A FlutterFlow alternative for web apps and agents
FlutterFlow builds Flutter apps for phones, the web and desktop on a backend you connect. See what its code download holds, where your records stay, and which projects an Exepad web app can take over.
FlutterFlow
Where FlutterFlow fits.
FlutterFlow is a visual development environment for mobile, web and desktop apps. You lay out screens from pre-designed UI elements, add logic in its Action Flow Editor, and connect a backend such as Firebase or Supabase. Each project is a complete Flutter app, and exported code runs without FlutterFlow.[1][2][3]
Flutter code you can download
On paid plans you download the project as a zip from the Developer Menu or with the FlutterFlow CLI. Growth plans and above can also push it to GitHub, where it lands on a branch named flutterflow.[4][5][6]
Exepad
Where Exepad fits.
Exepad is Your App Cloud. Each app starts as a description in Studio. You review what the building assistant makes, then publish a web app people open from a link in a laptop or phone browser. Where a FlutterFlow project leans on a backend you connect, an Exepad app carries its own.
Records, files and sign-in in one app
Where a FlutterFlow app takes Firestore, Storage and Authentication from Firebase, an Exepad app has its own database, file storage and sign-in. Describe the access for each collection, then check it with a test account.[7]
Models and agents next to the records
FlutterFlow's AI Agents are called from app actions. In an Exepad app, Language, Vision, Media and Voice models sit next to the database. An agent there reads the app's records with the context and actions you allow. Have a person approve its output before anyone acts on it.[10]
Email and schedules
FlutterFlow uses Cloud Functions in your Firebase project for push notifications and some payment integrations. An Exepad app can send email and run tasks on a schedule you set. Test each flow before users depend on it.[7]
Compare the work you need to do.
| Consider | FlutterFlow | Exepad |
|---|---|---|
| What you build | Mobile, web and desktop apps from one visual Flutter project. Android and iOS run by default, and web is a platform you switch on.[1][11] | Web apps that open in a browser, including on phones. Pick the one task people will do there first and describe it in Studio. |
| How you build | Build screens from pre-designed UI elements, wire logic in the Action Flow Editor, and write custom Dart functions, actions or widgets for features the standard components don't include.[2][12] | Describe in Studio what each FlutterFlow page shows and what its Action Flows do. The building assistant creates the app; you refine it, review the version, then publish. |
| Where records live | In a backend you connect: a Firestore database in your Firebase project, Supabase tables, or your own API. FlutterFlow's hosting does not store your users' data.[2][8][13][14] | In the app's own database rather than a Firebase or Supabase project you connect. Name each collection and its fields, then open a few records after publishing. |
| Sign-in | Firebase Authentication, which you enable in the Firebase console, or Supabase auth, which needs a users table in your Supabase project.[7][14] | Authentication, with the access you describe for each collection. Decide how people who signed in through Firebase or Supabase will sign in here, then test with a second account. |
| AI in the app | AI Agents for chat, images, video and speech, called from app actions. They need a Firebase project on the Blaze plan and an API key for the provider you choose.[10] | Language, Vision, Media and Voice models. An agent inside the app works on its records with the context and actions you allow, and model usage is metered separately. |
| Code you can take | The Flutter project, as a zip or through the CLI on paid plans. It runs as a normal Flutter app without FlutterFlow.[3][4] | You can export your app's data and code. Do a trial export early and open it, so you know what it holds before a move depends on it. |
| Reaching users | Web publishing to a flutterflow.app subdomain, or a custom domain on paid plans, plus App Store and Google Play releases from the builder on paid plans.[5][11] | Publish from Studio after review, on your own domain with Pro where you used a flutterflow.app address. People open the app from a link in a laptop or phone browser. |
| Working outside the editor | The FlutterFlow CLI creates projects, edits them with AI coding agents and downloads the code. The desktop app can set up an external coding agent for a project.[15][16] | Creating and publishing happen in Studio. An external coding agent can call the MCP server at api.exepad.com/mcp, which has three read tools for keys, wallet and plan limits. |
| How plans are charged | Free, Basic, Growth and Business plans, plus Enterprise. Growth and Business are priced per seat, and AI generation requests are an allowance that varies by plan.[5][17] | Free puts one one-page site live; an app with saved data, sign-in or email needs a paid plan to go live. See Pricing for the current plans. Model and service usage is metered apart from the plan. |
Choose FlutterFlow when
A listing in the App Store and Google Play is the goal.
FlutterFlow sends iOS and Android builds to both stores from inside the builder on paid plans. You still need an Apple Developer membership and a Google Play Developer account, so set those up first.
Flutter developers will keep working on the code.
Your developers write Dart, add custom widgets and actions, and keep the project in GitHub. The exported project runs as a normal Flutter app, so they can carry on in their own editor.
Firebase or Supabase already runs your backend.
Other apps already read the same Firestore database or Supabase tables. FlutterFlow connects to that existing project, so the data stays where it is and the new screens read it directly.
Choose Exepad when
People will use it from a link, not an installed app.
Staff, clients or members open the app from a link, on a laptop or a phone. If nobody needs to install it, there are no Flutter builds or store accounts to manage.
Setting up the backend is what stalls the project.
Connecting Firebase, turning on its billing for Cloud Functions, or writing Supabase access policies before launch is where the work stops. The app has its own database, file storage, authentication and email.
An agent should work through the app's records on a schedule you set.
FlutterFlow's AI Agents answer when an app action calls them, such as a Send button. In an Exepad app, an agent works through the app's records when asked or on a schedule you set, and a person reviews what it prepares.
What changes when you move from FlutterFlow.
FlutterFlow's docs treat the app and its data separately. The code comes out as a Flutter project, while records stay in the backend you connected.
What an export brings
- Pages, widgets and logic. The export is a complete Flutter app with the pages, widgets, business logic and packages you added, and it runs without FlutterFlow.[3]
- A zip or a CLI download. Use Developer Menu > Download Code, or the CLI, which FlutterFlow recommends. Code download is on paid plans only.[4]
- One branch and one environment at a time. The CLI downloads main unless you name another branch, and the project's current development environment unless you choose one. Repeat it for each branch you still need.[18]
- A GitHub copy on Growth and above. Pushes land on a branch named flutterflow, and the next push overwrites direct changes there. Keep your own edits on a separate branch.[5][6]
What stays behind
- Your users' records. FlutterFlow's hosting serves only the web frontend and does not store your users' data. Records sit in the Firestore database or Supabase tables you connected, so export them from that service.[8][13][14]
- Sign-in. Accounts run on Firebase Authentication, enabled in the Firebase console, or on Supabase auth and its users table. Decide how each person will sign in to the new app.[7][14]
- Cloud Functions. Push notifications and Braintree payments run on Cloud Functions in your Firebase project, and AI Agents rely on them too. List each one your app uses.[7][10]
- Store listings and web addresses. iOS builds go to App Store Connect and Android builds to Google Play. The web app is served from a flutterflow.app subdomain or your custom domain. Decide what happens to each listing and address after the move.[9][11][19]
Rebuild it in Exepad
List the screens behind one task
In FlutterFlow, pick the task you want in the browser first. Note each page it uses, what its buttons and Action Flows do, and which collection or table it reads.
Describe them in Studio
Describe those pages, the records behind them and who may use each one. Upload the records you exported and say what each field means. The upload is a copy, so decide where new records go during the switch.
Replace sign-in and notifications
Set up authentication for the people who used the FlutterFlow app. Where it sent push notifications, decide whether an email will do, and send yourself each message as a test.
Rebuild each AI Agent inside the app
Use the agent's system message and preloaded messages as a starting brief. Describe its job, the records it may read and who approves its output, then compare its replies with the FlutterFlow version.
Keep the FlutterFlow app live during the switch
Publish after review and keep the FlutterFlow app live while a few users finish the task in a phone browser. Retire the store listing or flutterflow.app address only once they have.
Try it with one task.
Move one booking screen to the browser
Illustrative example: Kestrel Hill Fitness, a sample gym in Fresno, has a FlutterFlow app where members book classes. Rebuild that one screen before anything else.
In FlutterFlow, open the Class Schedule page and write down its fields, the Firestore collection it reads and what the Book button does.
Get a copy of the classes collection from Firebase, then describe a schedule and booking app in Studio and upload the file.
Ask for member sign-in and a confirmation email when a booking is saved, then book a class as a test member.
Publish after review, open the app in a phone browser and compare ten classes with the FlutterFlow app.
Take new bookings in the FlutterFlow app until the checks pass, then choose one place for them.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Database
Keep data and context for apps and agents
Authentication
Give the right people access
File storage
A home for your documents and media
Language models
Reason, write, and understand
Email
Keep conversations moving
A little more context
Good questions.
Can I import my Flutter project into Exepad?
Studio builds an app from the description you give it, so use the Flutter project as your reference for a rebuild. FlutterFlow's docs say the exported project runs as a normal Flutter app without FlutterFlow, so it stays usable on its own. In Studio, describe the pages, the Action Flows behind each button and the collection each page reads. Then check the new app against the Flutter one, page by page.
Do I need Firebase or Supabase to use Exepad?
No. An Exepad app has its own database and authentication, so there is no Firebase project or Supabase key to connect. Your FlutterFlow records stay in the project you connected. Export what you need from there and upload a copy while you rebuild.
Will my phone app's features work in a browser?
Check each one. FlutterFlow's own web guide says AdMob, RevenueCat, the Share action and the Launch Map action are not yet supported on the web. An Exepad app opens in a browser, including on phones. List the device features your app relies on and try each in a phone browser before users switch.
Do I need to know Dart to build with Exepad?
No. Studio works from your description, and the building assistant produces the app for you to review and publish. FlutterFlow is visual too, but its docs point to custom Dart functions, actions and widgets for features its standard components don't include. In Exepad, you ask for that change in Studio and review it before publishing.
Can the AI Agents in my FlutterFlow app move to Exepad?
Rebuild them. A FlutterFlow chat agent is a system message, optional preloaded messages and model settings that app actions call. In an Exepad app, describe the agent's job, the records it may read and the actions it may take, then compare its replies with the FlutterFlow agent's. Model usage is metered separately.
Can I take my app and data out of Exepad later?
Yes. You can export your app's data and code. In FlutterFlow those come from two places: the code download needs a paid plan, and the records sit in Firebase or Supabase. With Exepad, try an export early and look through it, so you know what it holds before a move or a backup relies on it.
Explore Pricing for plans, included capabilities, and usage details.
Related guides.
Compare other tools.
Sources.
FlutterFlow details checked September 25, 2026. Confirm them on FlutterFlow's site before you decide.
- FlutterFlow: getting started ↗
- FlutterFlow: product overview ↗
- FlutterFlow: what is a project ↗
- FlutterFlow: Local Run and code download ↗
- FlutterFlow: plan comparison ↗
- FlutterFlow: push to a GitHub repo ↗
- FlutterFlow: connect to Firebase ↗
- FlutterFlow: application and data ownership ↗
- FlutterFlow: releasing to the Apple App Store ↗
- FlutterFlow: AI Agents in your app ↗
- FlutterFlow: web publishing ↗
- FlutterFlow: writing custom code ↗
- FlutterFlow: Cloud Firestore ↗
- FlutterFlow: Supabase setup ↗
- FlutterFlow: CLI ↗
- FlutterFlow: AI coding agents in the desktop app ↗
- FlutterFlow: pricing ↗
- FlutterFlow: exporting projects with the CLI ↗
- FlutterFlow: releasing to Google Play ↗
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building