To turn a Lovable, Bolt or v0 app into an Android and iPhone app, put its code on GitHub or in a zip and bring it into GrowApps with Bring your project on the home screen. There is no direct Lovable, Bolt or v0 connector. The code comes in through its GitHub repository or a zip export. Flutter apps open as they are. A React, Next.js or other web app is rebuilt in Flutter by the agent, which spends credits, and you see an estimate before the rebuild starts.

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. Once your app is a GrowApps project, the same code gives you an Android install, a Google Play bundle and an iPhone build. This guide covers each step as of November 2026: getting the code out, the import, what is left out, the keys to add back, the credit estimate, and how Lovable, Replit, Rork and FlutterFlow handle code you already have.

How do I get my code out of Lovable, Bolt or v0?

Each of these builders can put your code on GitHub, and GitHub is the easiest way in.

  • Lovable syncs a project to a new GitHub repository, both ways, on all plans. Downloading the code as a file needs a paid Lovable plan (Lovable GitHub docs).
  • Bolt connects a project to GitHub, and you can also download the project as a zip (Bolt Git docs, Bolt projects and files).
  • v0 connects your work to a new private GitHub repository (v0 GitHub docs).
  • FlutterFlow lets you download the code on its Basic plan and up, and push to GitHub on Pro and up (FlutterFlow plan comparison).
  • A React app you wrote yourself is probably on GitHub already.

GrowApps imports public repositories by their link. For a private repository, download it as a zip (on GitHub: the Code button, then Download ZIP) and upload that. The zip can be up to 25 MB. Leave out node_modules and build folders; GrowApps drops them anyway, and they are usually what makes a zip too big.

How do I import an existing app into GrowApps?

  1. Sign in to GrowApps with Google or email.
  2. On the home screen, press Bring your project under the prompt box.
  3. Choose From GitHub and paste the link in Repository URL, for example https://github.com/owner/repo. Or choose Upload a zip and press Choose a zip file.
  4. If the app sits in a folder of a bigger repository, type it in Folder inside the repo (optional), for example apps/mobile.
  5. Press Import. You see "Importing. This can take a minute."
  6. Read the summary. It names the project and the framework it found, lists the files it left out and any keys to add back, and for a rebuild shows the credit estimate.
  7. Press Open the project for a Flutter app, or Start the rebuild for anything else.

The import creates a new project in your account. You can import up to 20 projects a day.

What happens to a Flutter app, and to a React or Next.js app?

GrowApps sorts every import into one of two paths.

Your code What GrowApps does What you see
Flutter, including FlutterFlow and Dreamflow exports Opens it as it is and asks the agent to get it running Imported, then Open the project
React, Next.js, Vue, React Native or Expo, Angular, Svelte, plain HTML, native Android or iOS Keeps the original as read-only reference and rebuilds the app in Flutter Ready to rebuild, a credit estimate, then Start the rebuild

A Flutter app keeps its code. GrowApps removes the lock file and any path dependencies that point outside the project, adds a web folder if the app has none, and asks the agent to get it running in the preview and fix anything that stops it from compiling. Two things stop a Flutter import: a project with no lib/main.dart, and code generation (build_runner, freezed, json_serializable or riverpod_generator) without the generated files. GrowApps does not run build_runner, so run it on your computer, commit the generated files, and import again.

A React, Next.js or other web app is a rebuild, not a copy. Your original code goes into the project as read-only reference. The agent first maps every feature into a list with a check for each one, posts that map with its own estimate, then builds the app group by group and checks each group in the preview. A large app is built in slices over several turns, so test each part as it lands.

If the app used Supabase, the agent rebuilds sign-in with Firebase Auth, tables as Firestore collections, file storage as Firebase Storage and edge functions as Cloud Functions. Your existing users and rows stay in Supabase. The import copies code, not data, so people sign up again in the rebuilt app.

What gets left out, and which keys do I add back?

The import leaves out what a builder recreates or should never hold:

  • .env files. GrowApps keeps none of their values. An .env.example stays.
  • Dependency and build folders such as node_modules, build, dist, .next and .expo, and the .git folder.
  • JavaScript lock files, and any single file over 10 MB.

