Documentation
What is CapWrap?
CapWrap turns a website you already have on GitHub into an iPhone and Android app, then sends test builds to Apple and Google for you.
CapWrap is a control desk for shipping a phone app from a web app.
If you built a product in Lovable, Cursor, Bolt, v0, or another tool that puts a website on GitHub, you still need a real App Store and Play Store app. That usually means Xcode, Android Studio, signing certificates, and CI scripts. CapWrap is the missing middle: you stay in a simple dashboard, and CapWrap talks to GitHub, Apple, and Google on your behalf.
You do not need to become a native developer. You do need:
- A GitHub repository for the website (Lovable can create this)
- An Apple Developer account if you want iPhone (paid program)
- A Google Play Console account if you want Android
Honest scope
CapWrap sends test builds: TestFlight (iOS) and Play Internal testing (Android). It does not skip App Store review. It does not create your Apple or Google developer accounts. It does not replace Lovable — it ships what Lovable already pushed to GitHub.
What you get
- A dashboard of every GitHub repo you connect
- A button to add Capacitor if the repo is still a website only
- Store credentials stored on CapWrap’s servers, never in Git
- A GitHub Actions recipe that builds and uploads iOS and Android
- Store listing text you can edit, translate, and push to Apple / Google
- A QR preview of any commit on your phone (the website layer, not native plugins)
What CapWrap is not
CapWrap is not a coding tool, a Mac in the cloud, or a replacement for App Store Connect or Play Console. Apple and Google still own the stores. GitHub still owns the code and the build machines. CapWrap orchestrates them.
Read How it works for the loop, then Your first app to connect a repository.