Skip to content

Guide · Mobile technology · Updated November 2026

Flutter or React Native: which should you choose for your app in Morocco?

For the vast majority of service apps in Morocco (bookings, commerce, delivery, rentals, internal tools), Flutter and React Native both deliver a good iOS and Android app from a single codebase. The difference lies elsewhere: the team that will maintain the code, reuse with your website, over-the-air updates and the module ecosystem. Here is how to decide, project by project, and when native (Swift, Kotlin) is still the right answer.

Start a project →See pricing →

One codebase
iOS + Android, with Flutter or React Native
Flutter
Dart language, draws its own interface
React Native + Expo
JavaScript/TypeScript, native components
At VCTRUM
React Native and Expo by default, native when needed

Cross-platform or native: what are we talking about?

A native app is written twice: in Swift for iPhone, in Kotlin for Android. Two codebases, often two developers, and every feature is built, tested and fixed twice.

A cross-platform app is written once and published on both the App Store and Google Play. Flutter (Google) and React Native (Meta) are the two dominant technologies. They work differently:

Flutter

Code is written in Dart. Flutter draws every pixel itself with its own rendering engine: according to the Flutter documentation, Impeller has been the default engine on iOS and Android (API 29+) since version 3.27.

React Native

Code is written in JavaScript or TypeScript, with React. According to Expo, the app ships a JavaScript engine and a C++ interface that create and update real native iOS and Android views.

Expo

The framework recommended by the official React Native documentation: routing, ready-made native modules, builds and over-the-air updates. Expo is free and open source.

Native (Swift, Kotlin)

The most direct access to the phone and to new Apple and Google features on day one, at the cost of two codebases to fund and maintain.

Flutter vs React Native: point-by-point comparison

This table sums up what matters for a project in Morocco. It does not name a winner: it shows where each technology has the edge.

CriterionFlutterReact Native + Expo
LanguageDart, new to most teamsJavaScript / TypeScript, the language of the web
UI renderingOwn engine (Impeller): identical rendering on iOS and AndroidEach platform’s native components: iOS look on iPhone, Android look on Android
Performance of a service appExcellentExcellent since the New Architecture, enabled by default from React Native 0.76 (October 2024)
Rich animations, fully custom UIStrong pointDoable, needs more care
Reuse with a React / Next.js websiteLow: different language and componentsHigh: same language, shared business logic, validation and types
Over-the-air (OTA) updatesThrough a third-party service (Shorebird)Built in with Expo’s EAS Update
Right-to-left ArabicSupported (flutter_localizations)Supported (I18nManager)
Web version of the appPossible, but poorly suited to SEO according to FlutterPossible with Expo for web; a public site is better built in Next.js
App sizeBundled engine: a few compressed MB baseline according to FlutterJavaScript engine bundled in the app according to Expo: measure it on your build, as with Flutter

Sources at the bottom of the page. Both technologies move fast: always check recent versions before locking in a choice.

Performance: a non-issue for most projects

“Which one is faster?” is often the first question. For a booking, ordering or tracking app, the honest answer is: both are more than enough. What slows an app down in Morocco is almost always poorly optimised lists, heavy images, chained server calls or a slow back end, not the framework.

Flutter keeps a real edge on highly animated, fully custom interfaces, since it controls every pixel. React Native has closed most of the gap with its New Architecture, which the React Native team describes as enabled by default since version 0.76. If your product is a game, a photo or video editor, or relies on heavy on-device processing, neither is the best choice: see the section on native.

  • Test on an entry-level Android phone, not just the founder’s iPhone: that is what many of your customers use
  • Measure on an average 4G connection, not office Wi-Fi
  • Compress images server-side and paginate lists from the first version
  • Keep heavy processing on the server, unless you truly need offline

Arabic and right-to-left interfaces

In Morocco, a consumer app often has to work in French and Arabic, sometimes English. Both technologies handle right-to-left Arabic. According to the Flutter documentation, the flutter_localizations package sets the text direction and adapts Material and Cupertino components. According to the React Native documentation, the I18nManager module controls right-to-left layout; Expo documents the same approach.