The summary ends with a "Left out:" line, so you can check. If your app read keys from a .env file, GrowApps reads only the key names and lists them in a note: "If the app needs them, add these keys in More > API keys". In your project, open More, then API keys, and paste the values there. If the app used Supabase, its VITE_SUPABASE_* keys are no longer needed after the rebuild.

How does the credit estimate work?

For a rebuild, the summary shows "Rebuild estimate: X to Y credits" and what it was counted from, for example the screens, API endpoints, data tables, services and sign-in that GrowApps found in the code. More of those means a higher range. It is a first count from the files, and the summary says so: "The agent maps every feature first and gives its own estimate before it builds." So you get a second, closer number after the feature map and before the building starts.

A Flutter import shows no estimate, because nothing is rebuilt. The agent's first turn only gets it compiling.

How do I get the Android and iPhone apps?

Once the app runs in the preview, press Export.

  • Your own Android phone: press Install on my Android phone, scan the QR code and allow the install. The app updates on your phone as the agent works, for 0.02 credits per connected minute. More in testing your AI-built app on your Android phone.
  • An Android file: Build APK, then Download APK.
  • Google Play: Download .aab on a paid plan, with store listing text written for you. The Play Console steps are yours, and this Google Play guide walks through them.
  • iPhone: in the App Store row of Export, the step Build the iPhone app has a Build it button. It takes about 25 minutes and you can leave the page. Then press Download iPhone app. You get an unsigned .ipa that you install on your own iPhone with your Apple ID. It needs a paid plan, starting with Standard.

Uploading to the App Store is your own step today; GrowApps marks it "Coming to GrowApps". To ship to the App Store now, download the code (open More, then Files, then the Download as ZIP icon). The zip includes an ios folder for Xcode and a README_IOS.md with the steps, so you or a developer can sign and upload it on a Mac with your Apple developer account.

How do other builders handle code you already have?

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

Builder Existing code Phone apps
Lovable Imports Bolt, v0, Replit and other ZIPs and rebuilds them in Lovable Web apps; for phones it suggests a PWA or a wrapper such as Capacitor
Replit Imports from GitHub, Lovable, Bolt and ZIP files Expo apps; App Store through TestFlight, Google Play "not yet supported"
Rork Rebuilds a GitHub repo on paid plans; a Lovable app keeps its Supabase database Native Swift and Kotlin apps, plus web
FlutterFlow Code download on Basic and up, GitHub push on Pro and up Flutter apps, with store deployment
GrowApps GitHub link or zip; Flutter as is, other stacks rebuilt in Flutter One Flutter project for web, Android and iPhone

If your app should stay a website, Lovable is a strong choice and you may not need to move at all. Rork does more on store uploads today and keeps an existing Supabase database, where GrowApps moves the app to Firebase. GrowApps fits when you want web, Android and iPhone from one Flutter project and want to try the app on your own Android phone while the agent builds it.

FAQ

Can Lovable build an Android app?

Lovable's own FAQ says it does not make native apps and points to a PWA or a wrapper such as Capacitor (Lovable FAQ). To get a native Android and iPhone app from a Lovable project, sync it to GitHub and bring the repository into GrowApps, where the agent rebuilds it in Flutter.

Does GrowApps connect to Lovable, Bolt or v0 directly?

No. Export the code to GitHub or a zip, then use Bring your project on the GrowApps home screen.

Will my Supabase users and data come with the app?

No. The rebuild moves the app to Firebase, and the import copies code, not data. Users and rows stay in Supabase, and people sign up again in the new app.

How do I get a Bolt app on the App Store?

Bolt's own route uses Expo and EAS commands you run yourself (Bolt Expo docs). Through GrowApps, the agent rebuilds the app in Flutter, Build the iPhone app gives you a build for your own iPhone, and the code zip gives you an Xcode project to sign and upload with your Apple developer account.

Why did my Flutter app not import?

Usually the project has no lib/main.dart, or it uses code generation without the generated files. Run build_runner on your computer, commit the generated files and import again.

How many credits does a rebuild cost?

It depends on the app. The summary shows a range counted from the code before anything starts, and the agent gives a closer number after it maps the features. A Flutter app is not rebuilt.

Sources and further reading