What it is
Lovable turns a chat prompt into a full-stack web app and hosts it for you. Founders, indie hackers and product people who would rather describe an app than code it.
Start here
Lovable app → App StoreStep by step from the published Lovable URL to the App Store listing, with the Lovable-specific checks.Lovable app → Google PlayThe Android walkthrough for Lovable apps, including the Play Console setup and the 12-tester rule.Lovable: App Store + Google PlayBoth stores from one URL: differences, costs and the parallel plan.Lovable app rejected: fixesRejected? The triage for Lovable apps, the usual reasons and a reply template.
Native features for Lovable apps
Each feature page explains the native part (one setting or one URL call) and the web-app part for your Lovable stack, with a prompt to paste.
Push notificationsBrowser web push on iOS only works for home-screen web apps and most users never see it. As a native app built with WebViewGold, your Lovable app gets the real thing: system push notifications on iOS and Android, sent from your backend, from a dashboard, or scheduled by your own JavaScript.In-app purchasesYour Lovable app probably charges through Stripe, typically wired through Supabase edge functions. On the web that stays. Inside the iOS app, Apple requires In-App Purchase for digital goods (Guideline 3.1.1), and Google Play Billing applies on Android. WebViewGold handles both through RevenueCat with one URL call from your web app.Google login and Sign in with AppleLovable apps typically use Supabase Auth (email/password, magic links, Google, GitHub, Apple) or Lovable Cloud. Email and password login works unchanged inside a WebViewGold app. Google and other OAuth providers block embedded WebViews, and Apple adds a rule of its own. Here is how to make every login method work in the app without changing your auth code.Biometric loginA password field feels like a website. Face ID feels like an app. WebViewGold adds biometric authentication to your Lovable app in two flavors: a simple app lock switched on in the config, or a JavaScript API (
bioauth://) that returns the result to your web app so you can gate exactly the screens you want.QR code and barcode scannerBrowser-based QR scanning in a WebView is slow and permission-hungry. WebViewGold opens the native camera scanner from a link (qrcode:// or barcodescanner://) and hands the result straight back to your Lovable app: a URL is opened automatically, a barcode value lands in a JavaScript variable.GeolocationYour Lovable app already calls navigator.geolocation. Inside a WebViewGold app that call triggers the real system permission dialog, and the position comes from the device GPS instead of a browser approximation. No native code: you only write the purpose string and answer the store questionnaires.AdMob adsWeb ad networks pay little inside apps and often break in WebViews. WebViewGold integrates the native AdMob SDK: a banner below your Lovable app, interstitials after a number of interactions, and rewarded videos you trigger from JavaScript when the user wants extra credits or content.Offline modeReviewers switch on airplane mode. Users ride the subway. A Lovable app that shows a white page offline looks broken; a native offline screen with a retry button looks like an app. WebViewGold gives you three levels of offline support, and the right one depends on your stack (React + Vite + Tailwind CSS + shadcn/ui on the front end, usually Supabase (or Lovable Cloud) for auth, database and edge functions).Deep linksA user taps the magic link from Supabase Auth (email/password, magic links, Google, GitHub, Apple) or Lovable Cloud in their email and lands in Safari, logged in on the web but not in the app. Universal Links and App Links fix that: https links to your domain open the Lovable app directly. Here is the complete setup, plus custom scheme links for QR codes and other apps.Native share and hapticsTwo small things make a Lovable app feel native in the first minute: a real share sheet (AirDrop, Messages, WhatsApp, Mail) instead of a copied link, and a subtle vibration when something succeeds. WebViewGold exposes both as URL calls you can wire into existing buttons.File downloads and camera uploadsA plain WebView silently ignores a PDF download and shows a bare file picker. WebViewGold saves images to the camera roll (savethisimage://?url=…), downloads PDFs, audio, ePub and Office files, and opens the native camera or gallery for every <input type="file"> in your Lovable app.In-app ratingRatings decide whether a store listing converts. WebViewGold lets your Lovable app show the native rating dialog (rateapp://) exactly when a user is happy: after a completed order, a finished workout, a saved project. You decide the moment in your web app; the native part is one call.Custom CSS and JavaScriptThe website needs a cookie banner, a footer with 30 links and a "Download our app" badge. The app needs none of them. WebViewGold injects a custom.css and custom.js file into every page your Lovable app loads inside the app, so the website stays untouched and the app looks like an app.NFC tag readerSafari gives websites no NFC access at all, and Web NFC only exists in Chrome on Android. Wrapped with WebViewGold, your Lovable app starts a native NFC scan with one link and receives the tag content in a JavaScript function: on Android through the documented NFC API, on iPhone through the WebViewGold NFC plugin. Check-ins, equipment tags and tap-to-save contact cards become a few lines of code.Document scannerIf your Lovable app has a file upload, it can have a real document scanner. WebViewGold adds a Scan document entry to the native upload dialog: Apple VisionKit on iPhone and Google ML Kit on Android find the page edges, crop and enhance each page, and hand the result to your existing file input like any other upload.Printing and AirPrintThe print button that works in the browser usually goes quiet inside an app, because app WebViews do not handle window.print() the way Safari or Chrome do. WebViewGold gives your Lovable app a native alternative: printitem:// downloads a PDF or image from your server and opens the system print dialog, AirPrint on iPhone and the Android print service, with Save as PDF as an option.Clipboard copy and pasteCopy buttons that silently fail and paste fields that never fill are classic WebView annoyances. In a WebViewGold app, your Lovable app reads the device clipboard on demand with getclipboard:// (the content lands in the clipboarddata variable), and copying uses the standard web Clipboard API with a fallback. Here is the pattern, plus the privacy rules both platforms enforce.Contacts accessFind-your-friends screens, group invites and split-the-bill apps often want the address book. In a WebViewGold app, your Lovable app asks for permission with requestcontactpermission:// and receives names and phone numbers as JSON in the contacts variable after readcontacts://. The code takes minutes; how you use the data decides whether the app passes review.Video and audio playbackAn HTML5 video tag works inside the app, but long lessons feel cramped and playback usually stops when the user switches apps. With WebViewGold your Lovable app hands a stream URL to the native player with one link (startnativevideo://), so viewers get fullscreen and Picture-in-Picture on both platforms and AirPlay on iPhone. On iOS you can also keep HTML audio playing in the background for podcasts, radio and audio courses.Screenshot protectionPaid lessons, private chats, account balances, single-use coupons: some screens should not end up in a group chat. WebViewGold can block screenshots and screen recordings on Android and detect them on iOS, then call a JavaScript function in your Lovable app so you can react. The same toolkit also works the other way round: takescreenshot:// saves a screen to Photos on purpose, for tickets and receipts.HealthKit and Health ConnectFitness trackers, habit apps and coaching tools built with Lovable can show the user's real step count, heart rate or weight instead of asking them to type it in. WebViewGold reads and writes Apple Health (HealthKit) on iOS and Health Connect on Android with the same two URL schemes. The code is the easy part; the store rules for health data deserve most of your attention.Calendar eventsA booking that is not in the user's calendar is a no-show waiting to happen. On iOS, WebViewGold lets users add an event to the Calendar app from a plain link to an .ics file, so your Lovable app needs nothing more than a URL that returns the event. Android has no dedicated calendar API in WebViewGold; here is what works there instead.FlashlightReading a serial number in a dark storeroom, checking a meter in a basement, finding a seat at a concert: sometimes your Lovable app just needs light. WebViewGold switches the phone's torch on and off from two links, enableflashlight:// and disableflashlight://, on iOS and Android. It is a small feature that works best as a helper inside a bigger workflow.Share extensionA bookmarking tool, a recipe box or a moodboard is only useful if saving takes one tap. With WebViewGold your Lovable app appears in the iOS and Android share sheet, and whatever the user shares (a link, a piece of text, a photo) arrives in your web app as the JavaScript variable sharedData. Your code decides what happens next: prefill a form, save it to your backend, or open an editor.Widgets and shortcutsThe home screen is where an app proves it is more than a bookmark. On iOS, WebViewGold gives your Lovable app four ways to live there: an image widget your server keeps current, quick actions on a long press of the icon, Siri phrases that run your JavaScript, and alternate app icons. Android has no WebViewGold equivalent for widgets and quick actions, so this guide also covers the honest alternatives there.Apple Wallet passesIf your Lovable app sells event tickets, runs a loyalty program or hands out coupons, the pass belongs in Apple Wallet, on the lock screen when it matters. WebViewGold adds the missing link: replace https:// with addpkpass:// in your .pkpass URL and iOS shows the native Add to Apple Wallet sheet. You still create and sign the pass yourself, and on Android, Google Wallet works through its own web save link.Native storage and device IDUsers expect an app to remember them. Cookies and localStorage usually keep your Lovable app signed in, but they are web storage and go away with the cache. WebViewGold adds two small native helpers: a persistent value store (writevalue:// and readvalue://) for settings and session restore, and a device UUID (get-uuid://) for device-bound licenses, trusted devices and per-device settings on your server.Meta Audience Network adsIf your audience lives on Facebook and Instagram, Meta Audience Network can be an alternative to AdMob. WebViewGold integrates the native Audience Network SDK: timed or page-triggered interstitials on iOS, banners and interstitials on Android, configured in Config.swift and Config.java and steered from your Lovable app. Here is the setup, the privacy paperwork and where ad apps get rejected.Native tab bar and navigationA hamburger menu and a website header are the fastest way to make a Lovable app feel like a bookmark, and that is exactly what reviewers judge under Guideline 4.2. WebViewGold adds a native tab bar or sidebar on iOS and a Material bottom navigation or drawer on Android, each configured in one file, while your web app keeps doing the routing.Splash screen and loading indicatorA white screen for two seconds after launch is how a Lovable app collects a Guideline 2.1 note or a one-star review. The native app opens instantly; your web app needs a moment. WebViewGold covers that moment with a branded splash, a native loading indicator and pull-to-refresh, and a few lines in your web app make the hand-off invisible.Safe area and status barA Lovable app that looked perfect in the browser can lose its header under the Dynamic Island, its tab bar under the home indicator, or its clock to white-on-white in dark mode. WebViewGold keeps your page inside the safe area by default and colors the status bar natively or from JavaScript. Here is when to rely on that and when to go edge-to-edge with CSS.Force update and version checkYour Lovable web app updates with every publish, but the native shell around it only changes when users install a new store version. When a new feature depends on a newer shell, or old builds point at a URL you are retiring, you need to know who is behind. WebViewGold hands your web app the installed version; a few lines of code turn that into a gentle banner or a hard update screen.External links and URL handlingOn the web, a link to Stripe, Google login, WhatsApp or your help center just works. Inside an app every link needs a destination: the app itself, an in-app browser tab, Safari or Chrome, or another app such as Mail, Phone or WhatsApp. Get it wrong and users end up stranded on a third-party page with no back button, logged in in the wrong place, or paying in a browser while the app waits.Lovable at a glance
Stack
React + Vite + Tailwind CSS + shadcn/ui on the front end, usually Supabase (or Lovable Cloud) for auth, database and edge functions
Publishing and hosting
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.
Authentication
Supabase Auth (email/password, magic links, Google, GitHub, Apple) or Lovable Cloud
Payments
Stripe, typically wired through Supabase edge functions
Builder badge
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.
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.
Store-readiness prompt
Paste into Lovable, review the changes, 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.
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.
- Native app 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 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.
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.