Articles

Mobile apps 9 min read

Native vs cross-platform vs PWA: how to choose your company’s app

Native vs cross-platform vs PWA: what each can do on iPhone and Android today, what it takes to maintain and how to choose by use case. Comparison table inside.

André Valle Ortega Founder, Flouvia

Before design and budget, an app for your business starts with one choice: native vs cross-platform vs PWA. All three reach your customer’s or your team’s phone, but they can’t do the same things, they don’t ship the same way and they don’t cost the same to maintain. Here is each path in plain terms, what it can do on iPhone and Android today and how to choose by use case.

Three paths, in plain terms

Native: one app per platform, in Swift and Kotlin

It’s written in each platform’s own language: Swift, with SwiftUI, for iPhone; Kotlin, with Jetpack Compose, for Android. That means two codebases and, almost always, two specialties on the team. In return, it gets everything Apple and Google ship from day one: Bluetooth, NFC, sensors, widgets, background work and system payments. It has the fewest layers and takes the most work per screen.

Cross-platform: one codebase with React Native or Flutter

With React Native or Flutter you write the app once and ship it to the App Store and Google Play. React Native uses JavaScript or TypeScript with React and, at runtime, creates each platform’s native components. Flutter uses Dart, compiles to machine code and draws its own interface with its engine instead of the system’s controls. With either, anything not built in gets written in Swift or Kotlin.

PWA: a website you can install

A PWA (progressive web app) is a website built to behave like an app: it can be added to the home screen, opens in its own window, works offline and, with permission, sends notifications. No app store is involved: it lives on your domain and updates when you deploy. On Android, Chrome can offer to install it; on iPhone, people install it from Safari’s Share button, and since iOS 26 any site added to the home screen opens as a web app.

What about wrapping your site in an app and submitting it to the stores? Apple’s review guidelines ask apps to offer more than a repackaged website; if it’s just your site in a window, it risks being rejected.

Native vs cross-platform vs PWA: what each can do today

Capabilities shift every year. This is where things stand in October 2026, according to Apple, Google and WebKit documentation; for almost everything, cross-platform can do what native can.

  • Push notifications. Native and cross-platform apps send them on both platforms. A PWA sends them on Android from the browser; on iPhone, since iOS 16.4, only once the user has added it to their home screen and grants permission after tapping a button. If your app lives on notifications, on iPhone you first have to get people to install it by hand.
  • Hardware. Camera, microphone and location work on all three. Bluetooth, NFC and USB from the web exist only in some browsers, like Chrome; WebKit, the engine behind Safari, has chosen not to implement them. If the app talks to a mobile printer or an NFC tag from an iPhone, a PWA is off the table.
  • Performance. Native is the most direct. In catalog, ordering or form-based apps, cross-platform is rarely the limit; you feel it in heavy animation, video or augmented reality. A well-built PWA is fast for looking things up and capturing data, not for intensive graphics.
  • Offline. Native and cross-platform apps store data on the device and sync in the background. A PWA also opens without signal, but Safari has no background sync: on iPhone, anything captured offline goes out once the app is open and back online. Once it’s installed on the home screen, though, Safari doesn’t wipe its data for lack of use.
  • Distribution. Native and cross-platform apps ship through the App Store and Google Play, with each store’s review; internal apps have private channels. A PWA is shared with a link: nobody approves it, but it isn’t in the stores either.
  • Updates. With native, every change is a new version that goes through review, and users install it when they choose. With React Native, tools like Expo’s EAS Update ship JavaScript, copy and image fixes without the store; native code, permissions and any change in what the app does still go through review. A PWA updates when you deploy.

The same ordering app on an iPhone, in October 2026

Native and cross-platform Native

Swift and Kotlin · React Native or Flutter Swift and Kotlin

For almost everything they can do the same: notifications, background sync and hardware. Two codebases and everything Apple and Google ship, from day one.

Order 1042

Ferretería Montes

3 orders synced In the background, at 9:12
Print over Bluetooth

Route printer connected

1/2" PVC pipe 24 pcs

90° PVC elbow 40 pcs

PVC cement 250 ml 6 pcs

Total $3,412.50

Customer signature

Orders now Order 1041 is out for delivery.

Cross-platform

React Native or Flutter

One codebase for both stores. For almost everything, it can do what native can.

Order 1042

Ferretería Montes

3 orders synced In the background, at 9:12
Print over Bluetooth

Route printer connected

1/2" PVC pipe 24 pcs

90° PVC elbow 40 pcs

PVC cement 250 ml 6 pcs

Total $3,412.50

Customer signature

Orders now Order 1041 is out for delivery.

PWA

HTML, CSS and JavaScript

Installed from a link. On iPhone, it only notifies once added to the home screen.

Order 1042

Ferretería Montes

Sending 3 orders Safari has no background sync
Bluetooth isn’t available in Safari

1/2" PVC pipe 24 pcs

90° PVC elbow 40 pcs

PVC cement 250 ml 6 pcs

Total $3,412.50

Customer signature

Orders now Order 1041 is out for delivery.
The same ordering app on an iPhone, three ways. Native and cross-platform send what was captured offline in the background and print over Bluetooth; in Safari, the PWA can do neither.

The table: native, cross-platform and PWA side by side

