A Lovable app can ship as a progressive web app with no store fees or review, but on iPhone it must be installed manually from Safari's share menu, and push notifications and other device features are limited. Ship a PWA for internal tools, early validation or desktop-heavy use; ship native store apps when you need discoverability, reliable push, in-app purchases or the trust of an App Store listing.
On this page
Before investing in App Store and Google Play releases, it is worth asking whether your Lovable app needs to be in the stores at all. A progressive web app (PWA) can be installed on a home screen, opens full screen and can work partly offline. For some projects that is enough. For others, the limitations of PWAs, especially on iOS, cost more in lost users than a native release would cost to build. This article compares both options honestly and gives a decision framework you can apply to your project.
What a Lovable PWA can and cannot do
Lovable apps are React single-page applications, so turning one into a PWA mainly requires a web app manifest, icons and a service worker. You can ask Lovable to add these. Once deployed, users can install the app from the browser, and it opens without browser chrome, with your icon and name.
The limits show up on iPhone. Safari does not show an install prompt; users must open the share menu and choose "Add to Home Screen", a step most people do not know about. Web push on iOS works only for installed web apps, on iOS 16.4 or later, after the user grants permission inside the installed app. Background tasks, biometrics through Face ID as a native unlock, in-app purchases and deep integration with system features are either unavailable or limited. Storage can be cleared by the system if the app is not used for a while. On Android, PWAs are better supported, with install prompts and reliable web push.
Side-by-side comparison
| Criterion | Lovable PWA | Native store app (wrapped) |
|---|---|---|
| Store fees | None | Apple USD 99 per year, Google USD 25 once |
| Review process | None | Apple and Google review every release of the native app |
| Installation on iPhone | Manual via Safari share menu | One tap from the App Store |
| Discoverability | Search engines and links | Store search plus web |
| Push notifications on iOS | Only after home screen install | Native push for all users who opt in |
| In-app purchases | Not available, use web payments | Store billing available |
| Biometric unlock, deep links, sharing | Limited | Available through the native shell |
| Update speed | Instant | Instant for web content, review for native changes |
When a PWA is the right choice
A PWA is a strong option when your users already arrive through links you control, for example a team using an internal tool, customers invited by email or participants of an event. It also fits when the app is mainly used on desktop and phone use is occasional, or when you are validating demand and want to avoid store overhead until the product proves itself. Selling digital subscriptions through Stripe without store commission is another reason teams stay on the web, at least initially.
A PWA is also a reasonable first step even if you plan a store release later. Everything you do to make the PWA good on phones, such as touch-friendly layouts, a manifest, offline handling and fast loading, carries over directly into a native wrapper.
When native store apps win
Native apps win when reach on iPhone matters. In many markets a large share of consumers use iOS, and asking them to find "Add to Home Screen" loses most of them. They also win when notifications are central to the product, such as messaging, bookings, delivery updates or reminders, because native push reaches every user who opts in. If you sell digital features to consumers, store billing provides a familiar checkout. And for B2B and public sector customers, an official App Store listing often carries more trust than a link.
The cost of going native has fallen. A native shell like WebViewGold packages your existing Lovable app for iOS, Android and macOS with push notifications, biometric authentication, in-app purchases, an offline screen and deep links, so you do not maintain a second codebase. The main additional effort is the store process and meeting Apple's minimum functionality expectations.
A simple decision framework
Ask four questions. Will most users find the app through the stores or through links you send? Do you need push notifications on iPhone for the product to work? Do you sell digital features to consumers? Do your customers expect an App Store presence? If you answer "links", "no", "no" and "no", start with a PWA. If any answer points to the stores, plan a native release, and keep the PWA for desktop and web users. Many products run both from the same Lovable project.
When you decide to go native, our guides to publishing a Lovable app on the App Store and turning a Lovable project into iOS and Android apps walk through the process, and the article on push notifications for Lovable apps explains the notification setup in both scenarios. Choosing the right channel is ultimately a product decision, the kind we work through with founders when turning an app into an operating company.
Frequently asked questions
Can a Lovable app be installed as a PWA?
Yes. With a web app manifest, icons and a service worker, users can install it from the browser. On iPhone this requires the Add to Home Screen option in Safari's share menu.
Do PWA push notifications work on iPhone?
Only for web apps added to the home screen, on iOS 16.4 or later, and only after the user grants permission inside the installed app.
Can I offer both a PWA and native apps?
Yes. The same Lovable project can serve web and PWA users directly and power native store apps through a shell, so you maintain one codebase.