Flutter or native: one cross-platform app or two native apps?

A native app is written in the platform’s own language and tools: Swift for Apple devices and Kotlin for Android. The result is two entirely separate apps that look and behave alike but share no code, and each needs developers with different experience.

A cross-platform framework writes the app once and produces a build for each platform. Flutter, from Google, uses the Dart language and draws the interface with its own engine, so the app looks identical on both. React Native, from Meta, uses JavaScript and renders the system’s native interface components. Both let you write native pieces when you need something the framework does not cover.

Either way you need the same server and admin panel, a developer account in each store, and testing on real devices of both kinds. Cross-platform saves you writing the interface and logic twice. It does not save everything.

For most business apps. If your app is screens showing data from a server, forms, a basket and payment, notifications and maps, cross-platform handles all of that well, and the user neither knows nor cares what the app was written in.

The real benefit shows after launch, not before. Every new feature and every fix is written once and reaches both platforms together. With two native apps it is common for one platform to run ahead of the other, so half your customers complain about a feature the other half can see.

It is also the sensible choice for the first version of any idea. There is no point paying for two apps to test a market that has not been proven.

When what sets your app apart is exactly what the platform itself does best. These cases are real, but there are fewer of them than people assume:

The saving from cross-platform is real, but it is not half. The server, database, admin panel, design, testing on both platforms and publishing to both stores stay the same. What gets written once instead of twice is the interface and the app logic, a large share of the work but not all of it. That is why we give no fixed percentage; it varies from app to app.

As ranges from the Saudi market: a simple app or first version costs SAR 15,000 to 75,000, a mid-sized app on iOS and Android with an admin panel and payments SAR 60,000 to 170,000, and advanced apps SAR 100,000 to 300,000. Set aside 15% to 20% of the build cost each year for maintenance; with two native apps that percentage applies to two codebases, not one.

Do not confuse a cross-platform app with a web-view app that shows your website inside a wrapper. The latter is cheaper, SAR 4,500 to 25,000 in the market, but limited in performance and features, and it is not what we are comparing here.

For a project owner, the difference between the two is far smaller than the difference between a good team and a weak one. Both are mature and well-known apps are built with each. Flutter gives an identical interface on both platforms because it draws it itself. React Native sits closer to a company with a JavaScript web team, since it shares the language and some tooling.

Choose the team first, then let it work in the technology it has mastered. Ask it two things: show me a published app you built with this technology that I can download now, and what do you do if we need a feature the framework does not support? A good answer to the second is "we write that part natively", not "that is not possible".

Answer these honestly and the decision is clear in most cases.

At Fortune Code we build most business apps cross-platform and recommend native when the case calls for it. We send a written quote within 24 hours, with a written delivery date, code and store accounts in your name, and fast technical support after release.