One codebase, real store app
The Android app loads your published Lovable URL inside a native WebView. There is no second project to maintain and no code export.
Why wrapping beats rebuilding for Lovable apps
Lovable publishes a web app to your lovable.app address and has no native app output of its own, so the stores are out of reach until you wrap it. WebViewGold loads that published URL in a native shell, which means every Publish in Lovable updates the app instantly and you never export or maintain the generated React code. Native extras the review teams like to see (push, offline screen, share sheet, Universal Links for Supabase magic links) are settings, not a rewrite.
Keep shipping from Lovable
Publish in Lovable and the change is live in the app immediately, no store resubmission needed. Only changes to the native shell itself (icon, new native feature) need a store update.
Native features on top
Push notifications, offline screen, native sharing, biometric login, QR scanner, in-app purchases and deep links are single settings or one-line JavaScript calls.
Google Play approval guarantee
Google Play Store 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.
What you need
- A published Lovable app on a public HTTPS URL (yourproject.lovable.app or, better, your own domain)
- An Google Play Console developer account ($25 one-time) to submit to the Google Play Store
- Android Studio on Windows, macOS or Linux – or the WebViewGold Cloud Builder in your browser
- WebViewGold for Android ($109 one-time, free updates)
- A privacy policy page, a 1024 × 1024 px icon and 30 to 60 minutes
WebViewGold has allowed us the shortest and most efficient time-to-market ever possible from among all the other app platforms we have ever tried during the past 5 years. I don’t know why I hadn’t discovered you sooner, but I am really, really glad I did. Currently nearing 6000 app downloads on both iOS App Store & Google Play Store without any problem!
Lovable to Google Play: the walkthrough
Eight steps, no coding. Most people finish the native part in under an hour.
Publish your Lovable app to a production URL
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. 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. Custom domain: 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. See why a custom domain before submission is worth it.
Make it store-ready
Add a privacy policy page, an account deletion option (if users can sign up), and remove builder badges or "download our app" banners. Run the free Google Play readiness check on your URL: it flags mixed content, missing viewport tags, builder preview domains and other blockers in seconds.
Get WebViewGold for Android
One-time payment, free updates. You receive the ready-made Android Studio project, or activate the WebViewGold Cloud Builder and skip the IDE entirely.
Insert your URL and brand the app
Open Config.java (or the Cloud Builder form), paste your published URL, set the app name, choose your package name, upload the icon and pick the splash screen. No coding needed.
Switch on native features
Enable push notifications, the offline screen, pull-to-refresh, biometric login, the QR scanner or App Links with single settings. Everything is optional.
Build the signed App Bundle
In Android Studio: Build → Generate Signed Bundle. In the Cloud Builder: click Build and the signed .aab is prepared and uploaded for you.
Create the Play Console listing
Create the app in the Play Console, fill in the store listing, upload icon, feature graphic and screenshots, complete Data safety, content rating and app access.
Test, then submit
New personal accounts run a 14-day closed test with 12 testers first. Then promote the release to production and submit for review. Our approval guarantee covers you.
Lovable-specific checks before you submit
These are the points that come up most often with Lovable projects (React + Vite + Tailwind CSS + shadcn/ui on the front end, usually Supabase (or Lovable Cloud) for auth, database and edge functions).
- Magic-link and password-reset emails from Supabase open in the phone's browser, not in your app, unless you set up Universal Links (iOS) and App Links (Android). WebViewGold supports both.
- Google login inside an embedded WebView is blocked by Google ("disallowed_useragent"). WebViewGold's Social Login Helper routes the OAuth step through a browser window and returns to your app automatically.
- Lovable projects are single-page apps: configure a splash screen or loading indicator in WebViewGold so the first paint never shows a blank white screen in review.
- If your app has a Pro plan or credits paid through Stripe, Apple requires In-App Purchase for digital goods. WebViewGold supports RevenueCat-based IAP; physical goods and services can keep Stripe.
- Add a privacy policy page (for example /privacy) inside the Lovable project: both stores require a public privacy policy URL.
- 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. More on builder badges.
Let Lovable do the store-readiness work
Paste this into Lovable and let it apply the changes reviewers look for. Review the result, then publish.
Prompt to paste into Lovable
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.
Google Play review: the rules that matter for Lovable apps
Google reviews behavior, not tooling. Nobody is rejected for using Lovable; apps are rejected for the points below.
- Minimum functionality
Spam and minimum functionality policy
Google rejects apps that only wrap a website without the website owner's permission or that offer no real functionality. Wrapping your own product with added native features is fine.
- Data safety
User Data policy
Every app needs a privacy policy URL and a completed Data safety form that lists what the app and its SDKs collect.
- Account deletion
User Data policy
Apps that let users create accounts must offer account deletion inside the app and via a web link you provide in the Play Console.
- Testing requirement
Personal developer accounts
Personal accounts created after November 2023 must run a closed test with at least 12 testers for 14 continuous days before they can request production access.
- Target API level
Target API requirements
New apps must target a recent Android version. WebViewGold updates keep the template current; just build with the latest version.
- Payments
Google Play Billing
Digital goods and subscriptions sold in the app generally must use Google Play Billing (WebViewGold supports RevenueCat). Physical goods and services may use other payment methods.
Native features your Lovable app gets in the Android app
Every feature is optional and documented step by step in the WebViewGold for Android documentation.
Push notifications
Remote push via OneSignal or Pushwoosh, local scheduled pushes via a JavaScript call.
DocumentationApp Links and deep links
https links to your domain and custom schemes open directly in the app.
DocumentationIn-app purchases
Google Play subscriptions and one-time purchases via RevenueCat, triggered from your web app.
DocumentationOffline screen and fallback
A native "Try again" screen when the user is offline, or a local HTML fallback.
DocumentationSplash screen and loading indicator
Minimum and maximum splash duration with fade-out, or a native spinner while loading.
DocumentationBiometric login
Fingerprint / face unlock gate from a JavaScript call.
DocumentationQR and barcode scanner
Native scanner that returns the result to your web app.
DocumentationNative share and haptics
Share intent and haptic feedback from your web app.
DocumentationCustom CSS and JavaScript
Hide website-only elements and inject code when loaded inside the app.
DocumentationFile and camera uploads
Native file picker and camera for your upload forms.
DocumentationFeature guides for Lovable apps
Each guide shows the exact setup for your Lovable stack, with a prompt you can paste.
Push notificationsIn-app purchasesGoogle login and Sign in with AppleBiometric loginQR code and barcode scannerGeolocationAdMob adsOffline modeDeep linksNative share and hapticsFile downloads and camera uploadsIn-app ratingCustom CSS and JavaScriptNFC tag readerDocument scannerPrinting and AirPrintClipboard copy and pasteContacts accessVideo and audio playbackScreenshot protectionHealthKit and Health ConnectCalendar eventsFlashlightShare extensionWidgets and shortcutsApple Wallet passesNative storage and device IDMeta Audience Network adsNative tab bar and navigationSplash screen and loading indicatorSafe area and status barForce update and version checkExternal links and URL handling
Pre-flight checklist for Google Play
Tick these off and the review is a formality. The free readiness check verifies the technical half automatically.
- HTTPS everywhere: Android blocks cleartext http:// traffic by default on current versions.
- Responsive layout from 320 px to tablet widths, with predictable back-button behavior (WebViewGold maps the back button to the web history).
- Privacy policy URL ready and the Data safety form answered truthfully.
- Account deletion inside the app plus a web deletion link if users can sign up.
- App access credentials for the reviewer if content is behind a login.
- A unique package name (for example com.yourcompany.yourapp) set before the first upload: it can never change afterwards.
- A 512 × 512 px icon and a 1024 × 500 px feature graphic.
- At least two phone screenshots taken from the real app (tablet screenshots recommended).
- For new personal accounts: 12 testers lined up for the 14-day closed test.
- Signed Android App Bundle (.aab) built from the latest WebViewGold version.
Example: from Lovable project to approved app
Say you built a booking tool for personal trainers with Lovable: clients pick a slot, pay a deposit through Stripe and get a confirmation email from Supabase. You publish, connect book.yourdomain.com, hide the badge and paste that domain into WebViewGold. Because the deposit pays for a real-world training session, Stripe can stay and no In-App Purchase is needed. You turn on push notifications for a reminder the evening before each session, and Universal Links so the confirmation email opens the booking inside the app instead of Safari. Apple asks for a demo client account, you add it to the review notes, and from then on every Publish in Lovable shows up in the app without a new submission.
Your first week after launch
- Fix copy, layout and small bugs with a normal Publish in Lovable; installed apps load the new version on their next launch.
- Set a custom user agent in WebViewGold and save the platform (iOS, Android or web) on each new Supabase profile, so you can see how many sign-ups the stores bring.
- Send the first push campaign on day two or three to people who installed but never finished onboarding, and link it to the screen they skipped.
- Call rateapp:// right after a success moment such as a completed booking; Apple shows its native dialog only about three times a year per user, so do not waste it on the first launch.
- Collect shell changes (new icon, extra native feature, new Universal Link paths) and ship them together in one store update.
What you get with WebViewGold
A complete native app project, not a subscription. Everything below is included in the license and switched on with a setting.
- Complete Android Studio project
- Push notifications
- Offline screen
- App icon & splash screen
- Share sheet & haptics
- Deep & universal links
- In-app purchases
- Free updates, white-label
Frequently asked questions
Does Apple accept apps built with Lovable?
Yes. 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.
Do I need to export the Lovable code to make an app?
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.
Does the app keep working when I change the Lovable project?
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.
Do I need Android Studio?
Either Android Studio (free, runs on Windows, macOS and Linux) or the WebViewGold Cloud Builder, which builds and uploads the signed App Bundle from your browser.
What is the 12-tester rule?
Google requires personal developer accounts created after November 2023 to run a closed test with at least 12 opted-in testers for 14 continuous days before the first production release. Friends, colleagues or a Discord community are enough; organization accounts are exempt.
What if Google rejects the app?
Google names the policy in question and you can fix and resubmit. WebViewGold comes with a Google Play approval guarantee: if Google rejects the app for a non-content reason, you get your money back within 14 days of purchase.
Do I need to turn my Lovable app into a PWA before I wrap it?
No. WebViewGold loads the published Lovable URL directly, so a web manifest or service worker is not required. If you or Lovable added a service worker for offline caching, test that a new Publish actually reaches the app, because an aggressive cache can keep showing the previous version; WebViewGold's own offline screen usually covers the offline case without one.
Can I use Lovable Cloud instead of my own Supabase project for a store app?
Yes. Apple and Google review what the app does, not where the database lives, and the app simply loads your published URL. What matters is that sign-up, login, password reset and account deletion all work inside the app, so test each of them on a real iPhone and a real Android phone before you submit.
Do I have to resubmit the app every time I change something in Lovable?
No. The app loads your published URL, so content and feature changes you publish in Lovable are live in the app immediately. A new store version is only needed when the native shell changes, for example a new app icon or an added native feature.
What does it cost in total?
$109 one-time for WebViewGold for Android (free updates) plus the Google Play Console developer account ($25 one-time). Optional: the Cloud Builder add-on ($349 per license, one-time) if you want to build in the browser without a Mac, or the Full Service package (from $698 per platform) where our team configures, builds and submits the app for you.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.