Contents
- The short answer: it depends on usage frequency
- App and website compared side by side
- How to calculate an app’s revenue contribution
- The middle ground: progressive web apps and web apps
- Combining both: clear roles for website and app
- Checklist: do you need an app to grow revenue?
- Conclusion
- Frequently Asked Questions
Whether an app or a website generates more revenue depends above all on how often your customers come back. The website almost always wins on reach and first contact; the app wins with regular customers who buy, book or order repeatedly. This article compares both channels soberly, provides a way to calculate your own situation and explains why the answer is often “both, but with clearly defined roles”.
The short answer: it depends on usage frequency
A website gets found; an app gets installed. That difference shapes everything else. New customers usually arrive at the website first, via search engines, ads or recommendations. Hardly anyone installs an app for a one-off purchase. Customers who order weekly, book appointments or collect loyalty points, however, benefit from an app: it is one tap away, they are logged in, and push notifications create reasons to return.
As a rule of thumb:
- Infrequent purchases that need explanation (e.g. furniture, consulting, capital goods): the website is the more important revenue channel.
- Frequent, recurring purchases (e.g. groceries, restaurants, tickets, subscriptions, appointments): an app can carry a large share of revenue from regular customers.
- Services with ongoing use (e.g. customer portals, contract management, service): the app is often less a sales channel and more a retention channel that protects revenue indirectly.
App and website compared side by side
| Criterion | Website / web shop | Native app |
|---|---|---|
| Discoverability | Via Google, ads, links, AI search | Via app stores, usually after first contact on the website |
| Entry barrier | No installation needed | Installation and often registration |
| Return visits | Depends on e-mail, ads, bookmarks | Home-screen icon, push notifications |
| Checkout | Guest checkout, many payment methods | Stored details, Apple Pay / Google Pay, very short |
| Device features | Limited, depending on the browser | Camera, location, NFC, wallet, widgets, offline |
| Fees | Payment provider | Payment provider for physical goods; store commission usually applies to digital content |
| Cost | Usually lower, one codebase | Higher, two platforms plus store maintenance |
A common misconception concerns store fees: for selling physical goods and real-world services, such as restaurant orders or tradesperson appointments, store in-app purchases are not required. Commission mainly applies to digital content and features.
How to calculate an app’s revenue contribution
Instead of generic industry claims, a simple calculation with your own figures helps. Work through five steps:
- Identify regular customers: how many customers buy several times a year, and what share of revenue do they account for?
- Estimate app adoption: what share of these regular customers would realistically install and use an app? Be cautious – not every loyal customer wants yet another app.
- Assess additional purchase occasions: how much could purchase frequency increase thanks to reminders, saved baskets or loyalty programmes? Work with a conservative and an optimistic assumption.
- Subtract cannibalisation: part of the app revenue would have come through the website anyway. Only incremental revenue counts.
- Compare with costs: development, maintenance, hosting and marketing for the app over at least three years.
If the conservative scenario already shows a positive contribution, the decision is usually clear. If the business case depends on optimistic assumptions alone, an optimised website or a web app is often the better first step. For orientation, our price guide puts a simple app or MVP at €5,000–15,000 and a mid-complexity app for iOS and Android with login, payments and integration with existing systems at €15,000–50,000.
The middle ground: progressive web apps and web apps
There are intermediate options between a classic website and a native app. A progressive web app runs in the browser, can be added to the home screen, works offline and – depending on platform and browser – can also send notifications. It avoids building twice and publishing in the stores, but does not quite match the integration of a native app, especially on iOS.
When a PWA is enough is covered in our article on progressive web apps in 2026; for a cost perspective, see web app vs. native app costs. For many companies, a PWA is a sensible test: if usage data shows that regular customers use it frequently, moving to a native app later is worth it.
Combining both: clear roles for website and app
In practice, the most successful setups are rarely either-or. The website handles acquisition and the first purchase; the app handles retention and repeat purchases. For this to work, you need:
- A shared customer account: orders, points and favourites are visible in both channels.
- Targeted app promotion: do not push the app on every visitor; point existing customers to its benefits after their second or third purchase.
- Seamless transitions: links from e-mails or the website open the right screen in the app directly if it is installed. Our article on deep links and web-to-app journeys explains how this works technically.
- App-exclusive value: e.g. a digital loyalty card, faster ordering, real-time order status or click & collect.
For brick-and-mortar retail, our article on retail apps shows how loyalty cards, offers and click & collect work together.
Checklist: do you need an app to grow revenue?
- Your customers buy or use your offer several times per month or quarter.
- There is a clear app advantage over the website, such as speed, loyalty card, notifications or offline use.
- You already have a base of returning customers you can point to the app.
- Device features such as camera, location, NFC or wallet matter for the value you deliver.
- Budget and staff for maintenance and regular updates are planned.
If only one or two points apply, invest first in a fast, easy-to-find website with a smooth checkout.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
The website brings new customers and first purchases; the app grows revenue from regular customers – provided your offer is used frequently and the app delivers tangible extra value. Calculate incremental revenue conservatively and consider a PWA as an intermediate step. If the numbers favour an app, we will prepare a fixed-price offer for you after a free analysis.
Frequently Asked Questions
Do customers spend more in apps than on websites?
App users are often especially loyal customers, so their revenue per head tends to be higher. Partly, though, that is because already loyal customers install the app – what matters is the additional revenue the app actually generates.
Do I have to pay Apple and Google commission on sales in my app?
Generally not for physical goods and real-world services; you can use your own payment provider for those. Commission mainly applies to digital content and features used within the app.
Is a progressive web app enough instead of a native app?
For many use cases with modest requirements for device features, yes. If push notifications, wallet, NFC or very high usage frequency are central, a native app usually offers the better experience.
Should I improve the website or the app first?
In most cases the website first, because it wins new customers and carries the first purchase. An app pays off once you have enough returning customers who benefit from it.