Service · App development

Custom React Native app development for iOS & Android.

One codebase, two app stores. We build native-feeling mobile apps in TypeScript on the modern React Native stack — with Fabric, Hermes, Expo and EAS — for founders, product organisations and agencies who want to get to mobile quickly without setting up two separate teams.

TypeScriptNew ArchitectureExpo & EASOTA updates

What is React Native and why is it the default choice?

React Native is Meta's open-source framework that runs the React components you write for the web on iOS and Android. Under the hood, it connects JavaScript or TypeScript to real native UI elements — Swift and Objective-C on iOS, Kotlin and Java on Android. The result is not a webview and not a hybrid app in the old sense of the word, but a native interface driven by React. What the user sees on their screen are real UIKit or Android controls; only the logic and orchestration live in JavaScript.

Since version 0.76, the New Architecture is the default: Fabric as the renderer, TurboModules for native modules and the Hermes engine for fast JavaScript execution. The old asynchronous bridge between JavaScript and native has been replaced by synchronous, type-safe interop. For clients, that means a level of performance that is comparable to native in practice — for the vast majority of the business and consumer use cases we build.

Apps such as Facebook, Instagram, Discord, Shopify, Microsoft Office, Walmart and Tesla run on parts of React Native. A wide range of Fortune 500 companies use the framework somewhere in their product portfolio. The maturity of the ecosystem, the size of the talent pool and the easy transition for web teams make React Native the pragmatic default for most business apps. When it isn't a good fit, we'll tell you honestly. Further down this page you'll find the cases where we point you towards Flutter or native instead.

We build React Native apps for founders who want to get to mobile quickly, for product organisations with an existing React web platform, and for enterprises that want a phased migration away from a legacy native app. The broader service context, from scoping and architecture to CI/CD and maintenance, is covered on our overarching app development page. For the business-focused variant, see building a B2B app.

When React Native is the right choice.

Four patterns we guide clients through. If you recognise one of them, React Native is almost always the pragmatic answer.

Shared codebase

You want iOS and Android in a single project

Separate Swift and Kotlin apps mean, in practice, two codebases, two QA pipelines and two release schedules to coordinate. With React Native we share between eighty and ninety-five per cent of the code and only build platform-specific exceptions where UX or access to a platform API requires it. The scope is therefore noticeably smaller than a dual native build.

React experience

Your web team already knows React

If you already have a React or TypeScript team building for the web, that same team can deliver the mobile app without you having to hire Swift or Kotlin specialists. Hooks, types, validation schemas and utilities can be shared literally as they are. The pool of React developers in the Netherlands is also considerably larger than that of native specialists, which makes hiring and long-term maintenance easier. For longer-term capacity needs, we look at hiring app developers.

Brand-consistent UI

Your brand needs to feel the same on both platforms

For B2B portals, customer apps and branded e-commerce, you want the app to keep the same look and feel on iOS and Android. React Native uses native controls but leaves room for brand-specific components through libraries such as Restyle, Tamagui or NativeWind. We work with design tokens that your web app can use as well, so colours, type scale and spacing rules have a single source.

MVP & cross-platform launch

You want a working MVP on both platforms quickly

With Expo and EAS Build, we can put a testable version on your stakeholders' phones early in the project, with no Xcode installation and no Android Studio needed for reviewers. Iteration happens over the air via EAS Update, so feedback reaches users in a short feedback cycle. That measurably speeds up validating product decisions compared with a dual native route.

When React Native is not the right choice.

Honesty saves you an expensive change of direction halfway through. These are the three patterns where we'll point you towards native or a specialised alternative.

Not 01

Heavy low-level native features

AR applications, real-time vision pipelines, complex camera controls with manual exposure and focus, hardware keys such as YubiKey or smartcard readers, Bluetooth mesh or low-level low-energy IoT pairing: these belong on native. The right tooling, sample code and documentation live in the Apple and Google SDKs, and anything you would build in React Native would end up as a native module with a thin JS wrapper. In that case, you're better off leaving out the bridge altogether.

Not 02

Maximum performance for gaming

For graphics-heavy games, console-style 3D rendering pipelines and mobile games that keep the GPU running at sixty or 120 frames per second, Unity, Unreal or dedicated native rendering with Metal and Vulkan are the right choice. For occasional animation or a game-like dashboard we can get a long way with Reanimated and React Native Skia, but for production-grade gaming we would rather advise you to pick the right tools than force something that doesn't fit.

Not 03

Native UX perfectionism as a commercial requirement

