Native, cross-platform or web app: how to choose

Native, React Native, Flutter or a progressive web app. The honest trade-offs, what works on iPhone today and how to pick for a UK audience.

For most UK businesses the right starting point is a cross-platform app or a progressive web app, because you almost certainly need to reach both iPhone and Android users and you’d rather pay for one build than two. Go fully native when the app leans hard on the phone itself: camera processing, Bluetooth devices, heavy graphics, or the newest features of each operating system.

The UK detail that shapes this choice is the split between the two platforms. It is close to half and half here, which is unusual, so “we’ll just do iPhone first” leaves out roughly half your customers.

  • UK mobile use is split almost evenly: 50.14% iOS and 49.85% Android in October 2026, according to StatCounter. Worldwide, Android has 72.36%.
  • Native apps give the best performance and device access at the highest cost. Cross-platform shares most of the code across both stores.
  • A progressive web app is the cheapest route and now supports push notifications on iPhone, but only once the user has added it to their Home Screen.
  • Pick on what the app must do and how customers will find it. Fashion among developers is a poor guide.
iPhone and Android in the UK
50.14%iOS share of UK mobile web use, October 2026
49.85%Android share in the same month
53.93%highest monthly iOS share in the year to October 2026
46.97%lowest monthly iOS share in the same year

Source: StatCounter Global Stats, November 2025 to October 2026

The three options in plain terms

Native means two separate apps, each written in the platform’s own language: Swift for iPhone and Kotlin for Android. Each uses the platform’s own tools and gets every new feature first.

Cross-platform means one codebase that produces both apps. The two main frameworks are React Native and Flutter. React Native was released by Meta in 2015 and is still maintained by it. It is written in JavaScript and renders the platform’s real native components. Flutter is an open-source framework backed by Google, uses a language called Dart, and builds for mobile, web and desktop from a single codebase.

A progressive web app (PWA) is a website built to behave like an app. It opens full screen from an icon, can work offline and can send notifications. There’s no store download: people reach it through a link or your website.

How many of your UK customers use iPhone or Android

StatCounter’s figures for October 2026 put iOS at 50.14% of UK mobile web use and Android at 49.85%. Over the previous twelve months the iOS share moved between 46.97% and 53.93%, so the fair summary is an even split that wobbles month to month. Worldwide the picture is very different: Android had 72.36% and iOS 27.61% in the same month.

iOS share of UK mobile web use, November 2025 to October 2026

Vertical axis starts at 42%, not zero.

Android accounts for almost all of the remainder

Source: StatCounter Global Stats, mobile operating system market share, United Kingdom

View data
 iOS share of UK mobile web use, November 2025 to October 2026
Nov 202549%
Dec 202548.73%
Jan 202649.74%
Feb 202649.42%
Mar 202650.32%
Apr 202651.35%
May 202653.49%
Jun 202651.36%
Jul 202653.93%
Aug 202651.43%
Sep 202646.97%
Oct 202650.14%

StatCounter measures web browsing, so it’s a proxy for what people carry, and your own customers may differ. Check your website analytics for the split among your actual visitors before deciding. A business selling to trades may see more Android. A premium consumer brand in London may see more iPhone.

Either way, a UK app that ships on one platform only is choosing to ignore a large share of the market.

When native wins

  • The app depends on device hardware or deep system features: advanced camera work, Bluetooth accessories, health sensors, augmented reality, background processing.
  • Performance is the product, as with games, video editing or anything animation-heavy.
  • You need each platform’s newest features on the day they launch.
  • You only need one platform, for example an internal app for staff who all carry company iPhones.

The cost is two codebases, two sets of skills and two lots of maintenance. Every feature is built twice and the two versions drift apart unless someone polices it. Maintenance is the cost people forget: see what it costs to keep an app running.

When cross-platform wins

This is the default for most business apps: bookings, ordering, loyalty, customer accounts, field staff tools, anything that is mainly forms, lists and content from a server. One team builds one codebase, and both stores get the same features on the same day.

The trade-offs are real but manageable. Now and then a feature needs a piece of native code written for each platform. You depend on the framework and its community keeping pace with Apple and Google. And very demanding graphics or unusual hardware can still be awkward.

Choosing between React Native and Flutter matters less than people argue. React Native suits teams who already work in JavaScript and React on the web. Flutter gives tight control over how every pixel looks across platforms. The quality of the team matters more than the framework. For what the people cost, see our post on app development costs in the UK.

When a progressive web app is enough

