Shopify dropped React Native. Should you still hire iOS and Android engineers?

Yes, but not the way you did in 2020. Shopify is moving all six of its apps from React Native back to Swift and Kotlin, and says AI cut the cost of building twice enough to do it. At Shopify, the move to native does not bring back separate iOS and Android teams, and it does not remove the need for native expertise. For a decade, a cross-platform framework was how a company avoided funding two mobile teams. In September 2026, one of the most visible large-scale React Native adopters walked away from it. Days later, Gergely Orosz relayed that OpenAI’s head of engineering had told him they stopped hiring iOS and Android engineers.

Both stories point the same way, and both are easy to over-read. This piece covers what Shopify and OpenAI actually said, what we found when we checked OpenAI’s job board, and what it means for the next mobile job spec you write.

Key takeaways

• Shopify’s Head of Mobile, Mustafa Ali, announced on September 10, 2026 that all of Shopify’s mobile apps will move from React Native to native Swift and Kotlin. The Shop app already shipped fully native, 12 weeks from proof of concept. A core group of six engineers built the foundations, and feature teams joined midway.
• The stated reason is cost, not performance: coding agents made building the same feature on both platforms cheap enough that sharing code is no longer the deciding factor. In January 2025, the same team called React Native’s future bright.
• Gergely Orosz relayed at a WorkOS event in New York that OpenAI’s head of engineering stopped hiring iOS and Android engineers because the models are good enough at the work.
• OpenAI’s public job board still listed seven mobile roles on September 30, 2026, three of them posted in September. By role: three foundations or platform roles, three Android product-feature roles, and one mobile plus full-stack hybrid. Only one is an iOS role.
• The hiring change: one team where the same engineer ships on both platforms, a few deep platform specialists, and people who can verify agent output. Shopify is still hiring mobile engineers.

What did Shopify announce about React Native?

Shopify is migrating every mobile app it runs from React Native to fully native Swift and Kotlin, starting with the Shop app, which shipped fully native after a 12-week rebuild. Mustafa Ali, Shopify’s Head of Mobile, set out the decision in “Native is now the future of mobile at Shopify” on September 10, 2026. His one-line reason: “building the same feature in Swift and Kotlin no longer carries the cost it used to.”

The reversal is notable because of how well the original bet went. Shopify went all-in on React Native in 2020 for three reasons: stop building features twice, let developers work across the stack, and stop chasing feature parity. Gergely Orosz’s September 29, 2026 analysis in The Pragmatic Engineer counts six apps moved to React Native over five years. In Shopify’s January 2025 retrospective, the team reported sub-500ms screen loads and more than 99.9% crash-free sessions, and wrote that the future of React Native was bright.

The facts behind the new decision, from Shopify’s two September posts:

• Scope. All mobile apps move. The four named are Shopify, Shop, Point of Sale, and Inbox. The main Shopify app, with 300+ screens, widgets, and an Apple Watch app, is underway and due later this year.
• Team. “A core group of six engineers built the native foundations and the app’s main user journeys,” per the Shop app migration write-up. Feature teams joined midway to validate their areas.
• Method. Greenfield rebuild, not gradual migration, because LLMs are good at building Swift and Kotlin features using the React Native version as reference.
• What did not change. Ali is explicit: “Native still means building and maintaining software on two platforms, that cost has not disappeared.”

Shopify also said React Native “remains an excellent framework.” The argument is not that React Native got worse. It is that the main thing it saved you, writing everything twice, is now much cheaper.

Why is building twice so much cheaper now?

Coding agents can port a feature from one platform to the other and compare the two implementations over time, so the parity work that justified a shared codebase shrinks. Ali told The Pragmatic Engineer that agents “are quite good at porting a feature from Android to iOS or the other way around,” and that maintaining two codebases “was a big deal before LLMs, but not anymore.”

The part most commentary skips is that Shopify did not just point a model at the old code. Ali writes that one-shotting features from the React Native codebase “doesn’t work” and produces “a huge amount of unmaintainable code.” Instead, Shopify built a system called Helix that breaks each screen into small checkpoints. Each checkpoint has to pass tests, match the running app in a visual review, survive two adversarial code reviewers, and get a human’s approval before the next one starts.

