Your industry breaks apps in its own way.
A field crew’s app and a patient’s app fail in different ways. We’ve written up how we build for each:
We build iOS and Android apps from one codebase, and we rebuild native apps that need a new foundation. Mercari and GasBuddy shipped theirs with us. US-based, since 2015.
Chat with our team over ZoomWhen an app stutters, or an update drops the button someone used every day, they don’t file a bug report. They uninstall and forget you were ever on their phone. Getting to launch day is the easy part. The bar is an app people keep for years, one that survives its own rewrites with its rating intact.
When Mercari decided to move its US shopping app to React Native, the app had over 1.8 million reviews averaging 4.8 stars, and two native codebases doing everything twice. A rating like that does not survive a careless rewrite. Our senior engineers worked inside Mercari’s team for the rebuild: writing production code, pairing daily, and running a six-month React Native ramp-up program so Mercari’s own engineers would own the app after we left. They do, the rating held, and their team wrote publicly about how the transition went.
GasBuddy asked for the same care with a complete rewrite: an app more than a million drivers use to save on gas, ten years past its last overhaul. Their CTO published his own account of the project, down to why he hired us: “There is no substitute for experience in getting the ‘idiom’ of React Native and avoiding the numerous dark alleys around state management, performance tuning and third party module selection.” And when Zoom wanted developers to drop its video into React Native apps, they brought us in to help build the Video SDK, announced at Zoomtopia in 2021.
“Infinite Red played a vital role in developing our React Native app from the ground up... We would not have successfully transitioned to React Native without their contribution. I highly recommend them for any React Native development.”
— Naoya Makino, former Senior Engineering Manager, Mercari
There are more names on the client list; NDAs keep them off this page.
Chat with our team over ZoomWe build on React Native’s New Architecture and Expo. One codebase ships to iPhone and Android, and a fix reaches both at once.
We’re a team of about 30, fully remote across the U.S., and an official Expo partner. We maintain Ignite and Reactotron, open-source tools your React Native engineers probably already run. We host Chain React, the React Native conference, and our engineers host the React Native Radio podcast and curate the React Native Newsletter. A question you ask after lunch gets answered today, not overnight.
A field crew’s app and a patient’s app fail in different ways. We’ve written up how we build for each:
How much will an app cost? We won’t pretend to know before we’ve seen it. The start of a project is when everyone knows the least, so a fixed bid is a guess with a signature on it. We help you answer a better question instead: what should I budget to have enough resources to succeed? Then we fit scope to that number, in breadth or depth, as the project teaches us more.
Is React Native actually good enough for a serious app? Yes. Mercari’s marketplace and GasBuddy’s app run on it, and so do Shopify’s store app, Coinbase, and Bloomberg’s consumer app. Bloomberg cut its dev time roughly in half; SoundCloud reported 85% code reuse. When something needs to be native, it is: React Native calls the same platform APIs a Swift or Kotlin app does.
Will you build the app, or teach our team to build it? Both, usually. We pair with your engineers from the first sprint; at GasBuddy our seniors worked daily inside their mobile team on prioritization, implementation, and testing. We build so your team can run it after we’re gone.
Can you take over or rewrite an existing app? Yes. GasBuddy’s was a full rewrite with hundreds of thousands of daily users on the old app, and it shipped. Full rewrite or screen by screen, we fit the migration to your release schedule.
When would you tell us not to use React Native? When it’s the wrong tool. A 3D game, or an app built around one platform’s newest hardware the week it ships: we’ve told prospects to stay native before. These days that’s a recommendation, not a goodbye — in the AI era our senior engineers ship native Swift and Kotlin too, so if native is what your app needs, that’s what we’ll build. The choice gets made by your app’s requirements, not our preference.
Who actually writes the code? Senior engineers, employed by us, in U.S. time zones. No offshore bench, no subcontractors. Often the person answering your question in Slack is the one who wrote the code that morning.
Chat with our team over Zoom — one of our owners will meet you and talk through where your product is, what’s slowing the build, and whether we’re the right team to ship it. Fully remote across the U.S.
There's no perfect time to get started. Whether you have a formal proposal or a few napkin sketches, we're always happy to chat about your project at any stage of the process.
One of our owners will meet with you on Zoom to answer all your questions. Will it be Todd? Jamon? Gant? Email us and roll the dice!
