Yes. In GrowApps you can run your app on your own Firebase project and download its full source code whenever you want. A new app starts on GrowApps' own Firebase, so sign-in and saved data work from the first build with nothing to set up. When you want control, open More, then Your Firebase, to point the app at a Firebase project you own, or download the whole Flutter project as a zip. We don't lock you in. Start with ours, and take your code with you whenever you want.

GrowApps is an AI app builder that makes real Flutter apps for the web, Android and iPhone from one project, with an agent that writes, runs and fixes the code. This guide covers both ways out as of November 2026: the Firebase switch step by step, what stays behind (nothing migrates), what stops working, how to switch back, what the code zip holds, and how Lovable, Replit, Rork and FlutterFlow handle your backend and your code.

Why does a GrowApps app start on GrowApps' Firebase?

You should get a working app before you ever open a cloud console. So when your app needs sign-in, saved data or uploads, the agent adds them on GrowApps' own Firebase project, and they work in the preview right away. You do not create a project, copy keys or write rules to get started.

That is the default, not a wall. There are two ways out, and both are live today:

  1. Your own Firebase. Point the app at a Firebase project in your own Google account.
  2. Your full source code. Download the whole Flutter project as a zip.

You can use either one, both, or neither.

How do I switch my app to my own Firebase?

Open your app in GrowApps, press More, then Your Firebase. The panel says "Your app runs on GrowApps' Firebase project now." and lists the Firebase services your app uses. Then follow its five steps.

  1. Create a Firebase project. Press Open the Firebase console and make a new project.
  2. Add a web app and copy its config. In your Firebase project, open Project settings, scroll to Your apps, add a web app and copy the config Firebase shows you.
  3. Paste the config. If your app also runs on Android or iPhone, open Android and iPhone files (optional) and add the google-services.json and GoogleService-Info.plist files from the same Firebase page. Without them, the phone versions of your app stop at launch.
  4. Check your project. Press Check. Nothing changes in your app yet. GrowApps looks at your project and marks each item Passed, Not passed, Yours to do or Not passed, optional, with a Fix in Firebase link. It checks that the config belongs to the project, that your app's address is an authorized domain, that email and anonymous sign-in are on, that a Firestore database exists, and whether a Storage bucket exists. Google, Apple or phone sign-in you set up yourself in Firebase.
  5. Switch your app. Read the "What stays behind" box, tick "I understand my current users and data stay on GrowApps' project", and press Switch to my Firebase.

Right after the switch, GrowApps shows Paste these rules into your project with two boxes, Firestore rules and Storage rules. Copy each one into the Rules tab of the same service in the Firebase console, then press Done. Until you paste them, your app cannot read or write in your project.

The change goes live the next time you Publish. Uploads need a Storage bucket, and Firebase requires its Blaze plan for new buckets (Firebase Storage FAQ).

What stays behind when I switch?

Nothing migrates. The switch points your app at a new, empty project. It does not copy anything into it. Depending on what your app uses, the "What stays behind" box lists:

  • Accounts. People who signed in do not move, so they sign up again in your project.
  • Saved data. Everything your app saved so far stays in GrowApps' project. Your new project starts empty.
  • Uploads. Files people uploaded stay where they are.
  • Push notifications. Registrations belong to a project, so people allow them again.

If your app already has real users, this matters. The easiest time to switch is before launch, while the data is still test data.

What stops working after the switch?

Some GrowApps features run through GrowApps' own Firebase project, so they cannot follow your app into yours. The panel lists the ones that apply to your app. They include:

  • Sign in with Google or Apple through GrowApps stops working. Use Firebase email or anonymous sign-in instead.
  • Cloud Functions can no longer be deployed by GrowApps. You deploy them yourself, on the Blaze plan.
  • AI features need Firebase AI Logic and App Check switched on in your project.
  • App Check on the web is off until you add your own key.
  • Push notifications need your own Firebase Cloud Messaging setup.

None of this is hidden. The panel shows it before you press Switch to my Firebase, so you can decide with the full picture.

