Mobile app for e-commerce — when it pays off and when a PWA is enough

You run an online store and you are wondering whether you need a mobile app. It is one of the most common questions we hear from e-commerce owners — and one of the easiest to answer badly. A native app is a serious investment, while a PWA (Progressive Web App) tempts you with the promise of "almost the same thing" for a fraction of the cost. The truth is that both routes are good — but for different stores and different goals.

In this article we explain how a native app really differs from a PWA, when each of them pays off, and how to make the decision based on numbers rather than trends.

What a PWA is — in short

A Progressive Web App is a website that behaves like an app. It runs in the browser, but it can be "installed" on the phone's home screen, launches in full-screen mode, can work offline (thanks to service workers) and send push notifications. You will not find it in the App Store or Google Play — it installs directly from the website.

For e-commerce, the key advantages of a PWA are:

• One codebase, every platform. The same app runs on Android, iOS and desktop.
• No store installation. The customer lands on the site and buys immediately — zero friction.
• Lower cost and a faster start. You develop a single codebase, often built on top of your existing store.
• SEO and linkability. A PWA is still a website — it gets indexed by Google and every subpage can be linked to.

What a native app is — and what it adds

A native app (or a cross-platform one built in Flutter / React Native) is a separate product installed from a store. It costs more and requires publication in the App Store and Google Play, but in return it delivers things a PWA either cannot achieve or achieves in a limited form:

• Full hardware access. Camera, Bluetooth, NFC (payments, loyalty cards), biometrics, precise geolocation.
• Reliable push notifications — including on iOS, where PWA push is limited and has historically been unreliable.
• Top performance and smoothness — animations, scrolling through long product lists, advanced interactions.
• Presence in the app stores — visibility, credibility, an acquisition channel.
• Deeper system integration — widgets, Siri/Assistant, Apple/Google Pay in a native flow.

The key difference: iOS and push notifications

This is the point that settles many projects. On Android a PWA is very strong — push, installation and offline all work solidly. On iOS the situation is harder: web push notifications only became available in newer system versions, they require the user to add the PWA to the home screen first, and they tend to be less reliable than native push.

If your sales model relies on notifications as a marketing channel (abandoned carts, promotions, restock alerts) and a large share of your customers are on iOS, that is a strong argument for a native app.

When a PWA is enough

A PWA is usually the right choice when:

• You sell to occasional buyers. A customer visits the store once every few weeks — they will not install an app, but they will open a PWA from a link.
• You need a fast start on a smaller budget. You want to validate the mobile market without the full investment.
• Your traffic comes mainly from search and ads. Linkability and SEO work in your favour.
• You do not need advanced hardware. A standard cart, payment and account — no NFC, scanning or offline mode in the field.
• You have a broad, one-off assortment. Long-tail stores where the crucial thing is landing from Google straight on a product page.

When a native app is worth the investment

A native app starts to pay for itself when:

• You have loyal, returning customers. High purchase frequency and a loyalty programme justify an icon on the home screen.
• Push is your sales engine. You consistently make money on notifications — especially with a large iOS share.
• You need hardware features. Code scanning, NFC, loyalty cards in the wallet, AR for trying products on.
• You are after maximum conversion and speed. A smooth, native checkout with biometrics can genuinely lift the conversion rate.
• You are building a brand and a community. Presence in the App Store and Google Play is part of credibility and an acquisition channel.

How to calculate what pays off

Instead of asking "app or PWA", run the numbers on your own data:

1. Share of mobile traffic and the iOS/Android split. A large iOS share plus dependence on push argues for native.
2. Purchase frequency. Returning customers justify an app; one-off buyers point to a PWA.
3. Customer lifetime value (LTV) versus the cost of the app. If the app lifts retention and LTV enough to cover development and maintenance, it is worth it.
4. The role of notifications in sales. How much revenue do your email/SMS campaigns generate today? Push often performs better.
5. Hardware requirements. If any key feature requires native access, the decision has been made for you.

The middle road and a pragmatic approach

The decision does not have to be binary. A common, sensible scenario is starting with a PWA and moving to a native app once the data confirms that mobile customers return and convert. A PWA validates the hypothesis cheaply; a native app scales what already works.

It is also worth remembering that a good mobile app and a good website do not exclude each other — the best e-commerce businesses have a responsive store (often with PWA elements) and an app for regular customers. These are two different channels, not competitors.

If you do build a native app, cross-platform (Flutter or React Native) usually offers the best cost-to-effect ratio: one team covers iOS and Android while keeping native performance and hardware access.

Summary

There is no single right answer — there is an answer suited to your store. Choose a PWA when a fast, inexpensive start, search traffic and occasional customers are what matter. Choose a native app when you have a loyal base, build sales on notifications (particularly on iOS) or need hardware features and maximum conversion. You will make the smartest decision by looking at your own data: the iOS share, purchase frequency and the role of push in revenue.

At Mobilesoft we help you work through this decision on the numbers and we build both PWAs and cross-platform apps for e-commerce — from an MVP to a full rollout with payments and push. Get in touch to discuss your store and receive a quote.