शैडोइंग अभ्यास: Is React Native Dead? Shopify Is Leaving - वीडियो के साथ अंग्रेजी बोलना सीखें

Shopify just announced that they are moving all of their mobile applications from React Native back to Swift and Kotlin.

If you build with React Native, this is a pretty big headline to wake up to because Shopify has contributed to the React Native ecosystem for years,

including packages like React Native's Kia, Flashlist, and Restyle.

So whether you like it or not, this announcement carries weight.

Personally, it reminds me of the Airbnb moving away from React Native in 2018.

Even when I was working at Expo in 2025, I still heard people cite that decision as a reason they wouldn't give React Native a try.

Yeah, seven years later.

I hope we don't see that this time.

Because React Native has come a long way and Shopify is making this decision under very different circumstances.

So here's the official announcement from Mustafa.

He is the director of engineering and head of mobile at Shopify.

So in this announcement, Mustafa says

that the shop application already made the transition going from proof of concept to native application in the stores in 12 weeks.

Now if you've worked at a big company you know

that 12 weeks it's pretty damn good and the main Shopee 5 application is underway with the rest to follow.

So is React Native dead?

Personally I don't think so.

I still see a lot of value in React Native

but I also want to be honest about where mobile development is going because I've been experimenting with new models, including GPT-6 Astra.

And in my own test, they've become much better at working through multiple steps and checking their work.

And that makes building in an unfamiliar stack feel more approachable.

So my first reaction to this blog post is that this actually makes sense.

If an agent can help you build the Android equivalent of an iOS feature, the old argument about doing everything twice deserves another look.

So here's the full article of my grading shop app from react native to native

and I think there is a solid argument here.

Let's take a look at the details before we decide what this means for our applications.

Now let's start by mentioning that Shopify was already using native code

and then they decided to move to React Native

which it's also native I don't understand why they are saying native

but anyway so they moved to React Native in 2020 they were sharing code

and they were pretty successful made it easier for engineers to contribute across platforms and reduce the work of keeping features aligned.

So overall in this article, Mustafa mentions that the experience of working with React Native

and the benefits that they got by just migrating from native was great, at least in 2020.

So here's the TLDR.

The agents have reduced the cost of separate Swift and Kotlin implementations enough to change Shopify's decision.

Direct access to platform APIs and tools now carries more weight.

And he's also acknowledging that building separate projects for iOS and Android still has extra cost, right?

That hasn't changed.

But agents made it reasonable to reconsider that decision.

So for Shopify specifically, this decision happened as the team was evaluating the work required to adopt React Native's new architecture.

That gave them a concrete choice about where to spend engineering time.

The context matters.

If your application is already running well on a current React Native stack, you might be facing a very different decision by the way

so let's take a look at the results

that they achieved by moving to native now the startup time

of ios is faster down to 2.4 seconds i believe

and with react native it was 3.2 now on android it

is honestly a pretty big difference now on native using get

back on bose is 2.2 seconds versus 4.4 seconds um with react native that's uh you know, 50%.

Yeah, here's a 50% and 23% on iOS.

Now, app size, I've actually seen many teams complaining about the app size.

Again, I'm not entirely sure why Android is super huge on React Native, but I'm guessing, you know, like the React Native actual package and some of the essential,

you know, tooling to run a React Native application on Android.

But here the difference was 37%.

When native is 184 megabytes versus React Native, almost 300 megabytes.

iOS is actually not a big difference.

It's actually close one megabyte native.

Android release build time fell approximately 75%.

On iOS, release builds are taking about the same amount of time.

Let's take a look at the Android runtime performance.

So they were able to run basically the Android application at 120 frames per second, which is, you know, highly performance.

Yeah, I mean, the app looks pretty smooth.

Now there's something important to highlight here is that this comparison changes several things at once.

Language, architecture, dependencies

and parts of the product it cannot really tell us how much of the improvement came from each change

and another very important thing to highlight here is

that we are not getting a comparison with a react native application

that is actually using the new architecture

and also the article leaves the question of

which devices were measured over what period and how much the results varied

so i wouldn't treat these numbers as a general react native

benchmark now don't get me wrong i think this is a great achievement but before taking a decision like this, I would try to measure my application before expecting the same results.

Another thing that stood out to me is Shopify's warning about asking an agent to rewrite the whole application in one go.

Its strategy article says those attempts produce code it could not maintain or ship.

They are using a Helix workflow, which breaks the work into small checkpoints, and each one needs tests, a visual comparison with the running application,

