A PWA (progressive web app) is a web app that installs to the home screen, works offline and opens in its own window; a mobile app comes from the App Store or Google Play and reaches device features directly. The mobile app wins on store visibility, device features and iPhone notifications, the PWA on fast releases and occasional use. The eight questions below show which side your product is on.
It is easy to see this as a technology choice, but what decides it is what your users will do with the app. In mobile app development projects, we start with these questions rather than with code, and the answers often make the choice on their own.
What is a PWA, and what can it do?
A PWA is a web app that uses modern browser features to behave like an app. Users open it from a link and, if they want, add it to their home screen, with no store visit and no account needed. From then on, a PWA:
- Sits on the home screen with its own icon and opens in its own window, without the browser bar.
- Caches files through a script called a service worker and keeps working to a degree without a connection.
- Can send notifications. On iPhone, web apps added to the home screen have supported this since iOS 16.4, released in 2023.
- Updates without waiting for store review; once a fix is deployed, it reaches everyone.
- Can be found in search engines like any website and shared with a single link.
A PWA can also be listed on Google Play through Trusted Web Activity (TWA), so the same web app can be downloaded from the store on Android.
What do we mean by a mobile app?
A mobile app is software downloaded from the App Store or Google Play and installed on the device. There are two common approaches: native apps written separately for each platform (Swift for iOS, Kotlin for Android) and cross-platform apps built with frameworks such as React Native, which ship to both platforms from one codebase. Either way, the app accesses device features directly, as far as the user allows, is listed in the stores and is subject to store rules.
In short, the difference lies in the level of access and the distribution channel. A PWA does what the browser permits and is distributed over the web. A mobile app reaches a much wider range of what the operating system offers, but it ships through the stores. We look at a similar split on the desktop in Do You Still Need a Desktop App?
Which 8 questions should you ask to make the right call?
Answer these with your team. Under each one, we note which way the answer points.
- Do users need to find you in the app stores? Some users look for a service in the App Store or Google Play first, and a store page with ratings and reviews builds trust. If your users mostly reach you through search engines, a link or a QR code, a PWA already covers that channel. On the App Store, apps that simply wrap a website can be rejected under Apple's minimum functionality rule.
- Which device features do you need? Accessing the camera or getting a location while the app is open works on the web too. Connecting to a device over Bluetooth, reading cards or tags with NFC, tracking location in the background or accessing health data calls for a mobile app. Interfaces such as Web Bluetooth and NFC are not available in Safari on iOS; if part of your audience uses iPhones, that alone can settle the decision.
- How important are push notifications and background work? Web push notifications have worked on iPhone since iOS 16.4, but only after the user adds the web app to the home screen. That extra step narrows the audience a notification can reach. If instant status alerts, regular background sync or work done while the app is closed sit at the heart of the product, a mobile app is the more reliable foundation.
- How much does the app need to work offline? Showing previously opened pages and core content without a connection is a good fit for a PWA. Collecting data in the field for days without a connection, keeping large datasets on the device and resolving conflicting records when the connection returns are built more solidly in a mobile app with a local database.
- What are your performance and animation expectations? Screens built around content, forms and lists run smoothly in a well-built PWA. For heavy animation, gesture-driven interfaces, games or real-time processing of the camera feed, native components deliver a more consistent experience.
- Will you take payments or use in-app purchases? For physical goods and services, card payment providers work on both paths. If you sell digital content or subscriptions inside the app, the stores' in-app purchase rules and commissions come into play, and those rules can vary by country and change over time. Digital content sold on the web is not bound by them, but if you list your PWA on Google Play, the store's rules apply to it as well.
- How fast do you need to ship updates, and is there budget for two stores? With a PWA, a fix reaches everyone once it is deployed. With a mobile app, every release goes through store review, and some users may stay on an old version. Two stores mean two developer accounts, two review processes, separate store listings and privacy declarations. We cover that workload in publishing on the App Store and Google Play and mobile app maintenance and releases.
- How often will users open it? An app people open every day, such as a banking or loyalty app, needs a spot on the home screen, notifications and a fast launch; that is where the extra effort of a mobile app pays off. For an appointment, application or campaign service used a few times a year, asking users to download an app is often an unnecessary hurdle.
If store visibility, a device feature the web does not offer or reliable notifications on iPhone sit at the heart of the product, a mobile app is most likely the right choice. If the answers lean toward speed, easy access and occasional use, starting with a PWA makes sense.
Is there a middle path?
The choice is not always all or nothing. Three middle paths are common:
- PWA first, mobile app later: launch as a PWA, learn from real usage which features you truly need and move to a mobile app afterward. The backend, API and design language carry over to a large extent.
- Google Play through TWA: listing the same PWA on Google Play while serving iPhone users on the web is a way to test a store presence without writing a new app.
- A cross-platform mobile app: frameworks such as React Native produce iOS and Android apps from one codebase and lighten the load of two separate native apps. For Kemerköy Sitesi, we built the iOS and Android app with React Native, together with a management panel.
The path you choose also shapes the budget; we cover the cost drivers in what drives the cost of mobile app development.
When does each one win?
In short:
- The PWA wins: for content, catalogs, forms and bookings; when users come occasionally; when fast updates and search visibility matter; for internal tools where a store process adds nothing; and when you want to start quickly with a single web app.
- The mobile app wins: when you need to be in the stores; when Bluetooth, NFC, background location or health data are required; when reliable notifications and background work on iPhone matter; when expectations for animation and smoothness are high; and when users will open the app every day.
Base the decision not on technology, but on how often and how your users will meet the app.
Frequently asked questions
How do users install a PWA?
On Android, the browser often offers to install the app itself or provides an install option in its menu. On iPhone, users choose "Add to Home Screen" from Safari's share menu. Not everyone knows this step, so a short how-to prompt on your site helps.
Is a PWA cheaper than a mobile app?
The starting cost is often lower, because a single web app runs on both platforms and there are no store processes. But if the web cannot provide a feature you need, a cheap start can turn into a rewrite later. Compare the options on your answers to the eight questions, not on price.
Do you have to rewrite everything when moving from a PWA to a mobile app?
No. The backend, API, data model, design language and content are reused; what gets rewritten is mostly the interface. Building the PWA on a well-designed API from the start makes that move easier.
Does it make sense to offer both a PWA and a mobile app?
For many products, yes. Occasional users can be served on the web while regular users switch to the mobile app. Sharing the same backend keeps maintenance reasonable, but plan for testing and updating both interfaces separately.
Where to start?
Answer the eight questions on a single page and write "PWA" or "mobile app" next to each answer. Then check your current site analytics to see which phones your users carry; if the iPhone share is high, your answers to questions 2 and 3 matter even more. That one page is the most productive starting point for a technical conversation.
If you would like to work out the right path for your product together, get in touch.