Flutter or React Native? How we decide for a client

Clients often ask which framework is better. It is the wrong question, as both can ship excellent apps. The useful question is which one suits this product, this team and the next few years of maintaining it.

Start with who maintains it

A framework is a long-term hiring decision. If your company already has JavaScript and React developers, React Native lets them contribute from day one. If you have no existing team, or you are hiring fresh, that advantage disappears and the choice can rest on the product.

When we lean towards Flutter

• The design is heavily custom and needs to look identical on both platforms.
• Your app has lots of animation or custom drawing.
• You have no existing web team to share code or skills with.
• You want consistent behaviour on a wide range of older Android devices.

When we lean towards React Native

• Your team already builds with React and TypeScript.
• You want to share logic and types with a React website.
• The app should follow each platform's native look and conventions.
• You rely on over-the-air updates for fast fixes.

When we would go native instead

Sometimes neither is right. Heavy use of device hardware, background processing, or platform features that arrive first in Swift and Kotlin can justify two native codebases, along with the extra cost that brings.

Test the risky part first

Whatever the choice, we build a one-week prototype of the hardest part of the app first, such as the mapping, the Bluetooth connection or the offline sync. A week of evidence on real devices is better than any comparison table, including this article.