Built with Lovable?

CapWrap is built for founders who already ship a website with an AI coding tool. Lovable is the example we use in the product copy. The same steps work with Cursor, Bolt, v0, Base44, or a human developer — as long as the code lives on GitHub.

The division of labor

CapWrap does not log into Lovable. It never sees your Lovable chat. It only sees the GitHub repository you granted.

Connect Lovable to GitHub first

In Lovable, connect GitHub and sync the project so there is a real repo (your-user/your-app). CapWrap cannot wrap a site that only exists on a Lovable URL.

After “Add Capacitor”

CapWrap can add packages and config files, and a GitHub Action can generate ios/ and android/ folders. It cannot do everything an AI in your repo can: install lockfile updates, apply Capacitor breaking changes, or fix a custom Vite config.

That is why the dashboard shows a follow-up prompt. Copy it, paste it into Lovable (or Cursor / Copilot) on the wrap branch, and let the tool finish. You do not need to understand the prompt — it is written for the AI.

When native folders exist on the default branch, return to CapWrap and refresh. The checklist continues with Apple and Google.

Env files from Lovable

Lovable apps often have VITE_ keys in .env. Scan them in App config. Put publishable keys there (Firebase web key, Supabase anon key). Never put a private server secret or a store .p8 / Play JSON in that list.

If Lovable overwrites files

If the AI regenerates package.json or deletes ios/, the next native ship will fail. Tell the tool to keep Capacitor and the `ios` / `android` folders. Re-install the pipeline from Settings if workflow files vanished.