Helix is what Ali describes for the ongoing Shopify app rebuild. Around both migrations sits more verification infrastructure:

• One shared test suite (Ali, to The Pragmatic Engineer) that validates business logic in both Swift and Kotlin, so a feature cannot ship until it passes the same tests on both platforms.
• Headless business logic that runs on a desktop and is exposed to agents through a CLI, so they iterate in milliseconds instead of waiting minutes on a simulator. Ali describes this as work in progress.
• Tardis, built for the Shop app migration, a debugging tool that gives agents structured access to live app events, logs, and state, and compares React Native and native behavior at named checkpoints. The Shop team paired it with a subagent workflow that documented, planned, implemented, and reviewed parity for each feature.

Read that list again as a hiring manager. The work that made the migration possible is test design, review loops, and tooling that lets agents check their own output. None of it is “write the Swift.” That is where the skills shift is, and it is why the migration write-up says, in plain words, “Native expertise remained essential.” Generated code could meet feature requirements and still bring duplication, architectural drift, or performance problems. Shopify caught those with repository guidance, linting, tests, static analysis, performance checks, and code review, with platform knowledge guiding the architecture and the reviews.

For more on how engineering roles are changing around agents, see our guide to AI-native engineering.

What the native Shop app gained

On Shopify’s own measurements, the native Shop app starts 23% faster on iOS and 50% faster on Android, and crashes about ten times less often, than the React Native version it replaced. The numbers come from the Shop app migration post, which measured cold start from tapping the app icon until the home feed is visible.

The other reported changes:

Measure	React Native	Native	Change
Session stability	99.5%+	99.95%+	about 10x fewer crashing sessions
Android app size	baseline	109 MB smaller	−37.2%
iOS app size	baseline	1 MB larger	+1.5%
Android release build time	baseline	about 75% shorter	iOS unchanged
Android feed scrolling	not reported	120 FPS on a Pixel	—

Two cautions before anyone rewrites a roadmap on these numbers. First, they are the company’s own measurements of its own migration, not an independent benchmark. Second, the Shop app had not moved to React Native’s New Architecture. When Shopify moved its Shopify and Point of Sale apps there, Ali told The Pragmatic Engineer the gains were “modest”: about 10% faster startup on Android and 3% on iOS. Some developers have argued the comparison flatters native for that reason, as InfoQ’s coverage on September 16 notes.

The honest reading is that the performance gain is a bonus. The decision rests on cost.

Did OpenAI really stop hiring iOS and Android engineers?

Partly. OpenAI’s head of engineering told Gergely Orosz they stopped hiring iOS and Android engineers and stopped pulling internal specialists onto mobile work, but OpenAI’s public job board still listed seven mobile roles on September 30, 2026. The claim comes from Orosz’s fireside chat with Michael Grinich at WorkOS’s New York office, written up by WorkOS as “Software engineering is getting a second material” on September 18, 2026. According to that recap, the reason was that the models are good enough at the work. It is a secondhand account of a conversation, not an OpenAI policy statement.

So we checked. On September 30, 2026, OpenAI’s public job board (Ashby) listed seven roles with iOS, Android, or Mobile in the title. Three were posted in September. Grouping them by what the role actually owns tells a more specific story than “stopped hiring”:

The pattern in the descriptions:

• Foundations and platform. The two Applied Foundations roles build “reusable iOS foundations” and Android equivalents that other product teams depend on: sign-up, payments, safety. The Android Systems role says outright it is “not a traditional application-only Android role.”
• Hybrid. The newest listing, posted September 24, asks for Staff+ engineers with deep iOS or Android expertise plus experience “beyond mobile to frontend web or backend.” About half the work starts as native mobile.
• Product features. Three Android roles sit on product teams (Library, Ad Formats, ImageGen). Only one iOS role is listed at all, posted in January.

