Your first app

1. Create a CapWrap account

Open CapWrap and continue with GitHub or Google. Sign-in only identifies you. It does not give CapWrap access to private repositories.

2. Connect a repository

From Apps, tap Add app. GitHub asks which account and which repositories CapWrap may see. Grant only the repos you want to wrap.

CapWrap imports one repo at a time. After GitHub redirects back, pick the repository. CapWrap then:

• Creates an app on your dashboard
• Reads the default branch
• Checks for Capacitor
• Looks at native-related npm packages

3. If it is still a website

You will see Add Capacitor. Choose:

• App name (home-screen name)
• App ID — reverse domain, like app.yourbrand.mobile (lowercase, dots, no hyphens). This becomes the iOS bundle ID and Android package name. Pick it once and keep it. Changing it later is painful on the stores.
• Web folder — usually dist for Vite / Lovable
• iOS, Android, or both

CapWrap opens a pull request on a branch named capwrap/add-capacitor (or commits to the default branch if you tick that option). Merge it, then copy the follow-up prompt into Lovable so packages install and native folders finish. See Built with Lovable?.

4. Walk the checklist

Overview shows Get ready to ship:

1. Add Capacitor
2. App config (keys from .env, if the repo has an example file)
3. Create the iOS app in App Store Connect
4. Connect Apple in Settings
5. Create the Android app in Play Console
6. Connect Google in Settings
7. Turn on shipping (install the pipeline)

You can mark a step done by hand. Creating the Apple / Google app listing record still happens on their websites — CapWrap cannot invent an App Store page for you yet.

5. Send the first test build

When Apple or Google (or both) show Ready, and the pipeline is on the default branch, pick a commit on Overview → Push to Production. Testers install from TestFlight or Play’s internal track — not from the public store yet.

Apple and Google can take 10–30 minutes after a successful upload before the build appears.