For premium consumer apps where every detail of the iOS or Android Material experience must be pixel-perfect, down to haptics, system fonts in every state and platform-native motion, native is the sensible answer. React Native gets very close, but the last few percent between "feels native" and "is native" will be spotted immediately by a professional review or a design-conscious client. That route is more expensive in both worlds, and more honest in native.

React Native, Flutter or native: a sober comparison.

The three options side by side. In the first conversations we help you choose which fits, based on your existing stack, team and product ambitions.

Criterion
React Native
Flutter
Native (Swift / Kotlin)
Language
TypeScript / JavaScript
Dart
Swift & Kotlin (two teams)
Dutch talent pool
Large, shared with web
Small, growing slowly
Scarce, expensive
UI rendering
Native controls via Fabric
Own Skia engine, draws every pixel itself
Fully native per platform
Code sharing with web
High: React components and hooks
No native code sharing with web
None
Code sharing iOS/Android
Eighty to ninety-five percent
Comparable, often slightly higher
None, two codebases
OTA updates
EAS Update, in-app updates
Shorebird, more limited availability
None (store releases only)
Best for
B2B, portals, MVPs, e-commerce
Brand-consistent UI, animation-heavy
AR/VR, gaming, hardware IoT, premium UX
Ecosystem
Large, broad production track record
Growing fast, younger
Full platform SDKs, everything available

The modern React Native stack in 2026.

Our default configuration for production apps. Depending on your scope we swap out components, but these are the building blocks we start with as standard.

Core & runtime

React Native 0.76+, Hermes, New Architecture

We start on a recent React Native release with Fabric and TurboModules enabled by default, and Hermes as the JavaScript engine. Hermes is optimised for mobile, with fast start-up and lower memory usage than the old JavaScriptCore runtime. TypeScript is always part of the setup, with strict mode and types generated from your back end for end-to-end type safety.

Tooling & build

Expo SDK, EAS Build, EAS Update

Expo (managed workflow) is our default for most projects, thanks to the developer experience and the production-grade build and update infrastructure via EAS. We use the bare workflow where native modules are needed that don't work via Expo Modules, which is rare these days. EAS Build delivers cloud builds of iOS and Android binaries without your own Mac runners; EAS Update replaces the now-retired Microsoft App Center for over-the-air updates.

Data, state & UI

MMKV, TanStack Query, Reanimated

MMKV as fast on-device key-value storage instead of AsyncStorage, TanStack Query for server state and cache invalidation, Zustand or Redux Toolkit for client state depending on complexity, and Reanimated 3 with Gesture Handler for animations that run on the UI thread. For forms we use React Hook Form with Zod for type-safe validation, and for styling NativeWind or Tamagui, depending on design requirements.

Navigation & lists

Expo Router, Shopify FlashList

File-based routing with Expo Router, built on React Navigation v7. For high-performance lists we use Shopify's FlashList instead of the standard FlatList, which gives noticeably better scroll performance for long datasets and better memory efficiency. For re-render performance we rely on React.memo, useMemo and useCallback, and we use React DevTools and the Hermes profiler to catch hotspots early.

Quality & testing

Jest, Maestro, Detox, Reactotron

Jest for unit tests, Maestro or Detox for end-to-end flows on real devices or simulators, and Reactotron for local state and network inspection during development. Accessibility is built in from the start: semantic roles, focus management, contrast checks and screen-reader tests with VoiceOver and TalkBack are standard QA steps, not something ticked off once at the end.

CI/CD and monitoring

Fastlane, EAS Build, Sentry

Fastlane for the release pipelines to App Store Connect and Google Play Console, EAS Build for the binaries, and GitHub Actions as the orchestration layer that tests every pull request on iOS and Android. For production monitoring we use Sentry: native crashes, JavaScript errors and performance traces in one dashboard, with source maps and symbolication set up automatically. Feature flags via PostHog or LaunchDarkly allow phased rollouts.

Three flavours of React Native projects.

It depends on where you are now and what it needs to deliver. We'll advise which approach fits in the first conversation — no fixed packages, but clear outlines.

MVP · fixed sprint budget

Cross-platform MVP in a single project

A first working app for both platforms from a single Expo project. For founders and product organisations who want to validate quickly whether the concept works, with OTA updates for fast iteration and EAS Build for TestFlight and Internal Testing distribution. The architecture is production-grade from the start, so the MVP never needs a rebuild later.

Expo managedEAS BuildTypeScriptTestFlight
Production app · fixed sprint budget

