Shopify Mobile App vs PWA vs Mobile Site: Which Should You Build? (2026)

For most Shopify brands, the right order is: a fast mobile-optimized site first, PWA features where they help, and a native app only once you have enough repeat customers to fill it. A native Shopify mobile app gets you an App Store and Google Play listing, the most reliable push notifications, and a home-screen icon your best customers actually tap. A PWA (progressive web app) adds app-like features to your existing site for far less effort, but on iPhone its push notifications only work after a shopper adds the site to their Home Screen. A mobile-optimized site is the baseline every store needs, because it is where almost all new customers will land regardless of what else you build.

What each option actually is

Mobile-optimized site

This is your normal Shopify storefront (a theme or a headless build) designed and tuned for phones: responsive layout, thumb-friendly navigation, fast product pages, and a short path to checkout. Nothing is installed. Every visitor from search, ads, email and social lands here, so it carries your acquisition traffic whatever else you add.

Progressive web app (PWA)

A PWA is still a website, but it ships a web app manifest and a service worker. Those let the browser install it to the home screen, cache assets for faster repeat loads, show an offline screen, and (with permission) receive web push notifications. Shopify themes don't document installable or web-push behaviour as a standard feature, so on Shopify you usually get PWA features through a Shopify App Store app layered onto your theme, or by building them into a Hydrogen or other headless storefront, where you control the service worker directly.

Native mobile app

A native app is installed from Apple's App Store or Google Play. It talks to Shopify through the Storefront API for products, search and carts. Shopify's developer docs describe the pattern: the Storefront API builds the cart and returns a checkout URL, and Shopify's Checkout Kit (Shopify's docs list iOS, Android and React Native support) presents Shopify's own checkout inside the app, so payments, orders and checkout customizations stay on Shopify. You can get one from a no-code app builder on the Shopify App Store or as a custom build, which is the work our Shopify mobile app development team does.

Push notifications: the biggest practical difference

Push is usually why brands want an app at all, so it is worth being exact about what each option can do.

Native apps

Native apps use Apple Push Notification service and Firebase Cloud Messaging. Once a customer installs the app and allows notifications, you can send them back-in-stock alerts, drop announcements, order updates, and abandoned-cart nudges. Opt-in is asked inside the app, at a moment you choose.

PWAs on Android

On Android, Chrome and other major browsers support the Push API for websites, and the shopper does not have to install anything. MDN's Push API reference explains that messages reach a site's service worker "whether or not the web app is in the foreground, or even currently loaded". The only requirements are a registered service worker and the shopper accepting a permission prompt. Installing to the home screen is not required on Android.

PWAs on iPhone and iPad

This is where most PWA pitches oversell. According to WebKit's own announcement, Web Push for Web Apps on iOS and iPadOS, web push arrived in iOS and iPadOS 16.4, but only for web apps the user has added to their Home Screen. A Safari tab cannot receive push on iPhone. The permission request also has to come from a direct user action, such as tapping a subscribe button, not an automatic pop-up. The same release added the Badging API so Home Screen web apps can show an unread count on their icon.

In practice that means an iPhone shopper must (1) open Safari's share menu, (2) choose Add to Home Screen, (3) open the site from that icon, and (4) tap a button to allow notifications. Few people do all four without prompting. If a large share of your mobile revenue is on iPhone, and for many DTC brands it is, PWA push will reach a small slice of your list compared with a native app.

App store presence and review

A native app gets a listing in both stores, which gives you search visibility inside the stores, ratings, and the trust of an installed icon. It also brings costs and rules a website never faces.

• Developer accounts. Apple's Developer Program costs 99 USD a year (Apple enrollment page). Google Play charges a one-time 25 USD registration fee (Play Console Help). If you use an app builder, check whether you publish under your own accounts; you normally should, so the listing and its reviews belong to you.
• Apple's minimum functionality rule. App Store Review Guideline 4.2 says an app should offer features, content and UI that "elevate it beyond a repackaged website." A thin wrapper around your mobile site is the kind of app that risks rejection. Native navigation, saved wishlists, account features, push and app-only content help an app clear this bar.
• Payments for physical goods. Guideline 3.1.3(e) requires apps selling physical goods to use payment methods other than in-app purchase, such as Apple Pay or card entry. That is why Shopify stores can use Shopify checkout in their app and do not pay Apple's in-app purchase commission on product orders.
• Every update is reviewed. Changes to the native code go through store review before customers see them, and you need to keep up with new iOS and Android versions. Content and products pulled live from Shopify update without a release.

A PWA has none of this overhead, and none of the store visibility either. Google Play does accept PWAs packaged as Android apps through a Trusted Web Activity: Chrome's Bubblewrap quick-start guide says the app it builds can be "uploaded to the Play Store for release". Apple has no equivalent route, and its 4.2 rule makes a pure web wrapper a weak bet on iOS.

Offline support and performance

Speed matters more than any of these labels. A slow mobile site loses shoppers before they ever think about installing anything, so fix the site first: image weight, app scripts, theme bloat and third-party tags. Our guide to CRO covers how to find where mobile visitors drop off.

• Mobile site: relies on normal browser caching and how lean your theme is. Many Shopify speed problems come from installed apps injecting scripts.
• PWA: a service worker can pre-cache the app shell and recently viewed pages, so repeat visits feel near-instant and a branded offline page replaces the browser error. It does not make a slow first visit fast, and checkout always needs a connection.
• Native app: navigation and UI are on the device, so browsing feels smooth and screens can show cached data immediately. Product data, inventory and checkout still come from Shopify over the network.