NativeCross-platformPWA
Built withSwift (iOS) and Kotlin (Android)React Native or FlutterHTML, CSS and JavaScript
CodebaseTwo, one per platformOne for iOS and AndroidOne, which also works on desktop
How it’s installedApp Store and Google PlayApp Store and Google PlayFrom the browser, with a link
Push notificationsYesYesAndroid, yes; iPhone, only when installed on the home screen
Bluetooth, NFC and USBYesYes, sometimes through a native moduleOnly in some browsers, like Chrome; not in Safari
OfflineYes, and syncs in the backgroundYes, and syncs in the backgroundYes; no background sync in Safari
UpdatesUsers install the new versionSame; JavaScript fixes without the store in React NativeInstant on deploy
Team it takesiOS and Android specialistsOne team, with native help as neededA web team

What it costs to keep it running

The launch budget is the visible part; what decides whether a path suits you is what comes after:

  • The yearly iOS and Android releases. Every year brings new permissions and APIs, and Google Play requires new apps and updates to target a recent Android version (Android 16 since August 31, 2026). An app nobody touches eventually can’t ship an update and stops showing up for new users on newer phones.
  • Two stores, two accounts, two rulebooks. Apple and Google both ask for a D-U-N-S number for organization accounts; Apple charges a yearly membership and Google a one-time registration. And the rules move: in some countries, Google already requires every app installed on a certified Android device to come from a verified developer, including apps outside Google Play, and it goes worldwide in 2027.
  • Dependencies and testing. React Native, Flutter and their libraries ship new versions often, and every release of your app gets tested on real phones. Keeping up is recurring work; putting it off turns it into a project.
  • Several versions live at once. In the stores, each user updates when they choose, so your server keeps serving older versions. With a PWA, everyone runs the latest.
Launching an app is a project; keeping it current with two operating systems that change every year is a commitment.

One cost doesn’t change with the path: the server. Accounts, inventory, orders, payments and the link to your ERP or your store live there and need the same upkeep on all three. That’s often where the real work is.

How to decide, by use case

The useful question isn’t which technology is best, but what the app has to do, who uses it and how often.

How to choose, by who uses it

For your customers

  • It depends on hardware or system features Native
  • They use it often and notifications are part of the value Cross-platform
  • They only need it now and then PWA or mobile web

For your field team

  • iPhones on the team and hardware involved Native Cross-platform
  • Company Android phones: camera, location and forms PWA or mobile web

For your store

  • Always signed in, one-tap reorder, alerts and loyalty Cross-platform
Which path fits each use. With iPhones and hardware involved, native and cross-platform both work; a link is enough when the app is only used now and then.

An app for your customers

If your customers will use it often—to reorder, book or track an order—and notifications are part of the value, the default is cross-platform: one branded app in both stores, reliable notifications on iPhone and one team. Go native if the experience depends on hardware or on system features that land there first.

If they only need it now and then, don’t ask them to install anything: a well-built mobile site, or a PWA, arrives with a link. In Cord, for example, the client reviews, approves and pays a quote from their phone’s browser, with no account and nothing to install.

An internal app for your field team

Reps on the road, technicians or drivers: here, working without signal is what matters. The app captures orders, photos and signatures offline, syncs when the signal comes back and, sometimes, prints over Bluetooth or reads NFC tags.

  • With iPhones on the team and hardware involved: native or cross-platform.
  • With company Android phones and only camera, location and forms: a PWA can be enough, and Chrome on Android does offer Bluetooth, NFC and background sync.
  • To distribute it without publishing it: Apple offers custom apps for your organization, installed through Apple Business and still reviewed; Google, private apps on managed Google Play. Neither shows up in the public store.

An app that extends your store

If you sell online, your store already works on the phone. An app makes sense when it offers something the web doesn’t: always signed in, one-tap reorder, order-status or back-in-stock alerts, loyalty at hand.

If your store runs on Shopify, the app reads catalog and cart from the Storefront API, and Checkout Kit shows your store’s checkout inside iOS, Android and React Native apps. Because you sell physical goods, Apple requires you to charge with Apple Pay or a card, not with its in-app purchase system. That’s why cross-platform, and React Native in particular, is usually the natural path here.

React Native vs Flutter, if you go cross-platform

React Native came out of Meta and Flutter out of Google. The difference is in how they work and which team you have.

  • React Native uses TypeScript and React: if your site or your team already work in React, they share a language and part of the logic. It uses each platform’s native components, and the project itself recommends starting with a framework like Expo.
  • Flutter uses Dart and draws every control with its own engine: the interface looks identical on both platforms, which suits a brand with a very distinctive design. For native features it uses plugins and platform channels.

In practice, the team that will maintain it matters more than any benchmark: if your web and backend already speak TypeScript, React Native is usually the shorter road.

At Flouvia we design and build iOS and Android apps for businesses, wired to their operation (accounts, payments, notifications and App Store and Google Play release) and the web too, when that’s the right answer. See what we do in services, or tell us what your app needs to do.

Frequently asked questions

  • Can a PWA send push notifications on iPhone?
    Yes, since iOS 16.4, if the user has added it to their home screen and grants permission after tapping a button. Opened in a Safari tab, it doesn’t get them.
  • Can I publish a PWA on the App Store or Google Play?
    On Google Play, yes, packaged as a Trusted Web Activity. On the App Store it has to ship inside an app, and Apple asks for more than a repackaged website.
  • Should I build a native or a cross-platform app?
    If your app is about catalogs, orders, accounts or forms, cross-platform gets you both stores with one codebase and one team. Go native when it depends on hardware, extreme performance or system features from day one.
  • Can I start with a PWA and move to a native app later?
    Yes. The server, the API and the flows carry over; the interface gets rewritten. If your web app is built in React, React Native lets you share part of the logic.

Written by

André Valle Ortega

Founder, Flouvia

André Valle Ortega is the founder of Flouvia, the design and engineering studio that builds made-to-measure websites, stores, portals, apps, platforms and automation.

LinkedIn