In a surprising turn of events, Shopify has announced that it is moving its mobile app development back to native technologies—Swift for iOS and Kotlin for Android—after a multi‑year experiment with React Native. The decision, detailed in Shopify’s engineering blog, reflects a strategic shift aimed at delivering faster performance, deeper platform integration, and a more sustainable development workflow. This post unpacks the reasons behind the change, the challenges the team faced, and the implications for developers and merchants alike.
Why Shopify Adopted React Native in the First Place
When Shopify first embraced React Native in 2019, the goal was clear: unify the iOS and Android codebases to accelerate feature delivery and reduce engineering overhead. The cross‑platform framework promised:
- Code reuse: Up to 80% of UI logic could be shared across platforms.
- Faster iteration: Hot reloading and JavaScript tooling shortened the feedback loop.
- Talent flexibility: Web developers familiar with React could transition to mobile work more easily.
Early metrics seemed encouraging. Within the first year, Shopify reported a 30% reduction in time‑to‑market for new features and a 15% drop in platform‑specific bugs. These gains aligned with the company’s broader mission to empower merchants with rapid, reliable tools.
The Challenges That Prompted a Return to Native
Despite the initial upside, several technical and operational pain points emerged as the codebase matured:
1. Performance Bottlenecks
React Native’s bridge architecture, which translates JavaScript calls to native modules, introduced latency in high‑frequency interactions. For Shopify’s checkout flow, this translated into an average 150 ms delay per UI update, a noticeable slowdown compared to native implementations that typically stay under 50 ms.
2. Platform‑Specific Feature Gaps
Both iOS and Android released new APIs each year—Apple’s App Clips, Google’s Jetpack Compose, and advanced biometric authentication. Implementing these features required custom native modules, eroding the promised code‑share advantage. By 2023, roughly 40% of new Shopify mobile features were built as native extensions, increasing maintenance complexity.
3. Tooling and Debugging Friction
While JavaScript tooling is mature, debugging across the JavaScript‑to‑native boundary proved cumbersome. Developers often spent hours tracing issues that appeared in JavaScript but originated in native code, leading to higher Mean Time To Resolution (MTTR)—up to 2.5× longer than purely native teams.
4. Talent Retention
Shopify’s mobile squads found it challenging to attract senior engineers who preferred deep expertise in Swift or Kotlin. The hybrid skill set required for React Native was niche, resulting in a 12% higher turnover rate for mobile developers compared to other product groups.
Benefits of Going Back to Swift & Kotlin
Re‑investing in native development offers tangible advantages that align with Shopify’s long‑term roadmap:
- Speed and Responsiveness: Native UI rendering eliminates the bridge overhead, delivering sub‑50 ms interactions critical for checkout conversion rates.
- Full Access to Platform APIs: Immediate support for the latest OS features, such as iOS 18’s Live Activities and Android 14’s Privacy Sandbox, without waiting for third‑party wrappers.
- Improved Stability: Separate codebases reduce the risk of a single bug crashing both platforms, leading to a projected 20% reduction in crash rates based on internal telemetry.
- Developer Satisfaction: Engineers can leverage language‑specific tooling (Xcode’s Instruments, Android Studio’s Profiler) and stay current with community best practices, boosting morale and retention.
Moreover, the move does not abandon the lessons learned from React Native. Shopify plans to retain a shared business‑logic layer written in Kotlin Multiplatform, allowing non‑UI code to stay consistent across platforms while still delivering a truly native UI experience.
What This Means for the Shopify Ecosystem
For merchants, the shift promises a smoother shopping experience. Faster checkout pages and more reliable app performance can directly impact conversion rates—Shopify estimates a potential 1–2% uplift in sales per merchant due to reduced friction.
For developers, the change signals a renewed focus on platform expertise. Shopify will open new developer resources covering Swift and Kotlin best practices, as well as migration guides for existing React Native extensions.
Finally, the broader mobile community can view Shopify’s decision as a case study in the trade‑offs between cross‑platform convenience and native performance. While React Native remains a powerful tool for many startups, large‑scale, performance‑critical applications may eventually gravitate back to native stacks.
Conclusion: Key Takeaways
Shopify’s rollback to native development underscores a pragmatic approach to technology selection:
- Cross‑platform frameworks can accelerate early product development but may introduce performance and maintenance challenges at scale.
- Native Swift and Kotlin provide superior performance, immediate access to platform innovations, and higher developer satisfaction.
- Hybrid strategies—such as sharing business logic via Kotlin Multiplatform—can capture the best of both worlds.
- Merchants stand to benefit from faster, more stable apps, potentially boosting conversion rates.
As Shopify continues to evolve its mobile stack, the company’s transparent engineering blog will remain a valuable resource for developers navigating similar decisions in their own product journeys.
