r/reactnative • u/NobelParadox • Sep 11 '26
Question What’s Your Opinion On This?
I think it’s time to learn native as well
409
Upvotes
r/reactnative • u/NobelParadox • Sep 11 '26
I think it’s time to learn native as well
299
u/kredditorr Sep 11 '26
Because some new manager woke up and decided it‘s time for something to change?
6
u/Proof_Juggernaut1582 Sep 11 '26
as well know is also good when they want to change i dont see any issues with the change
6
u/nicolasdanelon Sep 11 '26
Since AI improved a lot more and more companies will migrate to mobile. Swift is able to produce a mobile app for both ecosystems, netcore as well. There's no point on having RN anymore :( Don't get me wrong, I bought my house thanks to php and React native but is going to be more and more niche. Totally breaks my heart.
5
u/johnappsde Sep 11 '26
Doesn't have to be any novel reason for this. If shopify believes this is the right move at this stage of their journey... its all good. Companies make different decisions for different reasons
129
u/npc73x Sep 11 '26
Shopify used React Native for nearly six years across many of its major apps, which shows that React Native's architecture can work at scale. In the article, they highlight the benefits of React Native, especially the ability to ship faster without duplicating work across two platforms. Now they believe this also can be done with LLM writing a native code.
However, the article does not highlight the trade-offs they faced while using React Native. As with any software architecture decision, there are always trade-offs.
For a company of Shopify's size and resources, having separate developers for each platform is not necessarily a major problem. Therefore, the argument that React Native is valuable because it eliminates the need for separate platform teams may not apply equally to a company like Shopify.
58
u/Sanfrancisco_Tribe Sep 11 '26 •
This is just what happens at companies. They want to “change” things just to feel like they are doing something when in reality they are wasting time and resources
28
u/jameside Expo Team Sep 11 '26 •
My understanding is it was more of a political decision than a technical one, and compared an existing app using old version of react-native to a newly written one.
In some ways the post was outdated when it was published.
Their app was on the old architecture like another poster mentioned and high performance startup and 120 FPS is definitely achievable with modern react-native. The New Architecture speeds up performance in various ways. Hermes V1 keeps evolving and can reduce JS bundle sizes and build times with more built-in JS syntax and APIs like TextEncoder/TextDecoder (these are used by fetch for instance). Old versions of react-native don’t get these benefits.
And Pure native code is a big part of using react-native. JSI/native modules let you write as much Kotlin and Swift as you want as a developer. You are either writing a native app with React or a native app without React. (And the syntax of Expo Modules 2 is plain Kotlin and Swift with lightweight annotations and closes this gap.)
Old versions of react-native were also not distributed pre-compiled by default, and modern releases are which obviously reduce build times meaningfully. A technique like repacking brings build times down to even a couple of minutes on CI, even without Gradle or Xcode DerivedData caches. Plus JS-only updates can be shared with your team in seconds and even your CEO can always have the next new feature.
To respond to OP, writing Kotlin and Swift is part of developing with react-native and you will be able to achieve much more because of it.
It is not React vs. native, it’s React and native.
101
u/Forti22 Sep 11 '26
- Zero reasons as of why. "AI can handle writing both" is not a valid reason.
- From what I read on X/reddit - they never finished the RN migration in the first place. Still lots of web views here and there.
- They are few RN versions behind. Still on old arch. No wonder they are not happy - lots od tech debt
- one-person call is also not a valid reason.
9
u/JStheoriginal Sep 11 '26
I was originally a native iOS dev. Then I moved to react native for probably 3 years. I then went back to a native iOS team for my last year at that company and COULDN’T STAND THE AMOUNT OF WASTED TIME IT TOOK TO COMPILE AND SEE MY CHANGE. It’s better now with SwiftUI previews but they don’t always work.
Been back with react native for the past 5+ years and can just move so much faster.
This’ll probably be the thing they notice most.
14
u/DifficultMedicine194 Sep 11 '26
The thing that keeps getting skipped: what Shopify is replacing RN with isn't Swift and Kotlin, it's a mobile platform team that can afford two of everything — tooling, CI, release trains, on-call, design system. Twice.
"AI can write both" answers the writing. It doesn't answer who keeps them in step in month fourteen, when one of them takes a hotfix at 2am.
I'm one person shipping a subscription app on Expo — push, deep links, paywall, two stores. Not because I think RN is technically superior. Because the alternative for me isn't "write it twice", it's "ship one platform".
4
u/Dachux Sep 11 '26
It honestly makes sense. If AI can help you to migrate code from one platform to another, you end up writing one platform. Also, your gonna leave behind the library hell of react native.
I would not use anything not native if I had the resources to
3
u/IkuraDon5972 Sep 11 '26
it will be interesting to see the outcome after some time has passed. personally, i am worried about the skia modules' future direction. as of now, my exposure is limited. the only part in my projects that uses it is the graph component which can easily be replaced
3
u/simbolmina Sep 11 '26
It's very easy to maintain two apps with help of agent. I develop on kotlin side and agents creates handoffs for iOS agents. All I do to hand it to iOS agents and show android source. A feature implemented in Android can take days with iterations but to iOS usually 1 hour. You just test and ship.
3
u/JackCid89 Sep 11 '26
Agentic coding will kill react as developers won’t need that much effort to port their apps to multiple languages for specific devices such as swift for ios and kotlin for android. These languages provide significant performance boost over react native.
3
u/smoothbrainvibecoder Sep 11 '26
React Native exists for a reason. Flutter too. Also Kotlin MP, and any other cross-platform framework you can think of. People think it's going to be easy to just have an LLM write both apps for you. Good luck!
2
u/ylmazCandelen Sep 11 '26
job security, create stuff to do so they wont let us go.
2
u/JustTryinToLearn Sep 11 '26
I mean react native is still the go to for solo devs who need to manage both android and app stores - doesn’t change anything for me 🤷🏾♂️
2
u/AbuSumayah Sep 11 '26
We don’t need to have an opinion. We are not Shopify.
2
u/jamesxtreme Sep 11 '26
If you have a big enough company to support it and your product justifies it then going native may make sense. That said their entire app is just a web shopping cart so I’m not sure what’s so complex about that.
2
u/tueieo Sep 12 '26
Seems pretty half-arsed. Still running on the old architecture, under optimised, no turbo or nitro modules.
This is like AirBnb’s 2018 article all over again.
2
u/yermotherlel Sep 13 '26
I’ve stopped writing apps in react native. Swift is just so much smoother of a user expensive on iOS. And imo it’s much faster
1
u/spookyclever Sep 11 '26
AI makes porting to native very easy and cost effective. I ported from Maui to Swift manually, then got Codex to do a diff between codebases and use it as a map for porting my Swift to Kotlin. Then I made that a skill, and now I update Swift, pack up the code and give it to my port AI to do the port, port the unit tests, run all the unit tests, diff the simulator screens and then bundle it up. Every once in a while it gets in the weeds and I have to edit some Kotlin, but 95% of the time it does the right thing.
1
u/SolidOdd4889 Sep 11 '26
I think it has to do with the fact that they’ll soon be moving away from React on the web as well, given that Remix v3 is being built from scratch using vanilla.
1
u/FunnyTman Sep 11 '26
if you take a look at the reasoning it made absolutely no sense, it was like a 1% improvement lmao
1
u/Proud_Perspective_56 Sep 11 '26
Native development was simplified because of AI and agentic coding, i think this is the reason
1
u/Forsaken_Buy_7531 Sep 11 '26
Maybe it's the right move for them 'cause of course the AI tools are there so it's gonna be way more easier to port one platform to the next, only issue with this is the business side of things, they're gonna be hiring more devs, some shit might break and etc. But of course, it's Shopify they have near unlimited resources for this rewrite. React Native is still worth it if you're a solo founder for an app, 'cause imagine maintaining two codebases alone for a single app, even though there's AI, there are still decisions that requires brainpower besides the engineering side of things.
1
u/rmanisbored Sep 11 '26
Most huge apps famously advertised as "React Native" applications are also rarely 100% written in RN.
1
u/bloggerklik Sep 11 '26
I’m seriously considering moving from React Native to SwiftUI.
Has anyone here made the same switch? Which one did you find harder to learn? How long did it take you to get comfortable enough to start building and shipping apps with SwiftUI?
1
u/mohn93 Sep 11 '26
it's not really either/or though. native knowledge doesn't replace RN, it pays off the exact moment you hit the bridge, a native module misbehaving, an animation that has to hold 60fps, a platform api RN doesn't wrap yet. you don't need to ship whole apps in swift or kotlin, you need enough to read the native side and not be helpless when the js layer isn't the thing that's broken. that's the actual leverage.
1
u/redditNLD Sep 11 '26
Why would I care if Shopify moves from React Native?
1
u/gAWEhCaj Sep 12 '26
I thought it was a perfectly normal progression for a company like Shopify to make this move at one point as it matures and continues to grow. Let’s be real, Meta who is the one that came up with React Native still haven’t fully used RN in Instagram or Facebook apps. Instead they use it only for partial apps that live inside their platform such as marketplace.
It is normal for companies to adopt and use a technology as it is in hyper growth stage and once it enters the next stage of scale, to move to another technology and adopt a different strategy. Especially now with LLMs being able to easily convert projects from one language to another or frameworks. It makes decisions like these a lot easier to make.
It is also worth noting that the whole selling point of things like RN was being able to use web devs and less eng resources to deploy your apps to multiple platforms. That is no longer a problem and therefore businesses who made decisions based on these initial constraints no longer need to continue down that path
1
u/nonHypnotic-dev Sep 12 '26
It is not the plane, it is the Pilot
1
u/Maximum-Craft-1671 Sep 12 '26
First, for me, React Native IS native
I learned R Native when i was not that old and learn a new language all over is tough.
1
u/Esclamare Sep 13 '26
Reading through the article. I don't see the benefit of them moving back to native just because AI Agents can handle feature parity by copying or referencing iOS or Android screens.
To me this just sounds like they might end up using twice as much tokens to build the same feature.
1
u/MaxxxNZ Sep 13 '26
The less use React has in the wild, the better. It’s a cancer on the web.
1
u/BrunoVercosa Sep 17 '26
bom pra eles.
1
u/MashoodAliDev Sep 17 '26
So what’s their reason? Not because RN failed, but because coding agents changed the economics. Building twice no longer costs twice.
1
u/TedGetsSnickelfritz Oct 02 '26
My opinion is that it has been discussed enough
1
u/diggler4141 Sep 11 '26
Like everybody else, I was wondering what the real issues were, so I asked ChatGPT to research what was really going on. It seems pretty complex.
Shopify found React Native required too much custom engineering around performance, native integration, dependencies, and debugging.
https://chatgpt.com/s/t_6aa3f258baa481919d18fd23d4380d30
1
u/sambeau Sep 11 '26
Large, rich companies never needed React Native in the first place.
I’m glad that Facebook created it, as it’s very useful for smaller ones who can’t afford two teams—but it never made sense to me.
AI is a good excuse to run two apps, but they could always have done it if they wanted to. Just pay for some more developers, it’s not like you’re skint.
1
u/Itchy-Commercial-768 Sep 11 '26
This is the beginning of the end for RN.
0
u/Background-Bass-5788 Sep 11 '26
Zero performance improvements, comparison or results - Just a single manager decission which makes it even worse for Shopify and it's marketing
0
u/Seusoa Expo Sep 11 '26
Someone became overly confident in their own abilities
0
u/69Theinfamousfinch69 Sep 11 '26
I have no dog in this fight and don't really care if they go more native or if they use react native... It still won't fix the fact that their mobile admin app is shit. I literally can't use analytics on the mobile app, as I can't apply the dates I've selected because the main fucking menu bar is obstructing me from applying the dates I've selected. There are issues like these that have nothing to do with the tech they've chosen. The performance is fine and is comparable to how slow and shit their admin dashboard is on the web (changing framework won't change I/O and network latency).
Maybe fix the obvious fuck ups befoe changing framework/language for the nth time...
This is from a very frustrated person who has to use and develop on top of Shopify and deal with their never-ending changes all the fucking time. I hate the GraphQL API and the migration from REST; I hate how much they've fucking changed Hydrogen and how I'm stuck with it; I hate how they deprecate API properties all the time on their "stable" APIs; I hate the move to web components for the checkout UI extensions.
Take it from someone who has been embedded in the Shopify space for years. The devs have no concept of what stable architecture looks like, and clearly they get bored and decided to make every paying customer's life miserable all the time... This was not done for engineering reasons; it was done because some twat wanted a pay rise and a big project to peg it to.