In both cases, the framework only does half the job. The rest is decided at design time:

  • Plan Arabic from the mockups: arrows, back icons, progress bars and charts flip
  • Avoid hard-coded absolute “left” or “right” positions
  • Test mixed text: an order number or a price in digits inside an Arabic sentence
  • Pick a font that renders both Arabic and Latin scripts properly
  • Decide whether language switches inside the app or follows the phone’s language

Planned from the start, Arabic costs little; added later, it means reworking part of the screens, whatever the technology.

Over-the-air updates: fixing without waiting for the stores

An over-the-air (OTA) update fixes an interface or logic bug without publishing a new version to the stores. For a delivery app on a Friday night, that is the difference between a fix in minutes and waiting for review.

According to the Expo documentation, EAS Update lets an app update its non-native parts (JavaScript, styling, images). On the Flutter side, there is no official Google solution; the third-party service Shorebird offers code push that, according to its documentation, works within store rules.

Apple’s rules remain the limit: under guideline 2.5.2 of the App Store Review Guidelines, an app may not download code that introduces or changes features. OTA is therefore for fixes and adjustments; any new feature or native change (a new permission, a new module) goes back through the stores.

Your website matters in the choice too

Many projects in Morocco have both an app and a website: a marketing site that must be found on Google, a web back office, a merchant portal on a tablet.

With React Native, the mobile app and a React or Next.js site share the language (TypeScript), validation rules, data types and part of the business logic. Expo also documents using Next.js for the web side. One team can work on both.

Flutter can produce a web version of the app, but its own documentation says Flutter web targets app experiences and that its output does not align with what search engines need; it recommends building public pages and content in regular HTML. For a site that must rank, you will need a second technology next to Flutter.

Ecosystem, hiring and maintenance

An app lives for years. The real question is not “what can my agency do today?” but “who can take over this code in three years?”.

The developer pool

React Native builds on JavaScript and TypeScript, the languages of the web: a React developer picks up mobile quickly. Flutter requires Dart. Before choosing, look at the profiles available where you will hire.

Available modules

Payments, maps, notifications, camera, Google or Apple sign-in: both ecosystems cover common needs. During scoping, check that every essential integration has a maintained module, or plan to write it.

Version upgrades

Apple and Google regularly require newer versions of their systems. A project updated several times a year stays simple; a project left alone for two years becomes costly to restart, in Flutter or React Native.

Ownership

Whatever the technology, the code, store accounts and access must be in your name. That is what lets you change providers without starting over.

Payments, maps, offline: what does not depend on the framework

The features that make a Moroccan app complex are mostly decided on the server and during scoping, not by choosing Flutter or React Native.

  • Card payments: the integration with the payment processor and the bank happens server-side; the app shows the payment page and receives the result. See our guide on CMI payments
  • Cash on delivery: this is business logic (order statuses, collection by the courier), identical in both technologies
  • Maps and real-time tracking: modules exist in both ecosystems; the cost comes mainly from the real-time server and map API usage
  • Offline mode: possible in both with a local database; the real work is synchronisation and conflict handling, to be scoped from the start
  • Background location (courier or driver app): subject to strict Apple and Google rules, whatever the technology

When native (Swift, Kotlin) is the right answer

Cross-platform covers the vast majority of service apps. Native is justified in a few specific cases:

  • Games, augmented reality, real-time video or audio processing
  • Heavy use of a specific sensor or hardware (industrial Bluetooth, payment terminal, connected device)
  • Needing every new iOS or Android feature on release day (advanced widgets, smartwatch)
  • An in-house team already made of native iOS and Android developers
  • A single target platform, for example an internal tool deployed only on Android devices

A common middle ground: the app in cross-platform, with only the demanding module written in Swift or Kotlin and plugged in. Both Flutter and React Native allow it.

Decision grid by project type

