# Ecommerce mobile app or PWA: when your online store needs an app

Ecommerce mobile app or PWA? What an app costs, when it pays off, what a PWA can do on iPhone and Android, and how to reach mobile shoppers in Europe.

Source: https://cloudcart.com/en/blog/ecommerce-mobile-app-vs-pwa · CloudCart · 2026-11-09

In short: an ecommerce mobile app pays off when thousands of regular customers buy every month and you have a budget for two platforms and ongoing maintenance. For most online stores, a fast mobile site, a PWA (Progressive Web App) and Web Push reach the shopper on the phone for a fraction of the cost. Across Europe, Android carries 63.67% of mobile traffic and iOS 36.32% (StatCounter).

This guide is for store owners across Europe deciding whether to commission a shopping app, and shows what CloudCart, the ecommerce platform for stores across Europe, gives the shopper and the merchant. How to prepare the mobile site itself is covered in [mobile ecommerce: 12 checks for your store on a phone](https://cloudcart.com/en/blog/mobile-version-online-store).

## Mobile app, PWA or mobile site: what is the difference

A native mobile app is a separate program the customer downloads from the App Store or Google Play. A PWA (Progressive Web App) is your store's website, which the customer adds to the phone's home screen and opens from an icon like an app. A mobile site is the same website laid out for a small screen and opened in the browser. All three show the same catalog, but they differ in cost, in how they reach the customer and in who has to take the first step.

| Criterion | Mobile site | PWA | Native app |

| How it reaches the customer | Google, ads, links | From the site, after "Add to Home Screen" | After a download from the App Store or Google Play |

| Visibility in Google | Full, it is the site | Full, it is the same site | Weak: content inside the app does not replace the site's pages in search |

| Notifications to the customer | Web Push in the browser (not on iPhone) | Web Push, on iPhone from iOS 16.4 | Push through the phone's system |

| Icon on the phone | No | Yes | Yes |

| Separate development | No | No, if the platform provides the manifest | Yes, for iOS and Android |

| App store fees | None | None | Apple: USD 99 a year; Google Play: USD 25 once |

| Updates | With every change to the site | With every change to the site | A new version, a store review and a download by the customer |

The mobile site is where new customers arrive. The PWA and the app sit on top of it and serve mainly people who have already bought, so the decision about an app depends on repeat purchases.

## When an ecommerce mobile app is worth it

An ecommerce mobile app is worth it when a large share of revenue comes from customers who return often, and when the app gives them something the website cannot. Check the five conditions below before you ask for a quote. If you meet fewer than three, the money for an app will earn more in advertising, email campaigns and site speed.

- Frequent purchases. Customers buy every month or more often: groceries, cosmetics, pet food, consumables. When people buy once every two years (furniture, appliances), the app stays unopened.

- A large base of regular customers. Thousands of people with more than one order a year. You can count them in your customer data and segments; the approach is described in the guide to customer loyalty and repeat purchases .

- A feature that needs the phone. A barcode scanner for quick reorders, a loyalty card used in your physical shop, a reorder from a saved list in a few taps.

- A maintenance budget. Every new version of iOS and Android can require changes, and the app stores change their rules. Maintenance is a cost every year.

- A reason to download. An app-only discount, early access to sales, parcel tracking. Without a reason, customers do not download a store's app.

Selling in several EU countries does not by itself call for an app: a shopper in Austria or Poland finds you through Google in their own language, so a store per country with its own language and currency does more for reach.

## How much an ecommerce app costs: the costs outside the quote

The cost of an ecommerce app is made up of development, the Apple and Google fees, and maintenance that continues every year. The development price depends on the agency and the features, so compare quotes against the same list. The app store fees are fixed and public:

- Apple Developer Program: USD 99 per membership year, in local currency where available ( Apple Developer ). Without a membership, the app cannot go into the App Store.

- Google Play Console: a one-time registration fee of USD 25 ( Google Play Console Help ).

For an online store selling physical goods, Apple takes no commission on sales in the app. Under rule 3.1.3(e) of the [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/), physical goods are paid for with methods outside in-app purchase, for example Apple Pay or a card. The same guidelines, in section 4.2, require an app to offer more than a "repackaged website". A site wrapped in an app frame risks rejection in review.

In the EU, iPhone users can also install apps from alternative app marketplaces or directly from a developer's website under the Digital Markets Act ([Apple, DMA and apps in the EU](https://developer.apple.com/support/dma-and-apps-in-the-eu/)). These routes come with their own eligibility criteria and terms, and the App Store remains where most shoppers look for a store's app, so budget for the Apple membership either way.

Put these on the list for the quote: screens for iOS and Android, catalog, cart and payment, customer login, push notifications, analytics, publication in both stores, testing on several phones, store listings in every language you sell in, and 12 months of maintenance.

> 0% commission 0% of your sales, from the site and from an app CloudCart takes no percentage of your revenue, so orders from your own app built on the Storefront API carry no platform commission either. How 0% commission works →

## How to calculate whether a mobile app will pay off

An app pays off when the extra profit from repeat orders placed through it covers development and maintenance over the same period. You run the numbers with your own data from the admin over a fixed period, for example 24 months.

- Add up the total cost. Development + maintenance for 24 months + 2 × USD 99 for Apple + USD 25 for Google + the advertising you will spend to get customers to download the app.

- Decide which customers will download it. Realistically, only regular customers. Take their number from the segment with more than one order.

- Estimate the extra orders. Not every order in the app is new: some of them the customer would have placed on the site anyway. Count only the additional ones.

- Work out the profit from them. Extra orders × average order value × your margin after shipping and payment costs.

- Compare. If the profit from step 4 is lower than the cost from step 1, start with a PWA and Web Push and test the interest without development.

An example with illustrative numbers: a store with 2,000 regular customers expects 500 of them to download the app and place 2 extra orders a year each. With an average order of €40 and a 30% margin, that is 500 × 2 × 2 years × €40 × 30% = €24,000 profit over 24 months. If the total cost from step 1 is above that, the app loses money. Replace the numbers with your own from the reports in the admin.

## What a PWA is and what it can do on Android and iPhone

A PWA (Progressive Web App) is a website with a manifest and a service worker, which the browser lets the customer add to the home screen and open full screen like an app. The manifest is a file with the store's name, icon and colours. The service worker is a script that runs in the background and receives push notifications. To the customer a PWA looks like an app; to you it remains the same website, with no separate development and no review by Apple or Google.

What a PWA can do depends on the phone. On Android, Chrome can show an install prompt. On iPhone and iPad there is no such prompt, and the customer adds the site manually from the Share menu → "Add to Home Screen". From iOS and iPadOS 16.4, home screen web apps get Web Push and the Badging API ([WebKit](https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados/)).

| Capability | Android (Chrome) | iPhone and iPad (iOS 16.4 and later) |

| Install prompt from the browser | Yes, as a banner or a dialog | No, only manually from "Share" |

| Web Push notifications | Yes, in the regular browser too | Yes, only for a site added to the home screen |

| Asks permission for notifications | Yes | Yes, only after the customer taps a button |

## The limits of a PWA on iPhone

The main limit of a PWA on iPhone is that the customer has to add the store to the home screen before receiving notifications, because a regular Safari tab cannot ask for push permission. That is two steps more than on Android.

How much this matters depends on your market. Across Europe, iOS has 36.32% of mobile traffic according to [StatCounter](https://gs.statcounter.com/os-market-share/mobile/europe), and the share differs a lot from country to country. Your own store may differ again, so make the decision from the device data in Google Analytics, split by country if you sell across borders.

The second limit affects ads. A customer who arrives from an Instagram, Facebook or TikTok ad views your store in the app's built-in browser. There they cannot subscribe to Web Push and cannot add the site to the home screen. So in the first email after an order, suggest adding the store to the home screen and explain how it works on iPhone.

Important: browser rules for PWAs change with new versions of iOS and Android. Check the current behaviour on your own phone after every major system update.

## Push notifications: from an app, from a PWA and with Web Push in CloudCart

You do not need a mobile app to send push notifications: Web Push sends short messages from the browser to the phone and the computer, even when the site is closed. In CloudCart you turn the channel on in Marketing → Channels → Channels setup → Web Push and use it in campaigns. When it works and when it does not is covered in the guide to [Web Push notifications for an online store](https://cloudcart.com/en/blog/web-push-notifications-ecommerce).

- Install the Web Push channel. The channel is not installed by default. Install it and activate it from its card on the channels screen.

- Set up the invitation. In the channel's Settings, write the text and buttons of CloudCart's pop-up, shown before the browser's own prompt. A customer who declines your pop-up can be asked again later; the browser never repeats its prompt after a refusal. You can show the invitation only after a successful order.

- Write short. The title is up to 63 characters and the text up to 128. The subscriber's name and the store name are available for personalisation.

- Add Web Push to a campaign. In campaigns ( Marketing → Campaigns ), add a "Web push notification" step for an abandoned cart, a back-in-stock product or a promotion. The next step can depend on whether the customer clicked the link.

- Add a fallback channel. For customers without Web Push, the campaign continues with email, SMS or Viber. How to combine them is covered in email, SMS, Viber and Web Push campaigns .

- Turn on the system messages. The templates for an order status change and for fulfilment send the customer a notification when the order ships.

Marketing notifications, like your newsletter, need the customer's consent under the GDPR, and the browser asks for permission on top of that. The strongest push notification for a store is the abandoned cart reminder, because the customer has already chosen the product. How to set up the whole sequence is on the [abandoned carts](https://cloudcart.com/en/abandoned-carts) page.

## What CloudCart gives the customer on a phone

CloudCart storefronts are responsive and ship with a PWA manifest by default, so customers can add your store to the home screen without separate development. The themes screen shows the active theme in a desktop and a phone view, and you change colours and fonts in Design. Everything themes and storefronts can do is on the [ecommerce website design](https://cloudcart.com/en/design) page.

> CloudCart Pay Apple Pay and Google Pay with a 0% fee until 31 December 2026 On a phone, Apple Pay or Google Pay saves the customer typing a card number, and in the mobile site and the PWA they pay in the same checkout. Businesses registered in 30 European countries (the EU, Norway, Switzerland and the UK) can apply. How CloudCart Pay works →

If you still decide to build your own app for customers, it connects to the store through the Storefront API. This is the GraphQL API that Nitrogen headless storefronts use: catalog, cart, customer accounts and orders stay in the CloudCart admin. App purchases can be reported to Google Analytics 4 from the server through the Measurement Protocol API secret in the Google Analytics app settings, with the buyer's consent. The developer documentation is on the [developer API](https://cloudcart.com/en/developers) page.

> Store with an AI assistant A Nitrogen storefront built with an AI agent If you want a mobile experience entirely to your own design, build a Nitrogen storefront with an AI agent first and test the idea on the site before you pay for an app. Store with an AI assistant →

Step by step: [storefront design with Nitrogen and an AI agent](https://cloudcart.com/en/blog/nitrogen-ai-storefront-design).

## CloudCart Admin: the mobile app for the merchant

Every merchant needs a mobile app, even when their customers do not. CloudCart Admin is CloudCart's app for iPhone and Android, with which the owner and staff manage orders from the phone. It is one app for all CloudCart stores and does not publish your store in the App Store. The app costs €0 and needs iOS 16.4 or later on iPhone.

| What you do from the phone | Exactly what |

| Notifications | A push for every new order (number, customer name and amount) and for every status change |

| Orders | Change the status, mark as paid, refund, fulfil with a tracking number |

| Shipping label | Create a shipping label with the store's courier, and change the courier, shipping method or pickup point |

| Dashboard | New and abandoned orders, out-of-stock products, revenue for a chosen period |

| New orders | Place a phone order for a customer and follow up on abandoned carts |

Notifications go to every phone signed in to the store, and each phone can switch them off on its own. The product catalog, settings and design stay in the web admin, which opens from the app in the browser. How to download it and sign in is on the [CloudCart Admin mobile app](https://cloudcart.com/en/offer/admin-app) page.

## Mistakes when choosing a mobile app

- An app before a mobile site. New customers arrive on the site from Google and ads. A slow or awkward mobile site loses orders that an app does not win back.

- A budget without maintenance. The development quote covers the first version. Updates for new iOS and Android versions and new features come every year.

- Push as the only channel. With an app and with Web Push alike, some customers decline notifications. Email and SMS remain the basis of repeat purchases.

- One language for many markets. If you sell in several countries, the app needs the same languages, currencies and prices per country as your stores, or it serves only one market.

- A decision without data. Before you order an app, check in Google Analytics the share of phones, of iPhones and of returning customers in your own store.

> New store €1/month for the first 3 months A responsive theme, a PWA manifest, Web Push and CloudCart Admin for your orders come with the store from day one, with no separate development for the phone. Create a store for €1 →

Questions about mobile, PWA or Web Push setup in your store: write to support@cloudcart.com.

## Frequently asked questions

**Do I need a mobile app for my online store?**

Most online stores do not. A good mobile site, a PWA and Web Push reach the customer on the phone without separate development. An app makes sense with frequent purchases, thousands of regular customers and a budget to maintain iOS and Android versions every year.

**How much does it cost to build an ecommerce app?**

The development price depends on the agency and the features, so compare quotes against the same list. The fixed fees are USD 99 a year for the Apple Developer Program and a one-time USD 25 for Google Play Console. Add maintenance and the advertising you need to get customers to download the app.

**What is a PWA in ecommerce?**

A PWA (Progressive Web App) is a store website the customer adds to the phone's home screen and opens like an app. It has a manifest with the name and icon and a service worker that receives push notifications. For the store it is the same website, with no separate development and no review by Apple or Google.

**Does a PWA work on iPhone?**

Yes. On iPhone the customer adds the site manually from Share → "Add to Home Screen", because iOS shows no install prompt. From iOS 16.4, a home screen PWA gets Web Push and a badge on the icon. In a regular Safari tab, the site cannot ask for notification permission.

**PWA vs native app: which is better for ecommerce?**

A PWA is better for most stores: it is your website on the home screen, updates with the site and stays visible in Google. A native app comes from the App Store or Google Play and needs development for two platforms, Apple and Google fees and a download by the customer. It suits stores with many frequent repeat buyers.

**Does Apple take a commission from an online store app?**

Not for physical goods. Under rule 3.1.3(e) of the App Review Guidelines, physical goods are paid for with methods outside in-app purchase, such as Apple Pay or a card. The USD 99 yearly fee for the Apple Developer Program still applies.
