A senior engineer’s decision framework for picking between React web and Flutter mobile when you only have budget to build one — based on user behavior, distribution, and economics.

The "React or Flutter" question is almost never about the technology. It's about distribution, user behavior, and which audience you can afford to launch without. Here's how I actually walk founders through the decision.

The wrong way to pick

Most founders pick based on what they've heard at a conference or what their cousin's startup used. That's a coin flip. The right framing is:

Where does your user already spend time, and how do they discover new products?

If the answer is "they search Google for a solution," you're building React. If the answer is "they download apps from the App Store on their commute," you're building Flutter.

Build React first when…

Users discover you through Google search, content, or paid ads that link to a URL
Your product is a tool people use at a desk — dashboards, B2B SaaS, admin systems
You need to iterate fast — web shipping is 10x faster than App Store review
Your conversion path is sign up → pay with no native-app advantages (push notifications, camera, location)

The unfair advantage of starting with React: you can ship Monday and learn from real users by Friday. You can't do that on the App Store.

Build Flutter first when…

Users live on their phone and expect a native app (consumer apps, fitness, food, social, gig economy)
You need native device features — push notifications, GPS, camera, offline mode, in-app purchase
Your competitors are all on the App Store and Play Store, and not having a listing makes you look unserious
Your distribution is the stores themselves (App Store search, featured placements, store ratings)

If you ignore the App Store when your category lives there, you're invisible.

Why not both?

You can — eventually. The mistake is doing both at the same time with the same budget. You will ship two half-built products that each underperform what a focused team would have shipped on one platform.

Pick the one where your users are. Win there. Then expand.

The economics

For roughly the same budget ($30K-$80K), you can ship:

A React web app with auth, payments, dashboards, and 3-5 core flows — live on day one
A Flutter mobile app with native iOS+Android, push, subscriptions, and the App Store + Play Store listings — live after review

Both are real products. Neither is "easier" — they have different shipping overhead. React has zero distribution cost; Flutter has zero web-to-mobile friction once users install.

The decision tree

Are your users searching Google for the problem you solve? → React
Are your competitors all on the App Store and you're not? → Flutter
Do you need native device features that the web can't deliver? → Flutter
Will you charge a subscription that benefits from in-app purchase / push reminders? → Flutter
Otherwise → React first, mobile later when you have revenue

We've shipped both stacks for clients. If you want a senior engineer's honest read on which one fits your specific business, book a discovery call — we'll talk through it in 15 minutes.

React or Flutter: Which Should You Build First?