Half the people who ask us to turn their Lovable app into a native app don't need a native app. The other half really do, and they usually find out by losing users first. The PWA vs native app question is mostly about which half you're in, and you can answer it before spending any money.
A PWA (progressive web app) is your existing Lovable site plus a manifest file and a service worker. Users "install" it, it gets an icon on the home screen, opens without the browser bar, and can work a bit offline. For a Lovable project that's maybe an hour of work: add vite-plugin-pwa, write a manifest.webmanifest with your name, colours and icons in 192 and 512 pixels, decide what the service worker caches. Done. No Apple developer account, no review, no 30% cut.
So why doesn't everyone stop there?
The iPhone is the whole argument
On Android, a PWA is close to a real app. Chrome shows an install prompt, push notifications work, and it shows up in the app drawer like anything else. Android users barely notice the difference.
iPhone is where it falls apart, and if your users are in the US, more than half of them are on iPhone.
There's no install prompt on iOS. None. The user has to tap Share, scroll down, find "Add to Home Screen", and tap it. You can put a little arrow and instructions on your page and most people still won't do it. We looked at the numbers for one founder whose app had a PWA install banner with step-by-step iOS instructions: of roughly 1,900 iPhone visitors in a month, 31 added it to their home screen. Thirty-one. That's not a funnel, that's a rounding error.
Push notifications on iOS only arrived in iOS 16.4, and they only work after the user has added the app to the home screen. So the 31 people above can get push. The other 1,869 can't. If your app depends on "your order is ready" or "someone replied to you", that alone settles it.
Then there's storage. Safari can clear a website's local data if the user hasn't visited in a while. An installed PWA is treated better, but it's still not the same guarantee a native app has, and we've seen the classic symptom: users "logged out for no reason" after a week away because the session in localStorage was gone.
What a PWA does better
I don't want to make it sound like PWAs are bad. They're the right call more often than founders think.
You ship instantly. Change a button in Lovable, publish, and every user has it on next load. With a native app, every change to native code goes through App Store review, and even with something like Capgo for live updates you're still managing versions.
You keep your payments. If you sell digital stuff (subscriptions, credits, premium features), a native iOS app has to use Apple's in-app purchase for it, which means Apple takes 15 to 30 percent and you rebuild checkout with RevenueCat or StoreKit. A PWA keeps your Stripe checkout exactly as Lovable built it.
And there's no rejection risk. Apple's guideline 4.2 exists specifically to reject "apps" that are just a website in a wrapper. A PWA can't be rejected because it never asks permission.
So which one?
Stay a PWA if your users mostly come from a link (a newsletter, a Slack community, a B2B dashboard people open from their laptop), if push isn't central, and if they're happy to use it in the browser. Internal tools, admin panels, B2B SaaS, anything people use at a desk: PWA, no question. Don't let anyone sell you an app for those.
Go native when the phone is the main screen. Habit apps, fitness, anything with a daily notification, marketplaces where people check messages, apps where "find it in the App Store" is how you'll get users. Also go native when a client or investor simply expects to see an App Store link. That's a dumb reason technically and a completely valid one commercially.
There's a middle path we like for a lot of Lovable apps: ship the PWA this week, watch your analytics for a month, and look at two numbers. What share of your active users are on iPhone, and how many of them come back more than three times a week. If both are high, you've proven you need native, and you've got real usage data to decide what the native version should actually focus on.
When you do go native, you have two routes. Wrap the same app with Capacitor, which keeps your code and adds real push and a real App Store listing, or rebuild the screens in React Native. We compared both in Capacitor vs React Native for Lovable apps. Either way, plan for the review: the App Store walk-through covers what Apple checks.
One thing I'd skip: don't build the PWA and the native app at the same time "to cover both". You'll end up maintaining two sets of push logic and two install flows for an app that doesn't have users yet.
If you've done the PWA and the numbers say it's time, tell us about your app. We'll tell you honestly if wrapping it is enough.
Originally published on lovable2app.com. Aakash Verma, software developer and founder of Lovable 2 Live.
Top comments (0)