Somebody, somewhere, someday will quote you a mobile traffic number.
What share of web traffic is mobile? (2026)
Cloudflare counts HTTP requests rather than page views. Blog aggregator figures are early 2026.
Statista’s read of Statcounter has mobile at 51.48% in Q2 2026, down from 62.73% a year earlier. Cloudflare counts HTTP requests instead of page views and lands around 43%. Plenty of 2026 articles still cite 62% to 64%. Every one of those is defensible, which means whichever number supports the decision you’d already made is available to you.
Where it does turn
Half the mobile web is very slow. Per the HTTP Archive Web Almanac using Chrome field data, 48% of mobile origins passed all 3 Core Web Vitals against 56% on desktop. The May 2026 Chrome UX Report reading, which blends devices, puts 55.9% of origins passing. Whichever way you look at it, roughly half of everything published fails a basic performance bar on a phone.
That’s the actual competitive landscape. A carefully built responsive web app beats a hastily built native one on the metrics users feel, and it does it without an app store review queue.
The decision tree
- Do you need Bluetooth, NFC, USB, or deep OS integration?
- YesNative. Nothing else clears this.
- NoKeep going.
- Do you need reliable background sync, or offline-first on iPhone?
- YesNative. iOS PWAs still have no background sync.
- NoKeep going.
- Is App Store presence a real acquisition channel for you, or a requirement of your buyer?
- YesNative, or a wrapper. Apple blocks PWAs from the App Store under guideline 4.2.2.
- NoKeep going.
- Do you sell subscriptions or digital goods?
- YesWeb first, deliberately. 15–30% store commission on every transaction is a tax on a business model you haven’t proven yet.
- NoKeep going.
- Everything else
- ThenResponsive web. Set the trigger that would push you to native now, while you’re calm, and write it down.
What native costs you
| Two native codebases | 2x the engineering, 2x the QA, 2x the releases |
| React Native / Flutter | ~1.3x a web build, plus platform quirks |
| App Store review | Days per release, occasional rejections |
| Store commission | 15–30% on in-app purchases |
| Install friction | Every user must decide to download first |
| Update cycle | Users on old versions for months |
Against that: since iOS 16.4, home screen web apps on iPhone can send push notifications, and as of iOS 26, every site added to the Home Screen opens as a web app by default. Still missing: background sync, Bluetooth, NFC, and App Store distribution.
The cure cured enough symptoms but not all. Apple has a well-documented commercial interest in keeping it just sick enough.
The truth
Most founders asking this question just want permission to build the native app, because native feels like a real company. The expensive mistake isn’t choosing native. It’s choosing 2 separate native codebases before you know which features are actually useful.
Working out which grass is greener between those 2? Book a free discovery call, and we’ll bring our best gardeners.




