PWA or mobile app: which to choose

“PWA or mobile app?” is one of the first decisions that shapes a product’s budget for years to come. Launch costs can differ threefold, and the time to ship an update ranges from minutes to several days. There is no universal answer: for some tasks a PWA covers every need, for others its iPhone limitations are a deal-breaker.

Here is what a progressive web app can do in 2026, where its capabilities end, and which questions help you decide in 10 minutes.

What a PWA is and how it differs from a website

A PWA (Progressive Web App) is a web app that the browser lets you install on the home screen of a phone or computer. Once installed, it launches with its own icon, without an address bar, in a separate window — visually just like a regular app. Under the hood are three technologies:

• Web App Manifest — a file with the name, icons, colors and display mode.
• Service Worker — a background script that caches assets and data, enabling offline work and fast loading.
• Web Push — push notifications that arrive even when the app is closed.

Unlike a regular website, a PWA works offline, opens instantly from cache and can re-engage users with notifications. Unlike a native app, it is distributed via a link, updates without app store review and has one codebase for all platforms.

PWA vs native app: a comparison

In practice, the choice is between three options: a PWA, a cross-platform app (React Native, Flutter) and a fully native app (Swift for iOS, Kotlin for Android).

Note the search row: a PWA is the only one of the three options that is also a website. Product catalogs, service pages, articles and specialist profiles get indexed by Google and Yandex and bring free traffic, while the installed app retains the users who have already arrived. An app store app has no such channel — you have to buy traffic or move it over from your website.

Cross-platform development is the sweet spot for most business apps: one codebase, near-full device access, app store publishing. Native code is needed for complex graphics, AR, Bluetooth hardware and tasks where every millisecond counts.

PWA limitations on iOS in 2026

Android and Chromium-based desktop browsers support PWAs almost fully. The main limitations are on iPhone and iPad, where every browser runs on the WebKit engine and follows Apple’s policies.

• There is no system install prompt: users must tap Share → Add to Home Screen themselves. You need clear in-app instructions, or only a handful of users will ever install.
• Push notifications work from iOS 16.4 onward and only for apps added to the Home Screen — they are unavailable in a regular Safari tab.
• No background sync: data is sent only while the app is open.
• No Web Bluetooth or Web NFC — you can’t work with POS hardware, tags or sensors from a PWA on an iPhone.
• Safari may clear storage for a non-installed site after a few days without visits; the limit is softer for installed apps, but local data should never be your only copy.
• Apple will most likely reject a PWA wrapper with no added value from the App Store — the store requires functionality beyond a website.

How to increase PWA install rates

• Offer installation not on the first visit but after a valuable action — a completed order, a saved favorite, a successful booking.
• On iPhone, show a short illustrated guide: where the Share button is and which option to pick.
• On Android, use the system install prompt, but trigger it from a button rather than a pop-up.
• Explain the benefit: “get order status updates”, “work offline”, “quick access from your home screen”.
• Measure install rates separately for iOS and Android — the numbers will differ a lot.

PWA pros and cons for business

Pros

• Cost and speed. One codebase for all platforms and desktop, and a launch that is several times faster.
• No app store commission on digital purchases and no waiting for review.
• Instant updates: a bug fix reaches every user the next time they open the app.
• Search engine indexing: every screen can be a page that earns SEO traffic.
• Low barrier to entry: users try the product via a link and install it once they like it.

Cons

• The iOS limitations described above are the main argument against.
• No app store storefront: you have to drive traffic yourself.
• Lower trust among some users: some don’t see an “app from the browser” as a real app.
• Heavy interfaces with lots of animation run less smoothly than native ones.

How much each option costs

For reference, a PWA costs about as much as a web app with similar functionality: our websites start at 120,000 ₽ and 3 days, while offline mode, push and sync add scope depending on how complex the data is. A mobile app for iOS and Android starts at 400,000 ₽ and 8–14 weeks. For the native option, add developer account fees — $99 a year for Apple and a one-time $25 for Google Play — plus app store commissions on digital sales, usually 15–30%.

Costs after launch

The options also differ noticeably in day-to-day running. A PWA updates like a website: deploy a new version and users get it the next time they open it. A mobile app needs builds for two platforms, store review and support for old versions that some users don’t update for months. On top of that, Apple and Google release new OS versions every year, and the app has to keep up with changing store requirements — budget for regular maintenance.

Russian companies face an extra factor: publishing in the app stores, taking payments through them and app availability for part of the audience can be complicated by restrictions that change over time. A PWA distributed from your own domain is practically immune to these risks — another reason to keep a web version even if you have a native app.

For a detailed app budget breakdown, see how much a mobile app costs; current reference prices for all products are on the development pricing page.

Decision tree: 6 questions

1. Do you need Bluetooth, NFC, background geolocation or external hardware? Yes — mobile app. No — next question.
2. Are iPhone push notifications critical from day one, and is your audience unwilling to install a PWA manually? Yes — mobile app. No — next question.
3. Do search traffic and the ability to open the product via a link without installing matter? Yes — PWA or website. No — next question.
4. Is your first-version budget under 400,000 ₽, or do you need to launch within weeks? Yes — PWA, with the app as phase two.
5. Does your audience live in Telegram? Consider a Telegram Mini App — the barrier to entry is even lower.
6. Is it an internal tool for employees? Most often a PWA: you can control installation, and updates arrive instantly.

Typical scenarios from our practice

Candidate and recruiter portals, internal portals, tools for field staff, catalogs and customer accounts are classic PWA use cases. For example, in the hiring platform for a manufacturing holding we used a PWA: candidates and recruiters work from one codebase on phone and desktop, and new features are available right after deployment.

Real-time tracking services, apps for drivers and couriers, and products with app store subscriptions call for a mobile app. In the transfer booking service, the customer and driver apps are built with React Native: drivers need stable geolocation and reliable notifications about new orders.

A common path is to start with a PWA, validate demand and scenarios, then release a mobile app on the same backend. If the API is designed properly, the server side won’t need rewriting. Learn more on the PWA development page.