React Native in 2026: where it is still the wrong fit.
React Native is a serious cross-platform option. That does not make it the right answer for every mobile product. The question is where the product needs platform depth, not what the team wants to reuse.
React Native is no longer the compromise it was once described as. It can be a strong choice when a product genuinely benefits from shared iOS and Android work.
That does not mean “one codebase” should become the brief.
Choose native when the platform is the product
We would think carefully before using React Native where the defining experience depends on new operating-system capabilities, highly specialised hardware, complex background behaviour or a platform-specific interaction model. A good bridge exists for many needs. The question is how much bridge work becomes the product.
Be honest about performance risk
Most business apps do not need extreme graphics performance. Some do. Real-time visualisation, demanding animation, audio processing, camera-heavy workflows and games deserve early prototypes on the technology that will carry them. Do not discover the constraint after the roadmap has been promised.
Cross-platform development still needs platform QA, store compliance, native permissions, device testing and decisions about where iOS and Android should behave differently. Reuse is valuable when it reduces repeated product work, not when it forces the same answer onto two different platforms.
Pick the stack that makes the difficult part easier, not the demo easier.
Decide from the first 2 years
List the capabilities the product must support over the next 2 years. Test the riskiest one. Then choose the smallest technical commitment that gives the product room to grow. React Native may be exactly right. It just should not win by default.
