Software Mansion

Software Mansion's React Native vs Swift and Kotlin: How We Choose the Stack

Original post React Native vs Swift and Kotlin: How We Choose the Stack

Article Summary

Michał Skałka from Software Mansion reveals the framework decision that saved Gobi's 120 FPS vision. The answer? It wasn't what they started with.

Software Mansion shares their battle-tested framework for choosing between React Native, native development, or hybrid approaches. Drawing from real projects like Gobi (migrated from RN to native), Filament (stayed RN with targeted native modules), and SeaPeople (fixed without changing stacks), they lay out exactly when each approach makes sense.

Key Takeaways

Critical Insight

The right mobile stack depends on your product's core interactions, performance needs, and team capabilities, not industry trends or default choices.

Continue reading

What This Article Covers

Problem

On an iPhone 13, SeaPeople's app pushed CPU usage up to 170% and kept the crash-free rate stuck at just 95%. The cause was poor background task handling combined with the screen re-rendering every second.

Solution

Software Mansion kept the existing React Native stack and fixed the code itself, tackling the re-render loop and cleaning up how background tasks were managed.

Impact

CPU usage fell from 170% down to 30%, and the crash-free rate climbed to about 99%. At the same time, a two-person team managed to ship a new Groups feature in just two weeks.

The article includes a detailed breakdown of how they built React Native Bottom Sheet (now open source) while discovering it wasn't enough to save their architecture.

This page summarizes “React Native vs Swift and Kotlin: How We Choose the Stack” by Software Mansion, published Nov 5, 2026. All credit for the original work goes to the authors.

Read the original on swmansion.com (opens in new tab)

AI tools for React Native

Browse all AI tools →