Two different approaches with different operating implications. Below is the honest, agency-perspective comparison: who each fits, who each does not, and how we'd decide.
Pick React Native if consumer apps. Pick Native (Swift / Kotlin) if ar, ml on-device, low-latency audio, ble-mesh, gaming. The right call almost always comes down to scale, team, and where your real bottleneck is, not which tool ranks better on a generic feature comparison. We've made the call both ways across our portfolio in the same year.
| Dimension | React Native | Native (Swift / Kotlin) |
|---|---|---|
| Pricing | Open-source. Hire React Native engineers $120K-$200K base US. | Two engineering teams. iOS + Android $250K-$1M+ each per year for senior teams. |
| Learning curve | Medium, competent in weeks | High, months to mastery |
| Scalability | Shipped to 5M+ US users at scale. | Maximum performance ceiling. |
| Ideal for | Consumer apps; Marketplaces | AR, ML on-device, low-latency audio, BLE-mesh, gaming |
| Integrations | Expo, native modules, every major mobile SDK | Direct access to every iOS and Android API |
| Support | Open-source community + Expo paid. | Apple + Google + community. |
| Best at | Default cross-platform mobile framework. | Required only when feature requirements force it. |
Open-source. Hire React Native engineers $120K-$200K base US.
Two engineering teams. iOS + Android $250K-$1M+ each per year for senior teams.
Medium, competent in weeks
High, months to mastery
Shipped to 5M+ US users at scale.
Maximum performance ceiling.
Consumer apps; Marketplaces
AR, ML on-device, low-latency audio, BLE-mesh, gaming
Expo, native modules, every major mobile SDK
Direct access to every iOS and Android API
Open-source community + Expo paid.
Apple + Google + community.
Default cross-platform mobile framework.
Required only when feature requirements force it.
React Native fits when your bottleneck is what react native solves well. Default cross-platform mobile framework. Pairs with Expo for a 90%-of-cases stack. The operating reality is that consumer apps, marketplaces, cross-platform shipping with limited dev capacity is where it earns its keep, the rest of the feature surface tends to be a tie or close to one.
Native (Swift / Kotlin) fits when your bottleneck shifts. Required only when feature requirements force it. The right call for ~10% of US consumer apps. The cases where it actually outperforms react native cluster around ar, ml on-device, low-latency audio, ble-mesh, gaming. Outside of those, the choice is closer to a coin-flip, and operational fit usually decides it.
If we were scoping this for a US operator at the $5M-$30M revenue band, the call usually goes to React Native, it covers consumer apps with the least operational burden, the lowest learning curve for the in-house team, and the deepest ecosystem of agency partners who actually know it. We'd switch to Native (Swift / Kotlin) the moment ar, ml on-device, low-latency audio, ble-mesh, gaming becomes the binding constraint, and we've watched brands make that switch at the right time (usually) and the wrong time (occasionally). Below $5M revenue the answer is almost always whichever option lets the founder ship faster; above $50M the answer shifts toward whichever option produces the cleanest data and the strongest integration story with the rest of the stack. We've made this call both ways inside the same client portfolio in the same year, it is rarely a permanent decision and almost never the most important one the company will make this quarter.
Migration between React Native and Native (Swift / Kotlin) is a real engagement, not a weekend task. Expect to spend 2-8 weeks of calendar time depending on data depth, integration count, and team experience with the destination. The cost lives in the integration work, not the platform itself, most teams underestimate the rebuild of the analytics layer, the customer-facing flows, and the operational reporting that quietly sits behind the existing setup.
Common reasons teams leave React Native: ar-heavy apps; low-latency audio/video processing. Common reasons teams leave Native (Swift / Kotlin): most consumer apps where cross-platform suffices. Sometimes the right answer is to fix the operating model rather than switch tools, we've talked operators out of migrations that wouldn't have solved what they thought they were solving.
Before a migration we audit the existing data, freeze writes during cutover, and run staging in parallel for 1-2 weeks. The post-migration period is the highest-risk window for the business, search rankings, attribution, and customer-facing flows all need to be retested under load. We have seen brands lose 6-12% of revenue or attribution during sloppy migrations. Almost always recoverable. Never costless.
Send a 1-page brief with your stack and goals. We'll respond with a written recommendation between React Native and Native (Swift / Kotlin), and the cost / timeline math for the migration if it's the right call.