two code reviewers looking for problems and a human approval.

They also separate business logic from the UI so agents can test it quickly from the command line.

And overall, they say that at the end of the day, native expertise was still essential.

You still need people that actually know how native works, iOS and Android.

So my takeaway is that AI makes working across stacks more approachable.

In fact, I've been building native macOS applications, utilities for me.

I actually tried building Inkigo, my AI tattoo application, fully on iOS using, of course, AI.

And I had a great experience.

My application looked great.

I was able to integrate authentication, reutilize some of the APIs that I already had.

Although you still need a way to describe the correct behavior, inspect the result and catch the cases that the agent missed.

Now there's another side of this that I think is easy to miss.

AI is not taking your job.

AI is actually increasing what's expected of an engineer.

So if you've been building with React Native, a move like this can mean learning enough about iOS and Android to review and maintain the native applications.

If you specialize in iOS, you might now be asked to contribute on Android too.

Why?

Because an agent can help you.

But someone still needs to check that it actually works like a human, not an agent.

And that human needs to take responsibility when it doesn't, because you cannot blame an agent.

So I can see how AI expands the job even when individual tasks get faster?

Time saved on implementation can become time spent learning another platform, reviewing more code, or taking on another part of the product.

That doesn't tell us whether Shopify's engineers are working longer hours.

My point is that the scope of the job can grow.

100

AI making something possible can quickly become a reason to expect you to do it.

101

And that's also worth noticing when we talk about AI saving developers time.

102

Now, when more of the job becomes explaining what we want the agent to do, how we give it context starts to matter.

103

So here's a small example using Voice OS.

104

You can just press on the input and press FN, hold it, start speaking, and it recognizes the application that you're working on, as you can see here at the bottom.

105

And as soon as I release the FN key, it will paste the text and I can hit send.

106

Now, you're probably already familiar with speech to text tools.

107

We have them everywhere, but VoiceOS, it's different because it can take action.

108

And let's say that you have a bunch of applications and you quickly want to open a specific app.

109

So I'm going to press Control Option, open Chrome, release, and it's going to just open it directly.

110

There we have it.

111

Now, here's a more concrete example.

112

So I'm working on this application here with Cloud.

113

Sometimes you might want to just make it bigger, immerse yourself within the experience.

114

And I don't know, let's say that we want to change this icon

115

so I can dispatch a task by pressing control option and just circle here with my mouse and say

116

can you please change this icon to be a gear for example dispatch the task with cloud code

117

and then release dispatching task to change icon to gear using cloud code there we go

118

so it's going to do it and after a moment I get the gear icon

119

so didn't have to move okay

120

so here we have the summary you can ask a follow-up literally the use case are

121

so many you can just dispatch tasks

122

while doing other things the speech to text functionality is super high quality

123

and fast so

124

if you want to be more productive make sure to check

125

out voice os the link is in the description now i was just telling you

126

that ai is actually increasing the amount of work

127

that you have to get done now right

128

but this also applies to everyone so if we actually take a deeper look at popular frameworks like Expo,

129

if we go to the landing page here in the Expo Application Services offerings,

130

you can see that they are telling us that they support Swift and Jetpack Compose and Kotlin.

131

Now, Expo are not the only ones.

132

For example, Software Mention, in their recent packages that they have released,

133

they are supporting fully natively packages for Swift and Kotlin as well, and of course React Native.

134

Other companies that provide CICD services for React Native like Bitrise have supported other platforms for a long time.

135

There's actually a platform breakdown of their services.

136

React Native 13% and as you can see just native Android and iOS is just way bigger.

137

That tells me these companies see an opportunity to serve mobile developers across stacks.

138

Offering native tools doesn't mean they are leaving React Native.

139

Another example is CodeMagic, another big company that provides CI-CD services for React Native.

140

So in 2020, they announced that they were going to provide CI-CD services for native iOS, Android, and React Native applications.

141

So native support has been part of their business for years.

142

Meanwhile, we also have Expo UI, which lets us use SwiftUI and Jetpack Compose components.

143

And Expo also introduced inline native modules in SDK 56, making it easier to place Swift and Kotlin alongside your React Native application.

144

So there is another path worth considering, keeping the shared parts of your application and use more native code where it actually helps.

145

And this is especially relevant with the AI argument

146

because AI can also help you to create amazing native modules and just bring any native integration that you need.

147

So the benefit of agents can apply to both approaches.

148

Now, on the other hand, Apple introduced the iPhone Duo on September 9, which is a foldable iPhone, it's a good example of why being close to the platform can be valuable.