The data does not fully support a blanket reading. OpenAI is still posting single-platform Android feature roles, two of them in September. What we do not see is iOS feature hiring: the only iOS-titled role is a foundations role from January. And the newest listing asks for mobile depth plus web or backend work. The most we can say is that OpenAI’s current mobile postings lean toward platform layers and cross-stack engineers, with no iOS feature roles, and that hiring has not stopped. In WorkOS’s summary of the same talk, Orosz sees engineering in general settling into two camps, product engineers and platform engineers.

A caveat on our own data: a job board is a snapshot. Postings can be stale, evergreen, or already filled, and we cannot see internal transfers.

Is this the end of the mobile engineer?

No. It is pressure on the mobile job spec built around one language and one platform, and it continues a trend that started before coding agents. In June 2026, The Pragmatic Engineer reported that native iOS and Android titles were among the fastest-disappearing engineering job titles, behind frontend-only ones, and said Orosz first observed the drop in demand for native iOS and Android engineers in 2022. His 2022 research, as WorkOS recounts it, found startups dropping native mobile for React Native so one engineer could ship to every platform.

The irony is that Shopify’s reversal does not bring those titles back. Shopify never rebuilt separate iOS and Android teams. Ali told The Pragmatic Engineer that one lasting benefit of the React Native years is that “we don’t have a separate iOS and Android team, unlike most native shops,” and that “the same developer builds a feature on both iOS and Android.” He expects that to become more common. Shopify’s Head of Engineering, Farhan Thawar, put it more bluntly: React as the shared language “is now replaced by the English language.”

And Shopify is hiring. The announcement ends by saying the company is looking for mobile engineers, infrastructure engineers, and developers working at the intersection of AI and software engineering. It is also not the first swing of this pendulum: Orosz points out that Airbnb adopted React Native in 2016 and left it two years later.

For the wider picture of which technical titles are growing in the region, see our IT recruitment trends for Eastern Europe in 2026.

How should you write a mobile job spec in 2026?

Hire for one team that ships on both platforms, a small number of deep platform specialists, and the ability to verify agent output. Drop “5+ years of Swift” as the headline requirement. Here is how the old spec maps to what the Shopify and OpenAI evidence supports:

2020 spec	2026 spec	Why
Separate iOS and Android hires, or one React Native team	One product team; each engineer ships the feature on both platforms	Agents port features between Swift and Kotlin; Shopify runs one team this way
“5+ years Swift” or “5+ years Kotlin”	Deep in one platform, productive in the other with agents	Native expertise still catches drift and performance problems in generated code
Feature throughput	Verification: tests, review loops, parity checks	Shopify built Helix, a shared test suite, and Tardis to check agent output
Mobile only	Mobile plus web or APIs	OpenAI’s newest mobile role is about half native, half web and APIs
Platform specialist as a nice-to-have	A few specialists for performance, OS integrations, widgets, devices	OpenAI’s foundations and systems roles; Shopify’s widgets and Watch app

Four practical moves for the next opening:

1. Rename the role. “Mobile engineer (iOS and Android)” or “Product engineer, mobile” signals the one-team model. Shopify’s setup argues for it; OpenAI still uses platform titles, so if you are unsure, test both versions of the posting.
2. Interview for review, not recall. Give the candidate a feature an agent built on one platform and ask them to review the port to the other. Look for whether they catch the architecture and performance issues, not whether they remember an API. Our piece on AI in technical screening covers how to run this fairly.
3. Fund the harness before the headcount. Shopify says agents needed tests, parity checks, and fast feedback loops to be reliable. If your codebase cannot tell an agent whether it broke something, a second platform will cost you what it cost in 2020.
4. Keep one or two true specialists. Someone has to own startup time, memory, background work, and the platform APIs agents get wrong. That person is worth more now, not less.

Salary expectations follow the scope. An engineer who owns a feature on both platforms and reviews agent output is a senior profile, and priced like one. Our IT salaries in Romania for 2026 guide has current bands if you are hiring in the region.

What not to conclude from this

Do not conclude that you should rewrite your React Native app, or that mobile engineers are obsolete. Three limits on the evidence:

