React Native App Development in Romania

What we deliver in React Native

We start from what you already have: types, business rules, components and conventions from your web app. Then we build navigation, sign-in, list and detail screens, forms, notifications and the offline layer in strict TypeScript. Styling uses NativeWind so the app mirrors your web design system, and server data is handled with TanStack Query for caching and retries. Native modules come in only when required: camera, scanning, Bluetooth, on-screen signatures.

• iOS and Android apps from one TypeScript codebase
• Signed EAS builds and internal test channels
• OTA updates for fixes, without re-entering the store
• Custom native modules where Expo does not reach

Expo, OTA updates and their honest limits

Expo shortens the path: cloud builds, vetted libraries, test channels and updates delivered inside the app. A wording fix or a logic bug reaches users in minutes instead of waiting for a store review. The limit is clear and we state it up front: native code changes, new permissions and SDK upgrades need a new build and a store review. When you need a module of your own, we write it and wire it in.

The app's API on our infrastructure

The server side runs on a Docker VPS in Frankfurt: a Node.js API, PostgreSQL on a private network, files on NVMe, mandatory TLS and no database port open to the internet. Push notifications go through the two platform services, and important events stay in your own logs. Data remains in the EU under a GDPR Article 28 agreement and standard contractual clauses, aligned with ISO 27001 practice and overseen in Romania by ANSPDCP.

What the included hours pay for

Requests begin in the DevOps Services section of the client panel, with a deadline you propose. On React Native work the hours go on Expo and React Native upgrades, new screens, fixes shipped over the air, store listing materials and integrations with invoicing, CRM or 4notify messaging. The allowance is per calendar month and does not roll over; extra hours are accepted and billed separately by the hour.

How we work

1. Open a request

   Raise a request in the client panel, share your web application code if there is one, list the screens you want and propose a date.

2. Scope and reuse

   We check which types, components and rules move over from the web and what needs native code, then estimate the effort in hours.

3. Test on a channel

   Signed EAS builds go to an internal channel, your team sends feedback, and small fixes ship straight away over the air.

4. Publish and hand over

   We publish from your developer accounts, then hand over the code, signing keys, OTA channels, documentation and a report of the hours used.

Use cases

Technology stack

• TypeScript
• React Native
• Expo
• EAS Build
• NativeWind
• React Navigation
• TanStack Query
• Zustand
• Detox
• Node.js 22

Frequently asked questions

• React Native or Flutter?

  React Native if your team already writes React: you reuse people, types and working habits. Flutter if you want an identical interface drawn the same way on both platforms and have no team constraint. In ordinary business apps the performance difference does not decide the choice.

• What is Expo and why do you use it?

  A toolset on top of React Native: cloud builds, vetted libraries, test channels and updates delivered inside the app. It removes manual setup of the iOS and Android projects and shortens the road to a first working build. When needed, we step outside its limits with modules of our own.

• How do OTA updates work now that CodePush is deprecated?

  With Expo, EAS Update serves JavaScript bundles from a channel you control, and the app downloads the update at launch. It covers text, logic and screens, but not native code, new permissions or SDK changes. We configure the channels and the rollbacks; it is the option we use by default.

• Can our React web team build the mobile app too?

  Largely yes. Types, the API client, validation and business rules move over almost directly. Navigation, gestures, permissions and store publishing differ, so we plan learning time at scoping. We deliver the first modules and the conventions, then your team carries on.

• How do I publish an Expo app to Google Play and the App Store?

  We create the signed build with EAS, prepare icons, screenshots, descriptions and privacy declarations, then submit from your developer accounts. We follow the review and treat rejections as part of the delivery. The accounts and signing keys stay with you.

• Do you host the API for the app as well?

  Yes, under the same plan. The API, the database and the files run on a Docker VPS in Frankfurt, with a private network and TLS. The included hours also cover the server side, so the project is not split between two suppliers who blame each other during an incident.