149

Apple's design guidance says that apps using the standard system components

150

and already designed for resizing can add up with a little adjustment.

151

The operating system can handle parts of that transition for you.

152

And this is the real benefit of using the platform's components.

153

But the conditions matter because Apple asks developers to check layouts and custom UI.

154

So if you're using React Native, you don't have to worry about the foldable phone because as long as you stay close to the native primitives, your application is going to look nice.

155

And now for APIs that are not supported yet, You can wait for someone to create a library

156

or for Expo to upgrade Expo

157

or the React Native team to bring a new version that is going to support all these latest and greatest APIs.

158

Or you can actually contribute because it's open source.

159

But I think the useful question here is how much platform integration work your product requires

160

and who is going to own it.

161

Now, like I said at the beginning, Shopify has been a great contributor to the React Native ecosystem.

162

So now that they are moving to native, what is going to happen to their platforms?

163

So according to the announcement for React Native Skia, Shopify is going to continue sponsoring it through 2026.

164

So this is the last year.

165

And then William Candilon plans to continue the maintenance through a fork

166

and a new package name with the original repository archived after the transition.

167

Now for Flashlist, which is another popular package, Shopify will fix critical compatibility issues while discussing long-term maintenance with other companies.

168

So a successor is not named yet in this article.

169

For Restyle, Shopify plans to archive this repository, keep it working through this year, 2026, then end the maintenance.

170

A handover might be possible, but I don't know, we'll see.

171

If you depend on these packages, you can follow the migration notices in their documentation.

172

They didn't mention any specific, you know, recommended replacement yet.

173

So keep an eye on that.

174

Okay.

175

If you made it this far, thank you so much.

176

Here's my take.

177

I don't think React Native is dead.

178

And this doesn't change the value I see in learning and building with it.

179

Shopify is actually giving us a really serious example of what agents can help a team do.

180

It also gives us a reason to revisit the assumption that two native applications are automatically too expensive to maintain.

181

I understand the appeal, use the platform tools directly, get help with unfamiliar syntax, and spend more time on the experience you want to build.

182

But at the same time, React Native still gives you a shared application layer across iOS and Android.

183

And if you already know React and that shared code helps you ship and maintain your application, that's a real advantage.

184

I wouldn't dismiss it because another company made a different decision.

185

You can also keep React Native and add native code for the parts that need it.

186

If you want to learn more about deeper native integrations, make sure to check out my course, by the way.

187

Now, but there is a cost here.

188

A custom native module can mean maintaining Swift code and Kotlin code, and then the interface that connects them to your React Native application.

189

So that interface adds work, but it isn't a third party full implementation.

190

The rest of the application might still be shared.

191

Now for apps whose main value depend on the platform integration, I would give Swift and Kotlin a closer look.

192

And for a team that benefits from sharing code, React Native still makes a lot of sense.

193

Better agents can help you with both.

194

If you already have a React Native application and are curious about migrating

195

or just starting from scratch on iOS and Android version, I would measure the problem before committing to a full rewrite, even with AI.

196

And I guess that's what I want people to take from this, get comfortable enough with the platform to evaluate these choices yourself.

197

That knowledge makes you a better React Native developer too.

198

The skill I want to keep building is the ability to ship and maintain a good mobile application wherever the implementation lives.

199

If you want to get a really solid understanding of React Native, make sure to check out my course.

200

The link is in the description as well.

201

Don't forget to try out Vision OS.

202

Thanks for watching and I'll see you in the next one.

✨ अनुशंसित वीडियो

74 वाक्य

इस पाठ की शब्दावली और बोलने के सुझाव

इस वीडियो में शैडोइंग के लिए 202 वाक्य और 2748 शब्द हैं। बोला गया हिस्सा 15:11 लंबा है। वक्ता तेज़ बोलता है, लगभग 181 शब्द प्रति मिनट, इसलिए जुड़ी हुई और कमज़ोर ध्वनियाँ ज़्यादा मिलेंगी। 82% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं; बाकी शब्द अभ्यास से पहले देख लेना अच्छा रहेगा।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 कम प्रचलित शब्द, उच्चारण और अर्थ के साथ:

