I don't download your app: the web version is enough for me

You are on a hotel website. You want to check if there is availability for the weekend. You find the date, select the room, click "Book"-and the banner appears:

. "Download our app to continue.".

Close tab.Go to Booking.

This scene is repeated millions of times every day. And each time, a company loses a customer it was about to convert. Not because of lack of interest, not because of price, not because of competition. To a download.

The problem is not that apps are bad or useless. The problem is that asking someone to do it at a time when they haven't yet decided for themselves is one of the most costly customer experience mistakes a business can make -- and in 2026 many are still making it.

Asking for a download is asking for a commitment

When you show a "download our app" banner, an instant evaluation between effort and perceived value is triggered in the user's head.

The effort is concrete and immediate: open the App Store or Google Play, search for the app, wait for the download, create an account, accept the terms, grant permissions. Each step is a potential point of abandonment. Each additional tap is an opportunity to change your mind.

The value, on the other hand, is still uncertain. The user doesn't know if the app will be worth the time invested. He doesn't know you well enough. He still doesn't trust you enough. Yet you are asking him to take up space on his phone -- a space he feels is his own, personal, cared for -- before you have even shown him anything concrete.

Space on the phone is a matter of trust

Think about how you choose the apps you keep installed. You probably have about 20 or 30 active ones. The others you've downloaded, used once, then uninstalled -- or worse, forgotten in a folder you never open.

Users have already experienced this too many times. They have become selective. And your app -- if you're not Netflix, Spotify or the bank -- probably doesn't pass that filter on the first encounter, before a relationship has formed.

The paradox is that many companies think the app creates loyalty. And it does, but only if the user gets there. Trust is built before the download, not after. If you force someone to download before you give them value, you are putting the cart before the horse.

An app's onboarding funnel is a sieve

According to recent estimates from companies specializing in mobile attribution such as Appsflyer and Adjust, a significant proportion of users who begin the process of installing an app do not complete the onboarding process. The abandonment rate during onboarding can be extremely high, especially for service apps that are not in the user's top of mind at the time of first contact.

This is not a problem with the user. It is a problem in the way the funnel is constructed.

When a native app makes sense - and when it doesn't

This is not a crusade against native apps. Some exist for specific reasons and work well in that specific context.

The legitimate cases

A native app makes sense when the user uses it every day or nearly every day. A fitness tracking app, banking, a social network, the main messaging platform. These tools access the phone's hardware--continuous GPS, camera, biometric sensors--and offer critical notifications that the user wants to receive in real time. In these cases, the download justifies itself, because the value is clear and everyday.

It also makes sense for already loyal communities: if you have passionate users who freely choose to download you, great. The app becomes an extension of an already established relationship, not a prerequisite for starting it.

The cases where the app is an unnecessary obstacle

The problem arises when companies replicate this model in completely different contexts.

A restaurant that requires downloading the app to see the menu. A hotel that requires the download to make a reservation. A professional firm that sends customers to the store to request an appointment. An e-commerce store with a catalog that rarely changes.

In these cases, the user will not return often enough to justify the busy place on the phone. The service is occasional, and a mobile-optimized site does exactly the same job-often better, because it requires no additional onboarding and works immediately.

The hidden cost to business

There is one aspect that many business owners underestimate: developing and maintaining a native app costs much more than a well-optimized web experience.

You have to develop and update two separate versions - iOS and Android - with different logic, different system APIs, different design guidelines. You have to manage compatibility with each new operating system update. You have to go through store review every time you release a change. You have to track crash reports and optimize performance on devices of different generations.

According to estimates gathered from platforms such as Clutch.co and GoodFirms, the initial cost of developing a native iOS and Android app is quickly measured in the tens of thousands for something functional--to which must be added the cost of ongoing maintenance. A Progressive Web App or optimized web experience can achieve equivalent results for many use cases at a fraction of that cost.

The modern web is powerful enough

There is a widespread belief that native apps are superior to the Web in quality of user experience. It was true ten years ago. Today it is much less true than many assume.

What the web can do today

Modern browsers support features that were once exclusive to native apps:

• Web Push API: push notifications directly from the browser, without going through any store
• Service Workers: offline access and intelligent content caching for fast experiences even with unstable connection
• Progressive Web App (PWA): the user can add the site as an icon to the phone's homescreen, with a full app-like experience, without any steps on the store
• Hardware access: camera, microphone, geolocation, gyroscope - all accessible via browser through standard APIs

Google Chrome, Safari, and Firefox support these standards on all modern devices. The technical gap between web and native apps has narrowed to the margins. And those margins concern very specific use cases - not booking a table or requesting a quote from a firm.

WhatsApp: the channel that requires no additional downloads

There is one aspect that is often overlooked: the most direct channel for customer service and communication with clients is neither a proprietary app nor a dedicated web app. It is WhatsApp.

WhatsApp is already installed on almost all your customers' phones. In Italy and throughout Europe, penetration among smartphone users is extraordinarily high. No one has to download anything. No accounts to create. No new interfaces to learn.

For a business that wants to communicate frictionlessly, this is a huge competitive advantage. And that's exactly why tools like Leader24 exist: they allow businesses to manage customer service via WhatsApp in an automated and scalable way, without ever asking the customer to take even one additional step beyond what they already do every day.

Friction kills conversion

There is one UX principle that always applies, in any digital context: users choose the path of least resistance.

It's not laziness. It is rationality. If two services offer the same thing and one requires an extra step, the user goes to the one that requires less. Every time.

The principle of least effort applied to customer service

Imagine that one of your potential customers wants to contact you for quick information. She has two options: send a WhatsApp message to the number she found on the site, or download your app to use the proprietary chat.

The answer is obvious. And if you don't offer an immediate channel but your competitor does, you already know how that goes.

The so-called principle of "invisible design"-or Zero UI-says that the best interface is the one the user doesn't notice because it works exactly as they expect. Proprietary apps developed for occasional services are often the opposite of this principle: they are an additional interface that the user has to learn, at a time when he or she would just like to solve a problem.

Onboarding is not the time to ask for too much

The worst time to ask for engagement is when the user does not yet know you. And in the vast majority of cases, the first contact between a business and a potential customer occurs well before any loyalty has been formed.

In that moment, the goal is not to get an app downloaded. The goal is to answer the customer's question as quickly and naturally as possible. Turn that first contact into a positive experience. Only after that - if and when a relationship has been built - does it make sense to propose a further step.

Companies that have figured this out are investing in conversational experiences that are already accessible, not proprietary apps that need to be built and maintained. They qualify leads via chat, answer frequently asked questions automatically, collect leads - all within channels the customer already uses. At Leader24 you can see how this approach is being applied in very different industries, from hospitality to professional firms to e-commerce: the common thread is to eliminate friction on first contact, not add it.

The right question to ask yourself before developing an app

If you are considering creating an app for your business, or if your customer experience strategy depends on a download, stop for a moment and honestly answer this question:

How often do my customers really need to interact with me through a dedicated tool? .

If the answer is "every day, for something that requires hardware capabilities that only a native app can provide," then it makes sense. If the answer is "a few times a year, for operations that a mobile browser handles perfectly," then you're building a barrier between you and your customers-and you're investing significant resources to do so.

The web is mature. WhatsApp is on almost every phone. Modern browsers are powerful. Customers are rational and impatient. The combination of these elements should drive every decision about your customer experience in 2026.

Forcing downloads is not a loyalty strategy. It is a filter that keeps out customers who might have converted-and who often convert from those who chose not to test them.

Try Leader24 Free for 30 Days