Short answer
Wrap the published web app in a native shell with Capacitor, build it in Xcode on a Mac, and submit it from your own Apple developer account. To pass review it has to be more than your website in a frame: plan native features such as push notifications, add Sign in with Apple if Google sign-in is the only option, and let users delete their account in the app.
The route, and what Apple checks
01
Neither builder sends a web project to the App Store for you
“Lovable has no built-in flow that packages and submits your project to the App Store or Google Play” Lovable docs, Publish
Lovable builds web apps, not React Native projects, and leaves store submission to you. Bolt’s mobile apps are Expo projects started as mobile; Bolt says a project created for the web doesn’t easily switch over. So an existing web app needs a native shell around it.
02
Wrap the app with Capacitor
“wrap your published URL in a native shell with Capacitor outside of Lovable, then submit that shell to the App Store or Play Store.” Lovable docs, Publish
Capacitor adds an iOS project to your web app that loads it in the system web view, with plugins for native features such as push notifications and the camera. Building for iOS needs a Mac with Xcode. Lovable names this route itself.
03
Make it more than the website
“Your app should include features, content, and UI that elevate it beyond a repackaged website.” Apple, Guideline 4.2
A wrapper that only shows the site is the classic rejection. Plan what the app does better than the browser, such as push notifications, offline screens, the camera or a home-screen experience built for the phone. No list of features guarantees approval, since Apple judges each app.
04
Add Sign in with Apple and account deletion
“If your app supports account creation, you must also offer account deletion within the app.” Apple, Guideline 5.1.1(v)
If people sign in only with Google or another social login, Guideline 4.8 asks for an equivalent option that collects only name and email, lets people hide their email, and doesn’t track them for advertising without consent. Sign in with Apple is the usual choice. If people can create an account, they must be able to start deleting it inside the app.
05
Submit it from your own developer account
“Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content.” Apple, Guideline 4.2.6
The app goes out under your own Apple Developer Program membership, which costs 99 US dollars a year, in your name or your company’s. Submit it yourself: Guideline 4.2.6 rejects apps from app generation services unless the content’s provider submits them, so an app should not go out under a builder’s or agency’s account.
Checked against the vendor’s docs on : Lovable docs: Publish (native iOS and Android); Lovable docs: FAQ (mobile apps); Bolt docs: Expo mobile apps; Apple: App Review Guidelines (last updated October 16, 2026); Apple: Developer Program membership; Capacitor docs: Environment setup.
Rather hand it over?
Start with a paid consultation to agree the plan, then get a written quote with a fixed price.
- $100 per 15 minutesPaid consultationGo through the app and the move with Simon and agree the plan.Book a consultation
- Written quoteDescribe the app, such as how people sign in and what it should do on the phone, and get a fixed price and timeline in writing; we reply by email, usually within one business day.Describe your project
Related: App Store Guideline 2.1 · App Store Guideline 5.1.1