Do you actually need a mobile app? — the install-friction tax and when the web wins

At some point almost every growing business says it out loud: "we need an app." It feels like the natural next step — a logo on the customer's home screen, push notifications, a sign that you have arrived. The instinct is understandable and it is almost always reasoned in the wrong order. The right question is never "should we build an app." It is "what job does the customer need to get done, and what is the lowest-friction way to put that job in their hand." Sometimes the honest answer is a native app. Far more often it is the website you already own — and the app would be a wall you pay to build between yourself and the people you are trying to reach.

The reason is friction, and friction has numbers. A native app is the only channel where the customer has to stop, go to a store, agree to download, wait, and grant permissions before they can do anything at all — and they shed at every one of those gates. Industry benchmarks put app-store page-view-to-install at roughly a quarter to a third of viewers [1], and of the people who do install, about one in four abandon the app after a single use, with cross-industry retention falling to the low single digits within thirty days [2]. The home-screen icon you were picturing is, for most of your audience, an icon that was never installed or was deleted inside a month.

This piece is the operator's map of that decision. Not "apps are bad" — they are the right tool for a real set of jobs. The questions that actually matter: what does the install funnel cost you in reach before anyone uses the thing, what can a modern website or a Progressive Web App do that people still think needs native, and what is the short list of jobs that genuinely justify the highest-cost channel you can choose.

Start with the gate nobody prices: getting installed at all. The app store is not a neutral shelf — it is a funnel, and every step sheds people. Industry benchmarks put app-store page-view-to-install at roughly 25 to 34 percent on the App Store and the high-20s on Google Play ^[1]; that is the best case, after the customer already cared enough to find your listing. It compounds with a broader fatigue: the long-standing comScore finding that the majority of smartphone users download zero new apps in an average month ^[3] has never really reversed — attention has consolidated into a handful of apps people already have, and a new icon has to fight its way into a home screen that is effectively full. You are not competing with other apps in your category; you are competing with the customer's unwillingness to install anything at all.

Then comes the gate that quietly undoes the install: retention. Getting downloaded is the start of the problem, not the end of it. Cross-industry benchmarks show roughly a quarter of users abandon an app after a single use, and thirty-day retention collapses to the low single digits — around 3 to 7 percent still active a month after install, with close to half of installed apps uninstalled inside that first month ^[2]. Read those two figures together and the home-screen dream gets honest: of a thousand people who saw your listing, a few hundred installed, a couple hundred opened it once, and a few dozen are still there in a month. Every one of the others is a person you could have served on the open web with no gate at all.

Now the part most "we need an app" conversations get wrong: the gap between native and the web is far narrower than it was, because the web grew up. A modern Progressive Web App — a website built to install to the home screen, work offline, and receive push — closes most of the capability gap without the store funnel. The proof is not theoretical. When Pinterest rebuilt its mobile web experience as a PWA, time spent rose 40 percent, user-generated ad revenue 44 percent, and core engagements 60 percent, with weekly active users on mobile web up triple digits year over year ^[4]. Flipkart's PWA drove a 70 percent increase in conversions, and AliExpress saw new-user conversion rates more than double ^[5]. Twitter Lite, a PWA under 600 KB, delivered 65 percent more pages per session and 75 percent more Tweets while cutting the bounce rate ^[6]. These are companies that could afford any native team on earth choosing the web on purpose — because reach with no install gate beats capability nobody downloads.

None of which means native is dead — it means native has a job description, and you should be able to name yours. The honest triggers for a real app are specific: you need deep or constant hardware access (camera-heavy workflows, Bluetooth, background GPS, sensors); you need genuine offline-first operation in the field, not just cached reads; you need the performance ceiling of compiled code (heavy graphics, games, real-time processing); your business model lives on rich push and daily habitual return where the home-screen icon is the product; or store presence and in-app purchase are themselves the distribution channel. If one of those is true, build the app and build it well. If your real job is "let customers browse, book, order, pay, and check status," that job runs on the web today — and shipping it as an app mostly adds a funnel, a second codebase, and an app-store review queue between you and the customer.

For the markets Felukaa builds in, the install tax is heavier, not lighter, and it points the same way. The region is overwhelmingly mobile-first — Egypt alone counts well over a hundred million mobile connections against a population where most people reach the internet from a phone first ^[7] — but that is mobile-first, not native-app-first. A customer on a mid-tier Android with metered data and limited storage is exactly the person least likely to spend a hundred megabytes and a download wait to try you, and most likely to delete you when space runs short. The thing that already lives on that phone, with zero install, is the browser — and the channel that already owns the conversation is WhatsApp, where a link opens instantly. For most businesses scaling in MENA, the winning first move is a fast, installable web experience wired into the channels customers already use, with a native app reserved for the specific job that genuinely demands one.