Engineering4 min read

Swift and Kotlin, or one codebase with React Native or Flutter? The honest answer depends on what your app has to do on the phone, not on which camp sounds more serious.

The short answer

Choose cross-platform (React Native or Flutter) when your app is mostly screens, forms, lists and network calls, and you need iOS and Android from one team. Choose native (Swift and Kotlin) when the core of the product lives in the hardware: heavy camera or AR work, background audio, Bluetooth devices, widgets, watch apps or animation that must feel perfect on each platform.

What "native" and "cross-platform" actually mean in 2026

A native app is written in each platform's own language and toolkit: Swift and SwiftUI on iPhone and iPad, Kotlin and Jetpack Compose on Android. You build two apps that share a design and a backend, but not code.

A cross-platform app is written once and runs on both. The two serious options today are React Native (JavaScript or TypeScript, rendering real native components, usually with Expo handling builds and updates) and Flutter (Dart, drawing every pixel with its own engine). Both produce real store apps, not websites in a wrapper.

There is a middle path too: Kotlin Multiplatform shares the business logic (networking, data, rules) and keeps the interface native on each side. It suits teams that want native screens without writing the same logic twice.

When cross-platform is the right call

  • Most of the app is screens and data. Sign in, browse, search, book, pay, chat, see your history. This is the majority of business apps, and cross-platform handles it well.
  • You need both stores on day one. One codebase means one team, one set of bugs and one release rhythm instead of two.
  • You are still finding product-market fit. Early products change weekly. Changing one codebase is cheaper than changing two in step.
  • Your web team already writes React. React Native lets the same people, and some of the same code, work on the app.

Worth knowing

With React Native and Expo, many fixes can ship as over-the-air updates without waiting for store review. That alone changes how fast an early product can learn.

When native is worth the extra cost

  • The camera, AR or video is the product. Real-time filters, scanning at speed, ARKit or ARCore work, custom video pipelines.
  • Deep hardware or system features. Bluetooth devices, background location or audio, HealthKit, CarPlay, Android Auto.
  • Platform extras users expect. Home screen widgets, Live Activities, Apple Watch and Wear OS apps, App Clips.
  • Interaction that must feel exactly right. Gesture-heavy or animation-heavy apps where a few dropped frames are the difference between delight and "it feels off".
  • A long-lived product with separate platform teams. At scale, two native teams can each move at full speed on their own platform.

React Native or Flutter?

Both are mature and both ship serious apps. The choice is usually about your team and your design. React Native renders the platform's own components, so the app looks and behaves like an iOS app on iOS and an Android app on Android, and it fits naturally next to a React or Next.js web product. Flutter draws its own interface, which makes a strongly branded, identical-on-both-platforms design easy and very consistent.

If you already have web engineers in React and TypeScript, React Native is usually the shorter path. If your design is custom from edge to edge and you want pixel-identical screens, Flutter is a strong choice.

The questions we ask before recommending either

  1. 01What is the one job a user opens this app to do, and does that job need the hardware?
  2. 02Do you need both iOS and Android at launch, or does your audience lean heavily to one?
  3. 03Is there a web product that should share logic or design with the app?
  4. 04Who will maintain it in two years: a small team or separate platform teams?
  5. 05Which platform extras (widgets, watch, CarPlay) are on the roadmap, not just the wish list?

What we build with, and why it varies

We build with Swift and SwiftUI, Kotlin and Jetpack Compose, React Native with Expo, Flutter and Kotlin Multiplatform (the full list is in our stack). We pick per product rather than per habit. A local discovery app like Mirchi35, where the value is in live, location-aware listings, is a different problem from an app whose whole point is the camera.

If you are unsure, start by writing down the one job your app must do brilliantly. Then book a 15-minute call and we will tell you which approach fits, and what the first version should leave out. Related reading: what drives the cost of building an app.

AL
“Most founders ask "native or cross-platform?" as their first question. It is usually the fourth. Decide the job, the audience and the platforms first, and the framework tends to choose itself.”
The Auralion Labs team

Questions people ask us.

For typical business apps (screens, lists, forms, network calls) users will not notice a difference with modern React Native or Flutter. Native still wins for heavy camera, AR, real-time graphics and some animation-heavy interfaces.

Usually, when you need both iOS and Android, because one team writes and maintains one codebase. The saving shrinks if the app needs many native-only features, since those still have to be built per platform.

React Native suits teams that already use React and TypeScript and want each platform's native look. Flutter suits strongly branded designs that should look identical on both platforms. Both are mature enough for production apps.

Yes. Many products start cross-platform to find their market, then rewrite the screens that need it natively, or move to native when separate platform teams make sense. A clean backend and API make that move much easier.

Keep reading.