Native app or PWA for your Shopify store? A practical comparison

The debate between progressive web apps and native apps has been going on for nearly a decade, and it still generates more heat than clarity. You will find confident advocates on both sides who overstate their case. This article tries to cut through that and give you an honest assessment of where each approach actually works.

I want to be upfront: there is no universally correct answer. The right choice depends on your budget, your platform mix, your customer behaviour, and what you actually need the app to do. Let me walk through the real differences.

What each actually is

A progressive web app is a website built with modern web technologies that can be installed to a user's home screen and, in some conditions, accessed offline. It runs in the browser engine, not as a native application. On Android, PWAs are reasonably well supported. On iOS, Safari's implementation of web app standards has historically been limited and inconsistent.

A native app (or a cross-platform app built with React Native or Flutter, which compiles to native code) runs as a genuine installed application. It has access to device hardware APIs, the platform's notification system, camera, biometrics, and the full range of OS-level capabilities. It appears in the App Store and Google Play.

Where PWAs genuinely work

PWAs are not a compromise solution in every situation. For certain use cases, they are the right tool.

If most of your audience is on Android, or you operate in markets where Android dominates, the iOS limitation matters less. PWA push notifications work reliably on Android, and a well-built PWA on that platform performs close to a native app for browsing and purchasing.

If your goal is primarily to get a home screen icon and basic offline capability without the cost of full native development, a PWA achieves that for significantly less money. Budget-wise, a solid Shopify PWA might cost £8,000 to £20,000 to build well, versus £60,000 or more for native.

If your app needs to ship fast and your feature requirements are straightforward, a PWA removes the App Store review process entirely. You can update it instantly, like a website.

Where PWAs fall short

On iOS, the limitations are real and significant for commerce brands.

Push notifications on iOS require the app to be installed via Safari, and even then the behaviour is inconsistent across iOS versions. As of iOS 16.4 and later, web push is technically supported for installed PWAs, but Apple's implementation has known limitations around background delivery, and many users simply do not install PWAs in a way that enables notifications. For a fashion brand that relies on campaign pushes, new drop announcements, sale alerts, back-in-stock notifications, this is a material limitation.

PWAs do not appear in the App Store. That sounds obvious but the practical consequence is that customer acquisition via the App Store, including search, editorial features, and app-install ads, is unavailable to you. For brands with meaningful App Store traffic or campaigns, this is a real loss.

Performance, particularly for image-heavy experiences, tends to be worse on PWAs. Fashion brands with editorial layouts, video backgrounds, and high-resolution product photography will notice the difference in scroll performance and image load times, especially on older devices.

Finally, access to Apple Pay, biometric authentication, and certain hardware features is more limited or more complex to implement in a web context.

Conversion rate comparison

The conversion data here should be treated carefully because it varies significantly by category, audience, and how well each implementation is built. That said, the pattern across published studies and agency data is consistent.

Well-built native apps consistently convert at 2 to 3 times the rate of mobile web for the same product category and audience. PWAs typically improve on vanilla mobile web by 20 to 60 per cent, which is meaningful, but leaves a gap versus native.

Platforms like Tapcart have published data showing average conversion rate lifts of around 2x for their merchant base moving from mobile web to app. Plobal Apps reports similar patterns. These figures come from SaaS app builders, so the underlying apps are not maximally optimised, but they do reflect a real structural advantage that native apps hold.

The conversion gap has two main sources. First, native apps load faster and feel more responsive. Second, the purchase flow is smoother, saved payment methods, biometric authentication, and Apple Pay or Google Pay work more reliably in a native context.

Who should choose a PWA

You should seriously consider a PWA if your audience skews Android, your budget does not support native development, you need to ship quickly, or your primary goal is an improved mobile web experience with home screen installability. Retailers in categories where browsing depth matters more than repeat purchase behaviour, think furniture, specialist equipment, may find a PWA sufficient.

You should also consider starting with a PWA if you are not certain there is demand for an app. A PWA is a lower-risk way to test whether your customers actually install and return to an app experience before committing to native development costs.

Who should choose native

Choose native if your category is fashion, beauty, or lifestyle, where the visual experience is part of the product, repeat purchase rates are high, and push notification campaigns are a meaningful part of your marketing. Choose native if your audience has a significant iOS presence (in the UK, iOS typically accounts for 50 to 55 per cent of smartphones, higher among premium demographics). Choose native if you plan to run app-install campaigns or benefit from App Store discoverability.

Agencies that focus on Shopify mobile, Talmee is one example, generally recommend native builds for fashion and DTC brands precisely because the conversion economics justify the higher upfront cost when the merchant's revenue and audience size are sufficient.

The honest version of this debate is: PWAs are a legitimate technology that solves real problems, but their limitations on iOS are genuine and they are not a direct substitute for native in categories where performance, push notifications, and App Store presence matter. The decision should come down to your specific numbers, not ideology about which technology is better in principle.