Google's Core Web Vitals guidance on web.dev gives concrete targets to aim for before you spend anything on an app or PWA. They apply at the 75th percentile of page loads, measured separately for mobile and desktop:

Two retailer case studies published on web.dev show what a PWA rebuild of a slow mobile site can do. Note that both were full rebuilds, not a PWA app bolted onto an existing theme, so much of the gain came from speed work. Lancôme reported a 17% increase in conversions, an 84% decrease in time until the page is interactive and a 15% lower bounce rate; 18% of its mobile push notifications were opened. George.com (Asda) reported a 31% increase in mobile conversion rate and 3.8x faster average page load time. These are the companies' own published results, not independent studies.

How to build a Shopify mobile app: builders vs custom

App builders on the Shopify App Store

Search the Shopify App Store for "mobile app builder" and you will find several apps that generate iOS and Android apps from your catalog using drag-and-drop screens, with push tools and integrations for common reviews, loyalty and subscription apps. They are the fastest way to launch and suit stores whose needs match the builder's templates.

• Pros: fast launch, no in-house engineering, the vendor handles OS updates and much of store submission.
• Cons: a monthly subscription that usually scales with plan or usage, limits on custom features and design, and dependence on the vendor's integration list. Moving off a builder later typically means rebuilding the app.
• Pricing: plans change often, so treat the snapshot below as a starting point and check the current listing before you commit.

Public pricing for two builders, read from their Shopify App Store listings as of October 2026 (vendor-published prices; all list a 30-day free trial):

Sources: Shopney on the Shopify App Store and Superfans on the Shopify App Store. Over three years, a 150 to 600 USD monthly plan works out to roughly 5,400 to 21,600 USD in subscription fees before any marketing spend, which is the number to set against a custom build quote.

Custom builds (React Native, Swift, Kotlin)

A custom app is written in React Native (one codebase for both platforms) or natively in Swift and Kotlin, and connects to Shopify through the Storefront API and Customer Account API, with Checkout Kit handling checkout. You own the code and can build anything: custom bundles, quizzes, member-only drops, deep loyalty features.

It is worth clearing up a common confusion: Hydrogen is not a mobile app framework. Shopify's developer docs call Hydrogen its "headless toolkit": a React-based framework for web storefronts. Brands sometimes pair a Hydrogen storefront with a React Native app, sharing the same Storefront API queries, design tokens and business logic, which keeps web and app consistent. But the app itself is a separate project.

Custom builds cost more up front and need ongoing ownership. If you want to compare the routes for your store, our mobile app development service page explains how we scope builder-based and custom apps.

What really drives the cost

Apart from the builder snapshot above, we are not quoting price ranges: custom quotes depend entirely on scope. These are the factors that move the number:

• Builder vs custom. A recurring subscription versus an upfront build plus maintenance. Over several years the comparison depends on the builder's tier and how much you would customize.
• Feature scope. Catalog browsing and checkout are the floor. Loyalty, subscriptions, reviews, wishlists, personalization, quizzes and account features each add integration work.
• Integrations. Every third-party app (loyalty, subscriptions, reviews, search, ESP) needs an API or SDK that works in a native context. Some Shopify apps only work in the web theme.
• Design. Templated screens versus a custom design system for the app.
• Store fees and accounts. Apple's 99 USD annual program fee and Google's one-time 25 USD fee are small, but they are real line items.
• Ongoing maintenance. OS updates, SDK upgrades, store policy changes and bug fixes continue after launch.
• Marketing the app. Installs do not happen on their own. Budget for install prompts on site, email and SMS campaigns, and app-only offers.

For context on the wider site budget, see our breakdown of what a Shopify website costs.

When a native app makes sense

• High repeat purchase. Consumables, beauty, supplements, coffee, pet food, fashion with frequent drops. If customers buy many times a year, an icon on their phone earns its keep.
• A loyalty program you want to deepen. Points, tiers, early access and member pricing feel natural inside an app and give people a reason to install.
• Drops and limited releases. Reliable push on iPhone matters when timing is the product.
• An existing engaged audience. A sizeable email and SMS list of repeat buyers you can convert into installs.
• Resources to run it. Someone owns the app's content calendar, push strategy and release cycle.

In each case the app is a retention channel, sitting alongside email and SMS. If that is the job, it should be planned with your retention strategy, not as a standalone project.

When it doesn't

• Low purchase frequency. Mattresses, furniture, one-off gifts. Customers will not keep an app for a purchase they make every few years.
• A small or new customer base. An app mostly re-engages people who already know you. With few repeat customers, it has little to work with.
• A slow or leaky mobile site. Fix the site first. It serves every new visitor, and an app cannot compensate for it.
• No one to run it. An app that never sends a useful notification or gets updated quietly loses users.

For these stores, a well-tuned mobile site plus email and SMS, and optionally PWA features for Android push and faster repeat visits, is the better use of budget. Social channels can also do some of the re-engagement work; see our guide to social commerce on Shopify.

A simple way to decide

1. Step 1: Audit mobile speed and conversion on your existing site. Fix the obvious problems.
2. Step 2: Look at repeat purchase rate and how often your best customers order. If they buy several times a year, an app is worth modeling.
3. Step 3: Check your device split. If most mobile revenue is on iPhone, PWA push will reach far fewer people than a native app.
4. Step 4: List the features you need. If a builder covers them and its integrations match your stack, start there. If not, scope a custom build.
5. Step 5: Plan how you will drive installs and what the app offers that the site does not.