What We Build with React Native
- new iOS and Android apps in TypeScript, usually with Expo, published to both stores;
- mobile versions of an existing React website or service, reusing its logic, data types and API client;
- apps with payments, push notifications, maps and social login, using actively maintained libraries;
- custom native modules in Swift and Kotlin for features that existing libraries don't cover.
React Native or Flutter
Both frameworks let you build a high-quality app from a single codebase. The choice usually comes down not to technical details but to your business context:
- if you have a React web product and a team developing it, React Native delivers more value through shared code and know-how;
- if the app has a complex custom design that must be pixel-identical on every device, Flutter is often the better fit;
- if neither applies, we compare the available libraries for your features and the experience of the team that will maintain the product.
For games, photo or video editors and animation-heavy interfaces, we recommend native development or other tools. For more on when a single codebase for two platforms makes sense at all, see our page on cross-platform apps.
Expo or Bare React Native
For most new projects, we recommend Expo: less manual iOS and Android configuration, simpler builds, and faster updates. Expo now supports custom native modules too. We work without Expo when a project has long existed that way, when full control over the native layer is needed, or when the app is embedded in an existing native project.
New Project or Upgrading an Existing One
For a new app, we set up TypeScript, well-planned navigation, and only actively maintained libraries from day one. If there's a React web version, we agree on which parts of the code will be shared and how to keep them in sync.
Existing apps often come to us with an outdated framework version, unmaintained libraries and a build that barely works. First, we restore a stable build, then upgrade React Native step by step so the app can still be released between stages. When an app is slow, we measure what is slowing it down on real budget smartphones, not just on high-end developer phones, and compare the results against the baseline after fixes.
Publishing and Life After Launch
A React Native app goes through the same App Store and Google Play review as a native one. We prepare the builds, store listings and data collection disclosures for both platforms. After launch, it's important to keep the framework and libraries up to date, because the longer you wait, the more expensive the upgrade. We can take this on as part of app support.
What to Prepare Before Kickoff
- A description of the app's features, or your existing design files.
- Access to your React website code and API documentation, if you want to reuse them.
- Developer accounts for the App Store and Google Play, or a decision on who will create them.
- For an existing app: repository access and the React Native version in use.
What Affects the Cost
- Code shared with the web: whether there's anything to reuse and how ready it is for reuse.
- Number and complexity of screens: standard forms and lists or custom animations.
- Native modules: how many features aren't covered by existing libraries.
- Backend: whether the same API as the website is enough or new endpoints are needed.
- State of an existing project: React Native version, number of outdated dependencies, test coverage.
We provide an estimate after reviewing the features and, for existing apps, a technical audit.
Frequently asked questions
Can we reuse code from our React website? Logic, data types and API code, yes. UI components will need to be rebuilt, because the app uses native components instead of HTML.
Can we update the app without store review? Small changes to the JavaScript layer, yes, as long as they don't change the app's core purpose and Apple's and Google's policies allow it. New native features are still published the usual way.
Our app is on an old React Native version. Does it need a rewrite? Usually not. Upgrading step by step is typically cheaper and safer than rewriting from scratch.
Is React Native suitable for a large product? Yes, many large apps run on it. What matters is a well-thought-out code structure and careful library selection.
Do you test on low-end phones? Yes. We test performance on low-end Android phones and older iOS devices, where performance issues show up first, and share test builds through TestFlight and Google Play closed testing.
Will you support the app after release? Yes, including updates of the framework and libraries, as part of our app support.
Why Promodex
Our mobile work includes Idram, as well as Fuelio and Omio, which we contributed to, part of 750+ projects since 2015. Our in-house team includes designers and mobile and web developers, so your mobile app and React website can evolve in sync. We don't outsource work, and we continue supporting the app after launch.