Skip to content

Native or cross-platform: choosing the right approach for your mobile app

Flutter, React Native, fully native — or a web app instead. How to decide based on what your app does, who uses it, and who will maintain it.

MobileMay 28, 20263 min read

A smartphone home screen full of app icons on a wooden desk

When a client asks us for an app, the first technical decision is how to build it, and it shapes the budget, the timeline and the maintenance bill for years. There are three realistic options, and no single one is right for everyone.

The three options

  • Native — a separate app for each platform, written in Swift for iPhone and Kotlin for Android. The best possible performance and access to every device feature, at roughly the cost of building twice.
  • Cross-platform — one codebase that produces both apps, most often with Flutter or React Native. Close to native for most business apps, at a much lower cost.
  • A web app — a fast, mobile-first website, optionally installable to the home screen as a progressive web app. No app store, nothing to download, one thing to maintain.

When cross-platform is the right call

For the large majority of business apps — ordering, booking, tracking, customer accounts, staff tools — cross-platform is our default. These apps are mostly forms, lists, maps and notifications, and modern frameworks handle all of that well. One codebase means one team, one set of bugs to fix and features that arrive on both platforms at the same time.

That last point matters more than it sounds. With two native apps, it is common for one platform to fall behind, and the customers on it notice.

When native earns its cost

Native development is worth the extra investment when the app's core value depends on the device itself:

  • Heavy use of the camera, sensors, Bluetooth or background location.
  • Demanding graphics, augmented reality or real-time media.
  • Deep integration with the operating system — widgets, watch apps, system-level features.
  • An existing in-house team that already writes Swift and Kotlin.

Do not skip the third option

Many apps do not need to be apps at all. If customers use it occasionally — to check an order, book a slot, view a catalogue — a well-built mobile website is often better. Nobody has to install anything, it is found through search, and every update is live immediately without waiting for store approval. A progressive web app can still sit on the home screen and send notifications on Android.

Ask honestly: will customers open this every week? If not, they are unlikely to download it, and a web app will reach more of them.

What changes in Nepal

A few local realities push the decision in particular directions:

  • Most of your users are on Android, often on mid-range or older phones. Test there first, and keep the download small.
  • Data can be expensive and connections patchy. Apps should load quickly and cope with going offline, especially for field staff such as delivery riders.
  • Payments mean integrating local wallets and gateways, which have their own SDKs and approval steps — allow time for them.
  • Publishing costs are modest but real: Apple's developer programme is an annual fee, Google Play is a one-time registration, and both stores review your app before it goes live.

Think about who maintains it

An app is never finished. Operating systems update every year, store rules change, and libraries need patching. Before choosing a technology, ask who will maintain it in two years. A popular cross-platform framework makes it far easier to find developers later than an unusual stack does. Whatever you choose, make sure you own the source code and the store accounts — not your developer.

A quick way to decide

  • Used rarely, found through search → a mobile-first web app.
  • Used regularly, mostly forms, lists, maps and notifications → cross-platform.
  • Built around the camera, sensors, graphics or the operating system → native.
  • Several apps for different users — customers, riders, admin → cross-platform, sharing one codebase and one backend.

When we built the customer, rider and admin apps for a logistics client, cross-platform let one team deliver all three on iOS and Android from shared code. That is the typical case. The exceptions are real, though, and it is worth an hour's conversation to find out which one you are before committing a budget.

All software articles

Build your next digital product with Nandi today

Let our experienced team design, build and maintain software that saves time, delights users and grows your business.

Get Started