React Native development · Build
One React Native codebase for your iOS and Android apps
For companies with a web app that now need a mobile one, we share tokens, components and logic with the web. Our own port reused 91% of what the phone draws.
EngagementHourly · remote
Hours9–18 CET · 4 h overlap
StackReact Native · Expo · TypeScript
Proof4 case studies
The service in 4 parts
01 · Who it’s for
A company that has a web app and now needs a mobile one, or whose mobile app has to work without a network or talk to hardware.
02 · What we’ve built
- The web app, the mobile app and the API for remote identity verification at a German financial institution, with one computer-vision layer running on both web and mobile.Case study 10 →
- An app for passport applications, built with Expo and published on Google Play, used by agents who work in villages with no signal.Case study 09 →
- Our own design system runs on three platforms. When our marketing page was ported to a phone, 91% of the code the phone runs came from the web unchanged.Case study 01 →
- An Android app that could no longer be installed on current phones. We got it running on both current and older devices for a client who came back three years after the first engagement.Case study 02 →
03 · How we work
01 · SHARED OR PER PLATFORMWe keep a written list of what is shared with the web and what is written separately for each platform, with the reason for each split.
02 · MEASURED BEFORE WE QUOTEWe first measure how much code can really be shared with your web app, and only then give you a quote.
04 · Stack
React NativeExpoTypeScriptNative modulesTokens and logic shared with web
Proof
Where we’ve done this before
Case study 10 · Identity98%The web app, the mobile app and the API for remote identity verification at a German financial institution, with one computer-vision layer running on both web and mobile.Read the case study →Case study 09 · Identity1 working dayAn app for passport applications, built with Expo and published on Google Play, used by agents who work in villages with no signal.Read the case study →Case study 01 · Platforms74 / 678Our own design system runs on three platforms. When our marketing page was ported to a phone, 91% of the code the phone runs came from the web unchanged.Read the case study →Case study 02 · Platforms~100 / 30+An Android app that could no longer be installed on current phones. We got it running on both current and older devices for a client who came back three years after the first engagement.Read the case study →
FAQ
Questions about this service
That depends on your code, so we measure it on one real screen before we quote. In our own port, the measurement also showed that everything specific to the browser was in one file, and we found and listed it before the port began.
That is a separate service, hardware integration in React Native. It covers passport chips, payment terminals and other devices.
Yes. The US marketplace we took over already had mobile apps in use, and during the rebuild we moved them to Expo. A mobile user updates whenever they like, so the old backend kept running until analytics showed that its last user had left. That engagement lasted four years, our longest.
Next step
Describe the problem and we’ll come back with three options.
The first call takes 30 minutes, and you’re under no obligation.