A PWA is one build that runs everywhere a browser does. There’s no developer account to pay for and no store review to wait on, and you can release an update whenever you like. For internal tools, customer portals, booking pages and anything people reach from a link, it’s often all you need. It also happens to be the natural route when you’re replacing a spreadsheet with a custom app for your own staff.

The weak points are discovery and the iPhone. People search the App Store and Google Play for apps, and a PWA isn’t there by default. On Android, Google’s Trusted Web Activity lets you open your web app full screen inside an Android app shell, which is the usual way of packaging one. On iPhone, the user has to add it to the Home Screen themselves from the share menu, and many don’t know how.

What PWAs can do on iPhone in 2026

More than their reputation suggests. Apple’s WebKit team added web push notifications for Home Screen web apps in iOS and iPadOS 16.4 in 2023, along with app icon badges. There are conditions: the web app must be added to the Home Screen first, and the permission prompt has to follow a direct tap by the user, such as a “subscribe” button. A PWA opened in a Safari tab can’t send push notifications.

From iOS 26, WebKit says that “by default, every website added to the Home Screen opens as a web app”, which removes one source of confusion. Since iOS 16.4, other browsers on iPhone have also been able to offer Add to Home Screen.

One piece is still moving. The Competition and Markets Authority designated Apple with strategic market status for its mobile platform in October 2025, and its published programme lists the removal of Apple’s WebKit restriction on browsers as upcoming work. If that happens, web apps on iPhone could gain capabilities over time. Nothing has been decided, so don’t plan around it.

A side-by-side summary

Native Cross-platform Progressive web app
Codebases Two One, with occasional native extras One
In the app stores Yes Yes Not by default
Device features Everything Most things What the browser allows
Push notifications on iPhone Yes Yes Yes, after adding to Home Screen
Releasing updates Store review each time Store review each time Whenever you like
Relative cost Highest Middle Lowest

How to decide

Choosing native, cross-platform or web

Step 1 of 4

Device needs

List what the app must do with the phone itself, such as camera, Bluetooth or sensors.

Step 2 of 4

Discovery

Decide whether people will search a store or arrive from a link or QR code.

Step 3 of 4

Audience

Check the iPhone and Android split among your own website visitors.

Step 4 of 4

Start small

Test demand with a web app or cross-platform first version before going further.

  1. List what the app must do with the phone itself. If the list is “show content, take input, send notifications”, you don’t need native.
  2. Ask how people will find it. If they’ll search a store, you need a store app. If you’ll send them a link or a QR code, a PWA may do.
  3. Check your own audience split in your analytics.
  4. Start smaller than you think. A PWA or a cross-platform first version tests demand cheaply. Our guide to validating a business idea covers that step.

Before any of this, it’s fair to ask whether you need an app at all. Sometimes existing software does the job, a question we cover in build or buy.

Common questions

Can we start with a PWA and move to a store app later?

Yes, and it’s a sensible path. The back end, the design and much of the thinking carry over. If the PWA is built in React, moving to React Native reuses skills and some code as well.

Will a web app feel slow?

Not if it’s built well. Speed on the web is measurable, and the same standards apply as for any site, which we explain in Core Web Vitals in plain English.

Do cross-platform apps get rejected by the app stores?

No more than native ones. The stores review what the app does and how it behaves. They don’t mark it down for the framework it was built with.

If you’d like a view on which route fits your project, our mobile and web applications team is glad to talk it through.

Sources

→Keep reading

Related guides.

All insights
Software reviews

Lovable vs Bolt vs v0: what AI app builders can build, and where they stop

Lovable, Bolt and v0 compared on published prices, credits and features, with an honest look at where AI app builders stop and real engineering… Read
Apps & software

Publishing an app on the App Store and Google Play as a UK company

What a UK limited company needs to publish on the App Store and Google Play: D-U-N-S, fees, review, privacy forms, account deletion and trader… Read
Apps & software

What it costs to keep an app running after launch

Why an app keeps costing money after launch: yearly iOS and Android updates, store deadlines, SDK upgrades, hosting and support, and how to budget. Read

→Get in touch

Got a question? Ask us.

Tell us what you’re trying to do. Every project starts with a free audit: someone who does the work replies with a few ideas, an honest view and a written plan with prices.

What happens next

  1. 1
    You send the formIt takes about two minutes.
  2. 2
    We do our homeworkWe look at your website and your market.
  3. 3
    You get a short planWhat we’d do first, with prices. Yours to keep.
  • Free, with no obligation
  • We won’t add you to a mailing list

We only use your details to reply to you. See our privacy policy.