Where native still wins
Writing in December 2021, a self-described "web guy" set out to catalog the concrete reasons a business might choose a native app over a website, so the list could be revisited later and checked for relevance. The focus is strictly on advantages that are distinct or at least perceived as distinct versus the web. Subjective claims like "faster to develop" or "more intuitive" are excluded, and so are the web's own strengths—its open standardized platform, backward compatibility, cross-platform reach, and URLs. What follows is the native side of the ledger.
The home-screen icon
Presence on the device is a mindshare question: the icon sits in front of the user every time the phone is picked up. A widely cited eMarketer report from a few years earlier suggests 90% of phone usage happens in apps rather than mobile browsers, though that figure carries acknowledged gray area. Making an app theoretically puts a business inside that 90% instead of the remainder.
When reach matters most, the best play is often both: a web app for shareability and searchability via URLs, plus a native app for a strong position on the device. The author's own home screen is dominated by apps that exist in both forms—Google Calendar, AccuWeather, Google Maps, Spotify, Notion, Front, Pocket Casts, Instagram, Discord, Twitter, GitHub, Slack, and Gmail.

Mitigation: iOS and Android both offer "Add to Home Screen" for websites, but it is buried and rarely used. Chrome on Android goes further with a Native App Install Prompt for Progressive Web Apps meeting extra criteria, such as at least 30 seconds of site interaction. That levelling tool would work best with better Apple support for PWAs. Authors have little direct control. Build tools such as Flutter, which target web and native from one codebase, are another route.
Launch speed, and why it's overstated
Native apps keep much of what they need locally, so they don't fetch it from the network at open. But the advantage is only partly real: downloading an app is itself a download of resources. The web caches by default and supports more advanced caching through Service Workers, so PWAs are competitive and native isn't automatically faster.
Ad blocking and data collection
Mobile ad blockers are plentiful—Block Bear, Adblock Plus, AdGuard, Clario, 1Blocker, Purify, Ka-Block!, and AdLock on iOS; Adblock Plus, AdAway, AdLock, and Block This on Android. They operate only in mobile web browsers, not inside native apps, so blocking ads in native apps is essentially not possible. A product built on ads or tracking will generally fare better natively—assuming it can attract comparable traffic, which is questionable.
The author hesitates to list "more secure" as a reason, since users exercise so little control over how native resources load. Still, app-store approval before distribution does provide a degree of protection the web lacks.
Mitigation: Let ad and tracker blockers work with native apps.
Persistent login
This one carries weight. A native app keeps you logged in until you log out or a special event occurs, such as a password change on another device. Web apps lose login state more often than one would like, shaping a subconscious impression of the product. On iOS specifically, client-side cookies are capped at 7 days. If there were a 30% chance of having to log in again, usage would drop sharply—perhaps good for the user, but not how a business sees it.
There's a further wrinkle: being logged in on a phone's primary browser doesn't guarantee login inside another app's in-app browser context, whereas native apps often intercept links and always open them in their own context.
Mitigation: No clean answer exists; it's largely trickery. Long cookie expiration dates help somewhat (six months is about the ceiling). Another option is storing a JSON Web Token (JWT) and performing rolling re-authentication behind the scenes, and a Twitter thread cited in the source collects further approaches. Easier sign-in—oAuth, magic email links—helps, but doesn't reproduce the always-logged-in feel.
Platform-consistent look and feel
"Native feel" usually means fast and smooth, but also visually consistent with the rest of the platform. Apple's SwiftUI, for example, builds native apps from pre-built Apple-style components. Matching that on the web takes serious work that native development gets "for free."
Mitigation: Platform owners could publish UI kits that bring their design language to the web, along the lines of Google's Material. The web version of Material, however, is not ready and is only a "planned" release.
No competitor a tap away
There's a sentiment that a browser is the wild west—users can go anywhere—while inside your native app they stay where you want them. A browser shares turf with countless other apps; a native app keeps users on home ground.
Mitigation: Get over it. Hiding the existence of competitors isn't a sound business strategy, and hopping across a shared, standardized, open platform is precisely the web's strength.
Full API access
The web can only hope for parity with native API access—camera, photos, GPS, push notifications, contacts, and so on. Native gets APIs first; the web may follow years later, if at all. Developers can be forced into native work when a crucial API is missing, and push notifications are the prime example. They can be annoying, but they are heavily used and often a business requirement, and they suit many apps well ("Your turn is coming up in 500 feet," "Your driver is here," "Your baggage will be arriving on carousel 9"). If solid push is essential on iOS, the web is not an option.
Mitigation: Give the web feature parity with device APIs, launching new APIs on both simultaneously.
App-store discoverability
A single, exclusive storefront on a platform offers free exposure. Build the best Skee-Ball game and good reviews may put you atop the "Skee-Ball" search, capturing most of that niche. The web sea is far larger, SEO is harder, and advertising and marketing are expensive, so a developer may pick native simply to be a bigger fish from day one.
Competitive markets cut the other way: a music-listening app will never beat the major players, especially when the platform maker fields its own app. There the web's wider audience may offer better odds.
Mitigation: Allow web apps into app stores.
Straightforward offline support
On the web, offline capability comes only through Service Workers. They're impressive, but not especially easy to implement, particularly when the goal is a truly offline experience for an app that otherwise leans heavily on the network. Native apps depend less on the network for everything: core assets are already local, so a game that doesn't need connectivity works offline, and apps that do need it can typically fall back on last-saved data.
Mitigation: Make building offline web apps easier.
The closing note: building for the web is the smart play for most app situations, but the case for native is thick enough that businesses choosing it is no surprise. The most successful operations run both, despite the extreme cost. The hope is that the situation evolves the way responsive design did—toward websites becoming the obvious and only choice for any kind of app. A related discussion appears in ShopTalk 497: The State of Native Apps and Web Apps in 2022 with Thomas Steiner.