B2B or B2C app on an existing stack

A React Native app that belongs to an existing product. Deep integrations with your back end, identity provider (SSO, biometrics), payment flows and analytics. We build with the production stack above from day one and deliver with monitoring, alerting and a release pipeline that your own team can run themselves.

SSOSentryEAS UpdateFlashList
Brownfield migration · fixed sprint budget

Phased migration of an existing native app

You already have a Swift or Kotlin app and want to move to React Native in phases, the model Meta itself uses. We add React Native as a brownfield module, start with a single screen or feature, and expand where it makes sense. Production stability is maintained throughout; no big-bang release.

BrownfieldModule-by-moduleNative bridgeCo-existence
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

What you get at the end.

A production-ready React Native project, plus everything around it to manage and develop the app yourself.

  • The app itself, iOS and AndroidBoth builds in App Store Connect and Google Play Console, published under your own developer accounts. You are the legal owner of the listings.
  • Codebase with TypeScript and CIFull source code, a monorepo setup where appropriate, GitHub Actions for PR checks, and EAS configuration for builds and OTA updates.
  • Documentation and architectureBuild instructions, a deployment runbook, ADRs for the key architectural decisions and an overview of all third-party services used.
  • Monitoring from day oneSentry for crashes and JavaScript errors, performance traces for slow flows, and a logging pipeline you can extend yourself.
  • Handover to your teamTwo knowledge-transfer sessions, a short video walkthrough of the codebase and a week of pair programming with your developers who will be involved in maintenance.
  • Maintenance contract (optional)Ongoing monitoring, dependency updates, security patches and further development. Fixed monthly price, with clear response-time levels per ticket priority.

How a React Native project runs.

1

Introduction and scoping

A conversation in which we understand what you want to build, for whom, and which stack it fits. We assess whether React Native is the right answer for your case, and we will tell you honestly if Flutter or native is a better fit. By the end of this conversation you will have a direction, a first outline of scope and an idea of the project.

2

Planning and design sprint

We draw up a sprint plan, sketch the architecture, choose the specific stack components and, where it makes sense, run a short design sprint for the most important screens. For production apps, we run a parallel spike on the most performance-critical screen, so that assumptions are validated up front rather than during the build.

3

Build in sprints with OTA updates

Every sprint delivers a working build on TestFlight and Internal Testing. You test along with us, and so do stakeholders, and feedback is rolled out over the air via EAS Update. The team works incrementally: core flows first, edge cases later. Code reviews, automated tests and performance checks are part of the cycle, not something done once at the end.

4

Store publication and rollout

We prepare the App Store and Google Play listings, screenshots, privacy disclosures and review submission. We guide the first publication and handle any reviewer questions that come with it. For B2B apps, we often choose a phased rollout: internal distribution first, then limited production, then a broad rollout.

5

Management and further development

After go-live, the team keeps monitoring sharp, processes the first feedback and makes sure dependencies and OS targets keep pace. OTA updates cover small fixes and JavaScript changes, while store releases are used for new native modules or permissions. Further development runs in new sprints, with clear prioritisation based on data and user feedback.

Who we build React Native apps for.

Four audiences for whom React Native, and the way we work with it, delivers proven value.

Founders

Fast to production

You want a working app on both platforms without setting up two native teams. We work with a fixed sprint cadence, OTA updates for rapid iteration and a production-grade foundation from the first commit. No MVP that you later have to rebuild from scratch.

Teams with React experience

Web developers moving into mobile

Your team knows React, TypeScript and modern front-end tooling. With React Native, you share components, hooks, validation schemas and design tokens with the web app. The step into mobile is an extension of existing knowledge, not the build-up of a new specialism.

B2B organisations

Apps with shared branding

For business users where the app is the digital extension of your brand, and where iOS and Android need to feel consistent. Can be combined with SSO, identity providers and your existing back office. See building a B2B app for details.

Enterprise & brownfield

Phased migration from native

You already have a production app in Swift or Kotlin and want to move to React Native without a big bang. We add RN as a module to the existing app, start with a single screen and expand where it makes sense, the model Meta itself uses.

Fabian van Dijk Business developer · Appfront

First point of contact for React Native projects at Appfront. Reach him at fabian.vandijk@appfront.nl for a no-obligation conversation about when React Native fits your stack, and when Flutter or native is the honest answer.

Frequently asked questions about React Native.

What clients usually want to know before we start.