• Shopify is an outlier. It has used LLMs to build software since 2021, has hundreds of engineers who contributed to its mobile apps, and built custom tooling to make this migration work. Ali’s own framing is careful: “for our apps and our team.”
• The OpenAI claim is secondhand. It reached us through an event recap of a conversation, and OpenAI’s live postings show mobile hiring continuing, with no iOS feature roles and a lean toward platform and cross-stack work.
• The trade-off has not vanished; it moved. Two native codebases still mean two sets of platform bugs, two implementations to keep in sync, and parity enforced by process instead of by shared code. What changed is who does the typing.

The Pragmatic Engineer also notes the obvious corollary: AI makes React Native, Flutter, and Kotlin Multiplatform apps easier to write too. If your cross-platform app is fast and your team is productive, Shopify’s decision is a data point, not an instruction.

Frequently asked questions

Why did Shopify move from React Native back to native?

Shopify says coding models got good enough that building the same feature in Swift and Kotlin no longer carries the cost it used to. Agents now do enough of the implementation, translation, testing, and review that the cost of two platforms is no longer the deciding factor, while native kept its advantages: closer platform access, first-party tooling, and fewer dependency layers.

How long did Shopify take to rebuild the Shop app in native code?

Twelve weeks, from proof of concept to a fully rebuilt native app in both app stores. A core group of six engineers built the foundations and main user journeys, with feature teams joining midway to validate their areas.

Did OpenAI stop hiring iOS and Android engineers?

According to Gergely Orosz, speaking at a WorkOS event in September 2026, OpenAI’s head of engineering said they stopped hiring iOS and Android engineers because models handle the work well. OpenAI’s job board still listed seven mobile roles on September 30, 2026: three foundations or platform roles, three Android product roles, and one hybrid. Only one was an iOS role.

Should we switch our React Native app to native?

Not because Shopify did. The case depends on whether your team has agent tooling, shared tests, and platform specialists to review generated code. If your cross-platform app performs well, the cost argument for switching is weak.

What skills should a mobile engineer have in 2026?

Deep knowledge of one mobile platform, the ability to ship on the other with coding agents, and strong review and testing habits. Experience beyond mobile, such as web or APIs, is part of OpenAI’s newest mobile listing.

The bottom line

A cross-platform framework used to be how a company avoided two mobile teams. Shopify’s reversal shows AI now does that job, but it did not bring the two teams back. At Shopify, the one team that ships on both platforms survives the move to native.

Three things to take from it:

1. Default to hiring across platforms. Hire engineers who ship a feature end to end on iOS and Android, with agents doing the translation.
2. Hire for verification. The migration ran on tests, review loops, and parity checks. Screen for that.
3. Keep the specialists. Foundations and platform systems make up three of OpenAI’s seven open mobile roles. Shopify’s own team says native expertise remained essential.

If you are hiring mobile or product engineers in Romania or the wider CEE region and want a recruiting partner that reads a job spec the way an engineer would, we are former software engineers who can tell you which profile you actually need. You get a curated shortlist of three to five candidates, and an honest view of what the market will bear. Tell us what you are hiring for. For how we already work with agents on our own side, see should a recruiting team use coding agents.

---

Last updated: September 30, 2026. Sources verified September 30, 2026: Shopify Engineering, “Native is now the future of mobile at Shopify” (Mustafa Ali, Sep 10, 2026); Shopify Engineering, “Migrating Shop app from React Native to native” (Sep 10, 2026); Shopify Engineering, “Five years of React Native at Shopify” (Jan 2025); Shopify Engineering, React Native as the future of mobile (2020); The Pragmatic Engineer, “Why has Shopify dropped React Native?” (Gergely Orosz, Sep 29, 2026; free sections only); WorkOS, “Software engineering is getting a second material” (Sep 18, 2026); InfoQ, “Shopify Drops React Native for Swift and Kotlin” (Sep 16, 2026); The Pragmatic Engineer, “State of the software engineering job market in 2026, part 2” (Jun 9, 2026); OpenAI job board on Ashby (retrieved Sep 30, 2026; roles with iOS, Android, or Mobile in the title). Role grouping in the OpenAI chart is Wise Step’s own reading of the job descriptions.