React Native, Flutter or native? Choosing a stack for an Indian startup app

Founders ask this as if it were a benchmark question. It is mostly a question about who will build and maintain the app, and what else they will build alongside it.

The three options

• Native: Swift for iOS, Kotlin for Android. Two codebases, two skill sets, the most direct access to every platform feature.
• React Native: one codebase in JavaScript or TypeScript, rendering real native UI components. Backed by Meta and used in production by large apps.
• Flutter: one codebase in Dart, drawing its own UI with its own rendering engine. Backed by Google.

Why cross-platform is the default for a business app

A business app is forms, lists, logins, payments, notifications and maps. None of that needs to be written twice. One codebase means one team, one bug tracker, one release, and roughly half the engineering hours of two native builds. For an MVP or a small business, this is decisive on its own.

React Native or Flutter?

Both are capable. The differences that actually matter to an Indian startup:

Hiring. React Native is JavaScript and React. India has an enormous pool of React web developers, and most of them can be productive in React Native within weeks. Dart is learned specifically for Flutter, so the pool is smaller, though growing.

Sharing with the web. If you also have, or will have, a React website, React Native lets you share business logic, API clients, validation and sometimes components. Flutter can target the web, but you will generally still build the website separately.

UI feel. React Native renders the platform's own buttons, lists and inputs, so an app looks and behaves like an iOS app on iOS and an Android app on Android. Flutter draws every pixel itself, which makes pixel-identical UI across platforms easy and platform-native feel a deliberate effort.

Backend integration. Either works with any backend. UgeWorks pairs React Native with a serverless AWS backend through Amplify and AppSync, which gives authentication, GraphQL APIs and push notifications with very little glue code.

The practical rule: if your team, or the team you can hire, knows React, choose React Native. If your team is Dart-first, choose Flutter. Do not choose against your team.

When native is right

• The app *is* the hardware: real-time camera processing, AR, professional audio, Bluetooth peripherals with tight timing.
• You need a new platform feature the day it ships, before the cross-platform community wraps it.
• You already have separate iOS and Android teams and are not trying to reduce headcount.
• Performance is the product, as in a game or a heavy animation tool.

For everything else, the second codebase is cost without benefit.

What this means for your quote

A vendor proposing native for a bookings-and-payments app should be asked why. A vendor proposing cross-platform should be asked which framework and why that one, and the answer should be about their team's skills and your future website, not a benchmark chart.

At UgeWorks the answer is React Native with an AWS backend, because that is what the engineer writing your app has shipped to the App Store before, and because most clients also want a website in React.

Questions people ask

Sources

1. React Native
2. Flutter
3. App Store Review Guidelines