Step-by-step
- Connect your app to a GitHub repository. Make sure your Lovable, Vite, or React app is in a GitHub repo so Nativize can read the source and run cloud builds.
- Open Nativize and sign in with GitHub. Use the Chrome extension on lovable.dev or the web Studio, then sign in with GitHub so Nativize can verify your plan and access the repository.
- Choose your app options. Set the app name and identifier, then pick app permissions, push notifications, native social sign-in, and store-upload workflows depending on your plan.
- Generate the Capacitor native kit. Download it as a zip or push it straight to your GitHub repository.
- Run the cloud build. The GitHub Actions workflow builds Android and compiles iOS in the cloud. Download the build artifacts when it finishes.
- Sign and submit to the stores. When you are ready, set up signing and submit to the App Store or Google Play with your own developer accounts. Store review and approval are handled by Apple and Google, not by Nativize.
Common use cases
Lovable app to iOS
Turn a Lovable web app into a native iOS project and compile it in the cloud without setting up Xcode on day one.
Lovable app to Android
Generate a native Android project and build an installable artifact through GitHub Actions.
AI-built web app to native
Take an AI-built web app that produces a web build and convert it into an owned Capacitor native project.
Vite or React to Capacitor
Skip the manual Capacitor setup and generate the native project, scripts, and build workflows.
Update and rebuild
Changed your app in Lovable? Push the new build and rebuild without redoing the whole native setup.
Mac and Windows builds
On supported plans, also generate macOS and Windows desktop project output from the same web app.
What you end up with
A real Capacitor project in your own GitHub repository — native platform folders, configuration, install scripts, and GitHub Actions build workflows. It is a project you own and can keep building with, not a black-box hosted wrapper.
- Standard Capacitor 8 project files you control.
- GitHub Actions workflows that produce installable native artifacts.
- Optional permissions, push, social sign-in, signing, and store-upload setup.
What Nativize does not promise
Nativize does not guarantee App Store or Google Play approval, and it is not a fully custom Swift, Kotlin, or React Native rewrite. Publishing still needs your own developer accounts, signing, and compliance with each store's policies.
Last reviewed: