Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Shopify is moving its mobile apps from React Native toward native Swift and Kotlin, but that is not evidence that every team should rewrite. Shopify says coding agents changed the economics for its own products and organization; the right decision elsewhere depends on whether a team’s original assumptions still hold and what its own measurements show.
Why is Shopify moving away from React Native?
Shopify says its 2020 choice of React Native made sense: shared implementation could help more developers contribute and reduce the work of keeping iOS and Android features in parity. In its September 10, 2026 announcement, Shopify said coding agents had improved enough to reduce the cost of implementing, testing and reviewing features separately in Swift and Kotlin. It also said native development keeps the apps closer to platform capabilities and first-party tooling, while acknowledging that two platform codebases still cost more to maintain (Shopify’s announcement).
As an Amazon Associate I earn from qualifying purchases.
This is a change in Shopify’s circumstances and calculation, not a declaration that React Native cannot produce fast apps. Shopify said its React Native apps could be fast—and that its own were. The company also said it had described React Native’s future as bright in January 2025, a view it considered accurate for the information and circumstances at that time.
The announced scope is broad, but the status matters: Shop had already shipped as a native app, the Shopify app migration was underway, and Shopify said its other mobile apps would follow. The Shopify app was described as having more than 300 screens, alongside platform-specific surfaces such as widgets, Apple Watch functionality and Siri Shortcuts. Those were plans and status as of September 10, 2026, not confirmation that every app had completed migration.
#1 Best Overall
What did coding agents change—and what did they not?
Shopify’s case is that agents lowered selected costs of native development. It did not describe agents as a substitute for engineering expertise or quality control. For the Shop app, Shopify reports that one engineer used agents for a proof of concept that took a week and showed a close feature-for-feature port. That prototype was not production-ready. A core team of six then built native foundations and key journeys; feature teams joined during the migration to validate areas and address edge cases. Shopify says the project took 12 weeks from proof of concept to publication of the rebuilt app. This is Shopify’s own timeline, not a delivery estimate for another team.
Shopify’s internal Helix workflow broke work into small, ordered checkpoints for a screen or subscreen. A checkpoint had to demonstrate behavior through tests, match the running React Native reference under visual review, pass two adversarial code reviews and receive engineer approval before it was committed and work moved on. Shopify’s guiding standard was: “An attempt is allowed to be wrong. It is not allowed to ship until it isn’t.” (Shopify’s Helix account.)
Rank #2
For parity checks, Shopify says it built Tardis to give agents structured access to app events, logs and state, plus commands and comparisons between native and React Native runs. The comparisons considered event names, counts and payload fields while allowing run-specific values such as timestamps and page UUIDs to differ. Shopify also warns that generated code can satisfy feature requirements while creating duplication, architectural drift or performance problems. Its conclusion: “Native expertise remained essential.”
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What results does Shopify report?
The figures below are Shopify’s measurements as reported in its September 10, 2026 account of the Shop migration. They are first-party results, not independently verified benchmarks. Startup was measured from tapping the app icon until initial home-feed content appeared. The comparisons describe Shopify’s app and conditions; they do not predict results for another product.
| Measure | Shopify-reported comparison |
|---|---|
| iOS cold start | 2,466 ms native versus 3,200 ms React Native; Shopify reports a 23% reduction. |
| Android cold start | 2,233 ms native versus 4,433 ms React Native; Shopify reports a 50% reduction. |
| Session stability | 99.95%+ native versus historical 99.5%+; Shopify characterizes this as a tenfold reduction in sessions that crash. |
| iOS release app size | 68 MB native versus 67 MB React Native, an increase of 1 MB or 1.5%. |
| Android release app size | 184 MB native versus 293 MB React Native, a decrease of 109 MB or 37.2%. |
| Android release build time | Shopify reports the native version was approximately 75% faster; it does not state an absolute baseline in the comparison. |
| Android scrolling and navigation | Shopify reports a 120 FPS result in a cited recording on a Pixel device; this is a specific recording, not a guarantee across devices or workloads. |
The results illustrate why a migration may be attractive to Shopify, but they do not establish that agents make native development cheaper than React Native for the market as a whole. Nor do they isolate a causal result that another app should expect to reproduce.
Four questions to ask before following Shopify
The following decision aid comes from Kiell Tampubolon’s article, not from an official Shopify checklist (Tampubolon’s four-question article). Use it to test your own decision rather than treating Shopify’s migration as a prescription.
- What assumption does your current stack decision rest on? State the original rationale in one sentence. If it bundles separate premises—such as sharing code will reduce staffing needs and improve feature parity—split them so each can be checked.
- What would prove that assumption wrong, and has it happened? Compare the original rationale with concrete changes in your team, framework, tooling or product requirements. A new tool matters only if it changes the work or trade-offs you actually face.
- What does the abstraction cost now? Measure costs that matter in your app: startup time, binary size, build and test latency, platform-parity work, review time or access to platform-specific capabilities. Establish your own baseline; Shopify’s figures are not a substitute.
- When will you review the decision again? Set a date or a concrete trigger, such as a product requirement, a recurring performance issue or a change in team capacity. Without a review point, a choice made for old constraints can persist by inertia.
How should your team compare its options?
Do not reduce the choice to “shared code versus two apps.” Compare the costs and benefits under your product’s workload and your team’s ability to build and maintain it.
Recommended Free Tools
- Product and platform needs: Identify required platform capabilities, interface behavior, widgets and integrations, and establish whether the current approach limits them.
- Total engineering cost: Compare the savings from shared implementation with the effort of platform-specific work and maintaining parity. Include ongoing maintenance, not only initial development.
- Team capacity: Check whether you can staff iOS and Android work, sustain native expertise and handle the organizational overhead of separate implementations.
- Measured app quality: Use representative workloads to assess startup, stability, size, responsiveness, accessibility and release quality.
- Development feedback loop: Track build and test delays, simulator and device automation, review throughput and how quickly developers can reproduce issues.
- Migration risk: Plan how to preserve feature parity, account and session continuity, analytics events and accessibility, and how the existing app will be maintained during a staged migration.
- Tooling and framework costs: Examine upgrades, dependency support and platform integration work in your environment instead of assuming Shopify’s experience generalizes.
A rewrite also has an opportunity cost: people working on migration are not working on other product needs. If the evidence does not show that the current approach is failing—or that a different one materially improves outcomes—a working app is not a reason to rush into replacement.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