Project typeOur recommendationWhy
MVP to test a marketReact Native + Expo, or Flutter if the team knows it wellOne codebase, remote fixes during the test phase; iteration speed is what matters
Marketplace (customer, provider, admin)React Native + ExpoSeveral apps and a web back office share TypeScript and business logic
Delivery or ride-hailingReact Native + Expo, native modules if neededMaps, real time and background location well covered; fast fixes in production
Internal tool (field, stock, inspection)Flutter or React Native; native Android if a single device typeOffline and forms matter more than the framework
Highly visual brand app, custom animationsFlutterIdentical rendering and full pixel control on iOS and Android
Game, AR, real-time videoNative or a game engineNeeds direct hardware access

If you already have working Flutter or React Native code, keeping it is almost always cheaper than rewriting everything.

What the choice changes for budget and timeline

Between Flutter and React Native, the budget gap is small for the same scope: both avoid paying for two apps. The big gap is between cross-platform and native: two codebases mean more development, more testing and more maintenance every year.

Budget depends above all on the number of user types, payments, real time and the back office. Our guide to mobile app prices in Morocco details market ranges and post-launch costs. For publishing, our App Store and Google Play guide explains accounts, timelines and rules.

  • Choosing a technology your future team can maintain avoids a costly rewrite
  • Over-the-air updates cut the cost of small fixes after launch
  • Sharing code with the website lowers the cost of app + web projects
  • One native module costs less than a fully native app

What VCTRUM uses, and why

We build with React Native and Expo by default: one codebase for the App Store and Google Play, over-the-air updates and the same language as our React and Next.js websites and back offices. When a feature reaches deep into the phone, our engineers write that module in Swift or Kotlin and plug it into the rest of the app.

We also audit existing apps in Flutter, React Native or native code. If your app already runs on Flutter, we will tell you honestly whether it is better to keep it.

  • iOS and Android apps in React Native and Expo, from scoping to store release
  • Interface in French, right-to-left Arabic and English, planned from the mockups
  • CMI, NAPS, Stripe or cash-on-delivery payments
  • Audits of React Native, Flutter, native iOS and Android apps
  • You own the code and the store accounts

Our work

Real projects, with their screens and their status.

All our work →

Frequently asked questions

Flutter or React Native: which is better?

Neither in absolute terms. For a service app, both give a very good result on iOS and Android. Flutter has the edge for highly animated interfaces that look identical on both platforms; React Native with Expo has it for sharing code with a React or Next.js site and for built-in over-the-air updates.

Is a Flutter or React Native app slower than a native one?

For a booking, commerce or delivery app, the difference is not noticeable if the app is well built. Native keeps the edge for games, real-time video or heavy hardware use.

Do both technologies support Arabic?

Yes. Flutter handles right-to-left with flutter_localizations, React Native with I18nManager. What matters most is planning Arabic from the mockups: icons, arrows and mixed text must work in both directions.

Can you fix an app without going through the App Store?

For interface and logic fixes, yes: with Expo’s EAS Update for React Native, or a third-party service such as Shorebird for Flutter. New features and native changes always go through the stores, in line with Apple’s guideline 2.5.2.

Can the app and the website share the same code?

Partly. With React Native, the app and a React or Next.js site share the language, types and business logic. Flutter can produce a web version of the app, but its documentation advises against it for a site that must rank on Google.

My app is built with Flutter: should I rewrite it in React Native?

Rarely. If it works and a team can maintain it, keeping it is almost always cheaper. A rewrite makes sense when the code is unstable, long abandoned or blocks an important change; an audit settles the question.

Does the technology change the price of my app?

Little between Flutter and React Native. The big gap is with two native apps, which require two codebases. Price depends mostly on scope: user types, payments, real time and back office.

Which technology does VCTRUM use?

React Native and Expo by default, with Swift or Kotlin modules when a feature requires it. We also audit Flutter and native apps.

Unsure which technology fits your app?

Describe your project in two minutes. Within 24 h, we give you our view on the right technology and a detailed quote.

Talk about my project →