package /ˈpæk.ɪd͡ʒ/ (संज्ञा) — पैकेज, पैकेट. Something which is packed, a parcel, a box, an envelope.
announcement /əˈnaʊns.mənt/ (संज्ञा) — इश्तहार, घोषणा. An act of announcing, or giving notice.
implementation /ˌɪmplɪmənˈteɪʃən/ (संज्ञा) — कार्यान्वयन. The process of moving an idea from concept to reality. In business, engineering and other fields, implementation refers to the building process rather than the…
integration /ˌɪn.tɪˈɡɹeɪ.ʃən/ (संज्ञा) — एकीकरण. The act or process of making whole or entire.
developer /dɪˈvɛləpɚ/ (संज्ञा) — विकासक. A person or entity engaged in the creation or improvement of certain classes of products.
stack /stæk/ (संज्ञा) — धुआँरा. A large pile of hay, grain, straw, or the like, larger at the bottom than the top, sometimes covered with thatch.
cloud /ˈklaʊ̯d/ (संज्ञा) — मेघ, बादल. A visible mass of water droplets suspended in the air.
architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (संज्ञा) — वास्तुकला, स्थापत्य. The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.
module /ˈmɑd͡ʒul/ (संज्ञा) — मॉड्यूल. A self-contained component of a system, often interchangeable, which has a well-defined interface to the other components.
custom /ˈkʌstəm/ (संज्ञा) — प्रथा, रीति. Frequent repetition of the same behavior; way of behavior common to many; ordinary manner; habitual practice; method of doing, living or behaving.
interface /ˈɪn(t)ɚˌfeɪs/ (संज्ञा) — राब्ता, वास्ता. The point of interconnection or contact between entities.
archive /ˈɑɹˌkaɪv/ (संज्ञा) — पुरालेख. A repository or other place for storing material (such as documents and records) no longer in current use, and usually having historical value.
ecosystem /ˈikoʊˌsɪstəm/ (संज्ञा) — पारितंत्र. A system formed by an ecological community and its environment that functions as a unit.
curious /ˈkjʊɹ.i.əs/ (विशेषण) — उत्सुक, जिज्ञासु. Tending to ask questions, or to want to explore or investigate; inquisitive; (with a negative connotation) nosy, prying.
skill /skɪl/ (संज्ञा) — कुशलता, कौशल. A capacity to do something well; a technique, an ability, usually acquired or learned, as opposed to abilities that are regarded as innate.

वीडियो में आने वाली फ़्रेज़ल वर्ब

look at (क्रिया) — हेरना. To observe or watch.
look for (क्रिया) — ढूँढ़ना, ढूँढना. To seek.

ध्यान देने योग्य उच्चारण

वक्ता 35 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे don't, doesn't, I'm। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।

“th” की ध्वनियाँ: smooth /smuːð/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/
“sh” और “zh” की ध्वनियाँ: implementation /ˌɪmplɪmənˈteɪʃən/, integration /ˌɪn.tɪˈɡɹeɪ.ʃən/, transition /tɹænˈzɪʃ.ən/, migration /maɪˈɡɹeɪʃ(ə)n/, assumption /əˈsʌm(p).ʃ(ə)n/
लंबे शब्द — बलाघात सही रखें: implementation /ˌɪmplɪmənˈteɪʃən/, integration /ˌɪn.tɪˈɡɹeɪ.ʃən/, developer /dɪˈvɛləpɚ/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, ecosystem /ˈikoʊˌsɪstəm/

इस वीडियो से अभ्यास कैसे करें

पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर package, announcement, implementation जैसे शब्दों पर ध्यान दें।

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
Present perfect continuous have/has been + -ing — पहले शुरू हुआ काम जो अब भी जारी है	I've been experimenting · I've been building · you've been building
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	has contributed · has come · you've worked
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	were measured · be asked · are not supported
Relative clauses who / which + उपवाक्य — व्यक्ति या वस्तु के बारे में अतिरिक्त जानकारी	second, which is · Flashlist, which is

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: Is React Native Dead? Shopify Is Leaving - वीडियो के साथ अंग्रेजी बोलना सीखें

Why Android is Simply Better Than iOS

Graphic Designers Were Trained to Be Replaceable

I Rebuilt My Entire Website in Astro… Was It Worth It?

Why Shopify Moved Inventory Reservations from Redis to MySQL

7 Programming myths that waste your time

The (Overdue) Collapse of AI Layoffs (here's the proof)

Most devs don't understand what agents are

What they got right! iPhone Duo

The Weird Design Playbook of 6 App Outliers

Shopify CEO Tobi Lütke Shares His Secrets to Entrepreneurial Success

Business Partner B2 Unit 4.1 Alternative video

The Reusable Water Bottle Trend is DEAD