Co-founder & CTO
Written by
Jonas Albrecht
Published
Reading time
6 min read
Category
Mobile
The short answer
For most of the apps we build, React Native is the right call. One codebase, one team and shared logic with the web app usually beat the small performance edge of two native apps.
But most is not all, so we run every new mobile project through the same four questions.
1. How heavy is the device work?
Camera pipelines, real-time audio, Bluetooth hardware and complex background tasks still feel better in Swift and Kotlin. If the core of the product lives there, we go native.
2. Is there a web app too?
If the same product also runs in a browser, React Native lets us share types, validation, API clients and often whole feature modules. That saving compounds every sprint.
3. Who will own the code later?
We hand every product over at some point. A team of strong TypeScript developers will maintain React Native happily. A team of iOS veterans will not, and that matters more than any benchmark.
4. How fast do you need to learn?
Early products change weekly. Over-the-air updates and a single release pipeline let us ship fixes and experiments without waiting on two app store reviews.
Our default
React Native, with native modules where they earn their place. It gets you to market faster and keeps the door open to go fully native for one feature later.