Lovable → iOS + Android
One published Lovable URL, two native apps. This overview compares what Apple and Google ask for, lists the Lovable-specific details, and links to the detailed iOS and Android walkthroughs.
Click Publish in the Lovable editor. Lovable builds the production bundle and hosts it at your project's lovable.app address. Every later Publish replaces the live version, so your app in the stores updates the moment you publish again.
Insert the URL into WebViewGold for iOS and WebViewGold for Android, set name, icon and splash screen, switch on the native features you want. No coding.
App Store & Google Play approval guarantee – or your money back within 14 days. 96.4% of all WebViewGold apps get approved by the review teams on the first attempt.
| Apple App Store | Google Play | |
|---|---|---|
| Developer account | $99 per year | $25 one-time |
| Build tool | Xcode on a Mac or the Cloud Builder | Android Studio on Windows, macOS or Linux or the Cloud Builder |
| WebViewGold license | $109 one-time | $109 one-time |
| Review time | usually within 24 to 48 hours | usually a few days, up to a week for new developer accounts |
| Testing before launch | Optional (TestFlight) | Mandatory 14-day closed test with 12 testers for new personal accounts |
| Third-party login rule | Sign in with Apple (or equivalent) required if you offer Google/Facebook login | No equivalent rule |
| Digital purchases | In-App Purchase required (RevenueCat supported) | Google Play Billing required in most cases (RevenueCat supported) |
| Detailed walkthrough | Lovable → App Store | Lovable → Google Play |
Do iOS and Android in parallel: both apps use the same URL and the same settings.
Open the project settings, add your own domain under Domains and point the DNS records Lovable shows you. Custom domains are a paid-plan feature. The live editor preview (addresses containing lovableproject.com or id-preview--) is a development view. Never put a preview address into your app: publish first and use the published URL or your custom domain.
Privacy policy page, account deletion, responsive layout down to 320 px, no builder badges, HTTPS everywhere. Run the free readiness check to see what is missing.
Paste the URL, set app name, icon and splash screen in Config.swift and Config.java or in the Cloud Builder. Enable push notifications and the features you need.
Xcode and Android Studio, or the Cloud Builder in the browser for both. The Cloud Builder also uploads to App Store Connect and the Play Console.
Same screenshots (per device size), same description, same privacy policy URL. Start the Google Play closed test the same day you submit to Apple so both reviews run in parallel.
React + Vite + Tailwind CSS + shadcn/ui on the front end, usually Supabase (or Lovable Cloud) for auth, database and edge functions
Supabase Auth (email/password, magic links, Google, GitHub, Apple) or Lovable Cloud. Google and Facebook logins need the WebViewGold Social Login Helper inside the app; Sign in with Apple is handled automatically.
Stripe, typically wired through Supabase edge functions. Digital goods sold inside the apps go through In-App Purchase / Google Play Billing (RevenueCat); physical goods keep your web checkout.
Default: yourproject.lovable.app. Open the project settings, add your own domain under Domains and point the DNS records Lovable shows you. Custom domains are a paid-plan feature.
Publish in Lovable and the change is live in the app immediately, no store resubmission needed.
Edit with Lovable: Hide the badge in the project settings before you build the app (the option is available on paid plans). A floating link to another product inside a store app invites questions from reviewers.
Paste into Lovable, review the changes, publish.
Prepare this app for publishing as a native iOS and Android app (it will run inside a native WebView wrapper): 1. Add a /privacy and a /terms page with placeholder text I can edit, and link them from the footer and the settings screen. 2. Add a "Delete my account" button in the account settings that deletes the user's data and auth account via a Supabase function, with a confirmation dialog. 3. Make sure every page is responsive from 320px to iPad widths, with no horizontal scrolling and tap targets of at least 44px. 4. Remove any "Download our app" banners, external links in the main navigation and the Lovable badge. 5. Add a /offline-friendly empty state for failed network requests instead of a blank screen. 6. Set the <title> to the app name (max 30 characters) and add a meta description.
Documented for iOS and Android; the JavaScript calls are identical on both platforms.
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call, permission prompt at the moment you choose.
DocumentationGoogle and Facebook logins work inside the app; Sign in with Apple is handled automatically.
DocumentationLinks from emails (magic links, password resets) open directly in the app.
DocumentationApp Store subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationA native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationYes. Apple reviews what the app does, not which tool wrote it. A Lovable app that behaves like an app (responsive layout, native navigation, no dead links) passes review like any other WebViewGold app. The guideline to respect is 4.2 Minimum Functionality: add native value such as push notifications, offline handling or native sharing, all of which WebViewGold switches on with one setting each.
No. WebViewGold loads your published Lovable URL inside a native app shell, so the app always shows the current version of your project. You keep editing in Lovable and never touch the generated code unless you want to.
Yes. Because the app loads your published URL, every Publish in Lovable updates the app instantly. Only changes to the native shell itself (new app icon, new native feature) need a new build and store update.
Yes, if you can. Both apps use the same web app, so the extra work is one more license and one more listing. Start the Google Play closed test early: for new personal accounts it takes 14 days before production is available.
Yes, one for iOS and one for Android. Each is a one-time payment with free updates, and the Full Service package covers both if you prefer our team to do everything.
App Store & Google Play approval guarantee – or your money back within 14 days
Prefer to hand it over? Full Service: we configure, build and submit for $349. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.