Can I switch back to GrowApps' Firebase?

Yes. While your app uses your project, the panel says "Your app uses your Firebase project" with its name, and shows Check again and Switch back. Press Switch back and GrowApps asks "Switch back to GrowApps' project?" with a plain warning: "Anything people saved in your project stays there. It does not come back." Press Yes, switch back, or Keep my project to stay. Like the first switch, it goes live the next time you Publish.

How do I download my app's full source code?

This is the second way out. In your app, press More, then Files, and press the Download as ZIP icon at the top. The download is not tied to a plan. The zip holds:

  • The whole Flutter project: your code, assets and platform folders, ready to open in any editor and run with Flutter.
  • Your chat history with the agent, as growapps_chat_history.txt, so whoever picks up the code knows why it is the way it is.
  • An ios folder for Xcode and a README_IOS.md with the steps to build the iPhone app on a Mac, when your project did not have an Xcode project yet.

It leaves out the .git history, .env files, build output and Android signing keys. One thing to know: if you have not switched to your own Firebase, the downloaded app still talks to GrowApps' Firebase project. Do the switch first if you want both the code and the data under your control.

Where do my app and its data live?

On the default setup, your app's data lives in GrowApps' Firebase project. After you switch, new data is saved in your own Firebase project, which you manage in your own Firebase console.

Your project's code and history are kept by GrowApps, which runs on AWS. Download as ZIP gives you your own copy at any time. When you bring code into GrowApps, .env files are never kept.

How do Lovable, Replit, Rork and FlutterFlow handle your backend and code?

As of November 2026, from each builder's own docs:

Builder Built-in backend Bring your own Take the code
GrowApps GrowApps' Firebase Your own Firebase project Download as ZIP
Lovable Lovable Cloud, built on Supabase Your own Supabase project Two-way GitHub sync; download on paid plans
Replit Replit-managed PostgreSQL Your own database through DATABASE_URL Download as zip
Rork Rork Cloud (Postgres) Your own Supabase or Firebase GitHub sync on paid plans
FlutterFlow Firebase and Supabase integrations Your own Firebase, and it can create the project for you Code download on Basic and up, GitHub on Pro and up

FlutterFlow connects your own Firebase natively and can create the Firebase project from inside the builder, which is more built in than GrowApps' paste-the-config flow. Rork can transfer a Rork Cloud backend, with its data, into your own Supabase organization, while GrowApps does not move data on a switch. Lovable is a strong choice for web apps and connects your own Supabase. GrowApps fits when you want to start with nothing to set up, get web, Android and iPhone from one project, and keep your own Firebase and your full Flutter code one step away.

FAQ

Which AI app builders let me use my own Firebase?

As of November 2026: GrowApps (More, then Your Firebase), FlutterFlow, which connects an existing Firebase project or creates one (FlutterFlow docs), and Rork, which has a Firebase backend option (Rork Firebase docs).

Does Rork let me bring my own database?

Yes. Rork's docs describe connecting your own Supabase project or your own Firebase, and transferring a Rork Cloud backend into your Supabase organization (Rork backend docs).

Lovable Cloud vs Supabase vs Firebase: which should I pick?

Lovable Cloud is Lovable's built-in backend and is built on Supabase. Lovable can also connect your own Supabase project. Lovable says it does not move a project from Lovable Cloud to your own Supabase in one step (Lovable Cloud docs). Firebase is Google's backend, and in GrowApps it is both the built-in option and the one you can own.

Will my users and data move to my own Firebase?

No. Nothing migrates. Accounts, saved data and uploads stay in GrowApps' project, and your project starts empty.

Can I download my app's code from GrowApps?

Yes. Press More, then Files, then the Download as ZIP icon. You get the whole Flutter project and your chat history, without .env files or the .git history.

Do I need a paid Firebase plan?

For uploads, yes: new Storage buckets need Firebase's Blaze plan. Cloud Functions you deploy yourself need it too. Check Firebase pricing for the rest.

Sources and further reading