React Native or Flutter: which should we choose?
React Native is the default, unless there is a strong argument for Flutter. React Native has the largest ecosystem, the most Dutch developers and the easiest transition for web teams. We choose Flutter when there are heavy graphics, complex animations or a strong preference for Dart, for example with gaming-style UIs or teams already working with Flutter. A third consideration is brand uniformity: Flutter draws every pixel itself, whereas React Native uses native controls that differ slightly per platform.
React Native or native (Swift / Kotlin): what is the difference in practice?
Native remains the right choice for AR/VR, real-time vision, complex camera flows, hardware-sensitive IoT, Bluetooth mesh, or wherever premium platform UX is a commercial requirement. For everything else — portals, dashboards, e-commerce, healthcare, field service — React Native is often faster and cheaper, because you don't build twice or maintain two teams. We often work in a hybrid way: ninety-five per cent React Native, with the few performance-critical parts built as native modules.
Is React Native fast enough for our app?
For the vast majority of business and consumer apps, yes. With the New Architecture (Fabric and TurboModules) and the Hermes engine, baseline performance is close to native. For specific graphics-heavy screens, we can use React Native Skia or build those screens locally as a native module, without touching the rest of the app. If in doubt, we run a short performance probe on the heaviest screen up front, so you have certainty before committing to a project.
Use Expo or "bare" React Native?
In practice, we start with Expo (managed workflow) by default. The developer experience is by far the best, EAS Build and EAS Update are production-grade, and you can run "prebuild" at any time to add native code. We only choose bare RN if you need native modules that don't work via Expo Modules — rare these days, as Expo now supports most popular native modules as first-class.
How do OTA updates via EAS Update work?
EAS Update lets you roll out JavaScript and asset changes over the air without a new app store build. Bug fixes and small features can reach users quickly, and you can differentiate updates by release channel (beta, staging, production). Native changes — new permissions, new native modules, new iOS or Android target versions — do require a new binary in the App Store or Play Store, because Apple and Google always review those. Microsoft App Center is now end-of-life; EAS Update is the modern successor.
How do you handle performance and re-rendering?
We use React.memo, useMemo and useCallback where they make sense, use Shopify FlashList instead of the standard FlatList for long lists, and MMKV instead of AsyncStorage for synchronously fast storage. Animations run via Reanimated on the UI thread, not the JS thread. We profile with the Hermes profiler and React DevTools, and catch performance issues in production via Sentry traces. It isn't a separate "optimisation phase" but a continuous track alongside the build.
What about accessibility in React Native?
Accessibility is built in from day one. Semantic roles via accessibilityRole, focus management via accessibilityState, contrast checks against WCAG 2.2 AA, and screen-reader tests using VoiceOver on iOS and TalkBack on Android. For B2B apps that fall under public tenders or accessibility regulations (EN 301 549), we also deliver an accessibility report listing known issues and mitigations.
Can we migrate our existing native app in phases?
Yes. We add React Native as a brownfield module to an existing Swift or Kotlin app, start with a single screen or feature, and expand where it makes sense. This is the model Meta itself uses, and it significantly reduces migration risk compared with a full rewrite. You keep production stable while the modernisation proceeds at its own pace, with no big-bang release and no feature freeze lasting months.
Does React Native also work for a single-page web app alongside the mobile app?
Yes, and what's more: for teams that have or are building a React-based single-page application, React Native is often the logical extension. Components, hooks and validation schemas can be shared between web and mobile in a monorepo. In that case we use Solito or Expo Router for Web to unify routing as much as possible, and share design tokens via a shared design-system package.
Why do you choose TypeScript, Jest and Detox / Maestro?
TypeScript is standard in every new React Native codebase, with strict mode and generated types wherever the back end provides them. We use Jest for unit tests and Detox or Maestro for end-to-end flows on real devices and simulators, depending on the setup you want. During development we use Reactotron to inspect state, network traffic and async storage. The aim is for automated tests to catch regressions, rather than manual regression testing just before a release.
Do you work with our in-house developers?
Almost always. We hand over knowledge throughout the project, schedule pair-programming sessions with your developers, and make sure the codebase is easy to understand for whoever works on it after us. For longer-term support, we look at capacity needs via hiring an app developer. The ultimate goal is always that your team can manage and develop the app itself, with us as a fallback for specific areas of expertise if needed.

Talk to us about your React Native app.

A half-hour introductory call, no obligation. We listen to what you want to build, look at how it fits your existing stack and team, and give you honest advice (React Native, Flutter or native) rather than automatically selling our own work.

Edit content