Earlier quoted context omitted.
You just install it on your phone and use the app. Maintainability concerns are entirely overblown by people who don't use agentic AI to develop large mobile apps, but anyway give their opinion as if they had that experience. I put in a few hundred hours, and I reached the same conclusion as Shopify. With reviews from other models and then a manual QA pass the result is fully usable.
> You just install it on your phone and use the app. Some people on the cybersecurity side are starting to cry....
Shopify is moving from React Native back to Swift and Kotlin
251–260 of 962 posts
Re: Shopify is moving from React Native back to Swift and Kotlin
#252Earlier quoted context omitted.
> I think people in the tech community have probably also noticed that it's rather popular to have an absolute opinion on the goodness or badness of these tools. For a while it seemed that having deeply held, nuance-free opinions about technologies was a sign of being wise and experienced. The slightly lighter version of this was having near-absolute convictions but leaving a tiny exception for extreme cases to try t…
Strong opinions considered harmful
I try as hard as I can to have strong opinions, loosely held
Re: Shopify is moving from React Native back to Swift and Kotlin
#253Re: Shopify is moving from React Native back to Swift and Kotlin
#254Models have gotten a lot better at generating native iOS apps. The main appeal of RN was being able to leverage your web devs for mobile dev. that's what I did at my last company. And it's fine for a startup, but eventually you want dedicated native engineers bc each platform really deserves its own technical masters who can optimize for it. But now that all code is generated, there's little upside to having an RN ap…
[0] I always thought the best answer was something like KMM to do all the backend comms and local data model in a shared way, and then a bespoke UI building on what that shared code exposed.
Re: Shopify is moving from React Native back to Swift and Kotlin
#255Earlier quoted context omitted.
You just install it on your phone and use the app. Maintainability concerns are entirely overblown by people who don't use agentic AI to develop large mobile apps, but anyway give their opinion as if they had that experience. I put in a few hundred hours, and I reached the same conclusion as Shopify. With reviews from other models and then a manual QA pass the result is fully usable.
> You just install it on your phone and use the app. Some people on the cybersecurity side are starting to cry....
Re: Shopify is moving from React Native back to Swift and Kotlin
#256Earlier quoted context omitted.
You just install it on your phone and use the app. Maintainability concerns are entirely overblown by people who don't use agentic AI to develop large mobile apps, but anyway give their opinion as if they had that experience. I put in a few hundred hours, and I reached the same conclusion as Shopify. With reviews from other models and then a manual QA pass the result is fully usable.
> You just install it on your phone and use the app. Some people on the cybersecurity side are starting to cry....
Re: Shopify is moving from React Native back to Swift and Kotlin
#257Re: Shopify is moving from React Native back to Swift and Kotlin
#258Earlier quoted context omitted.
You just install it on your phone and use the app. Maintainability concerns are entirely overblown by people who don't use agentic AI to develop large mobile apps, but anyway give their opinion as if they had that experience. I put in a few hundred hours, and I reached the same conclusion as Shopify. With reviews from other models and then a manual QA pass the result is fully usable.
I am using Gemini as well as Opus on a somewhat small project in React Native and I can not imagine this thing being able to build the whole thing on its own without it being a dumbpster fire. Can you share some details of how you work? What models? What harness?
Re: Shopify is moving from React Native back to Swift and Kotlin
#259Earlier quoted context omitted.
The problem with tomorrow is sunk costs. There are many places I wish we had made a difference decision in the past - but we need to balance that with cost to make changes when what we have works okay.
There's also a recency bias, where you ignore how valuable some decision was in the past and ignore the fact that you maybe wouldn't even get to the place you are if "you made a different decision in the past".
Not always, but very often people in the past had good reason for what they did.
Re: Shopify is moving from React Native back to Swift and Kotlin
#260A companies with thousands of engineers should simply go native. Write once, deploy everywhere like React Native mainly benefits small teams and startups who are okay with building 90/10 solutions. At the shopify's scale, they would want to go advance for every corner of the apps and use cases, and only native allows that.
And, honestly, the cost of tracking React over time has always been higher than the cost of tracking native deployment options, which move more slowly and usually with more care than React, where breaking backward compatibility is just another Tuesday. I don't think the promise of React Native being an almost-free "native" app actually pans out in reality. I've never maintained a large React Native app, but from following some apps that are, it seems like it introduces a sizable amount of technical debt that you pay over time. So, in exchange for worse software you also get worse maintenance costs.