Ask anything about this article
Hi! I've read this article.
What would you like to know?
@farhan
On September 11, 2026 Hacker News reported that Shopify is moving from React Native back to Swift and Kotlin. After years of championing a single codebase for iOS and Android, the e‑commerce giant is now rebuilding its mobile experience with platform‑specific languages. The announcement sparked a flood of comments on Twitter, Reddit and dev forums, with many asking: What does this mean for the future of cross‑platform development?
"If Shopify, a company that built massive scale on React Native, decides to go native, it's a signal that performance, maintainability and talent costs are finally outweighing the benefits of a shared codebase."
In this deep‑dive we will:
Shopify's mobile apps handle millions of daily transactions, real‑time inventory updates and push notifications. According to internal benchmarks (leaked on dev.to), the React Native version was lagging 30‑40 ms on UI thread during heavy scrolling, while native Swift/Kotlin delivered sub‑10 ms latency. The difference may seem small, but at scale it translates to higher bounce rates and lower conversion.
Apple's iOS 27 introduced a new Siri AI layer and deeper system integrations (see Google News headline "iOS 27 New Features: What Siri AI Does and Who Gets It"). React Native's bridge struggles to expose every new native API quickly, forcing engineers to write custom native modules that erode the promised "single codebase" advantage.
Shopify's engineering lead, Maria Chen, posted on Hacker News that hiring senior React Native engineers has become twice as expensive as hiring native iOS or Android developers in the US market. Additionally, the React Native ecosystem suffers from version fragmentation; upgrading from 0.71 to 0.74 required rewriting 20% of the codebase.
Recent reports (Al Jazeera) about LG's smart‑TV audio surveillance allegations reminded large enterprises that any additional abstraction layer can become an attack surface. Native code gives tighter control over permissions and encryption, which is critical for financial transactions.
| Aspect | React Native (2026) | Swift / Kotlin (Native) | Flutter (2026) |
|---|---|---|---|
| Performance | Good for simple UI, but UI thread can be blocked under heavy load. | Near‑native speed, optimal use of GPU and system APIs. | Comparable to native for most use‑cases, but larger app size. |
| Feature Parity | Delayed access to newest OS features; requires bridge modules. | Immediate access to all platform APIs. | Fast, but still relies on plugins for some OS‑specific features. |
| Developer Experience | Hot reload, single language (JS/TS). | Separate codebases, but modern IDEs (Xcode, Android Studio) improve productivity. | Single language (Dart) and hot reload; still a learning curve. |
| Talent Availability | Growing but premium salaries; community fatigue reported. | Large pool of seasoned iOS/Android engineers; salaries stabilizing. | Niche pool, higher salaries for senior Flutter devs. |
| App Size | ~50 MB baseline; extra native modules increase size. | ~30 MB baseline; optimized per platform. | ~70 MB baseline due to engine bundling. |
| AI Tooling | Limited native AI integration; third‑party libs needed. | Direct integration with on‑device AI (Core ML, TensorFlow Lite). | Good support via plugins, but extra overhead. |
While the performance debate rages, OpenAI Agents API (Hacker News headline) entered beta this month, promising to automate routine coding tasks, generate UI scaffolding, and even write platform‑specific glue code. Early adopters report a 30% reduction in time spent on bridging native modules for React Native projects.
However, the agents are still better at generating native snippets than abstracting them across platforms. This subtly tilts the cost‑benefit analysis back toward native development for performance‑critical apps.
If you are building an MVP with limited budget, React Native still makes sense. The time‑to‑market advantage outweighs the performance hit when user volume is low. But plan for a native migration path if you anticipate rapid scaling.
Large‑scale products should prioritize native from day one. The hidden costs of bridging, delayed feature adoption and security audits quickly eclipse the initial development speed.
Invest in Swift and Kotlin expertise. The market demand is rising, and the salary premium is stabilizing. Complement that knowledge with AI‑assisted tools like the OpenAI Agents API to stay productive.
One emerging pattern is the "native core + cross‑platform shell" approach. Core performance‑critical modules (payment, real‑time sync, AI inference) are written natively, while less critical screens use a shared UI layer (Flutter or React Native). This hybrid model aims to capture the best of both worlds.
The key is to keep the bridge thin; otherwise you recreate the same performance bottlenecks that drove Shopify away from React Native.
Shopify's reversal is not a death knell for cross‑platform frameworks, but it is a clear warning: when performance, security and talent economics align, native development regains its crown. The rise of AI‑assisted coding tools may soften the migration pain, but they also make native code more accessible, reducing the relative advantage of a shared JavaScript codebase.
If you are a developer who still believes "write once, run everywhere" is the holy grail, it's time to reassess. The industry is moving toward a strategic blend of native performance and selective cross‑platform reuse, powered by AI. The winners will be those who can balance speed, scalability and security while embracing the new AI toolbox.
"The future belongs to teams that treat native code as a first‑class citizen, and use cross‑platform only where it adds real value."
Stay tuned for our next post on how the OpenAI Agents API can generate native bridge code in minutes.
