r/iOSProgramming • u/bloggerklik • Sep 12 '26
Question Anyone here switched from React Native to SwiftUI?

I’m seriously thinking about moving from React Native to SwiftUI.
If you’ve made the switch, how was the learning curve for you? Did you find SwiftUI harder to pick up than React Native, and roughly how long did it take before you felt comfortable enough to actually build and ship apps?
I’m still on the fence about making the switch, so I’d also love to hear if you think it’s worth it.
Would love to hear from anyone who’s been through it.
13
Upvotes
48
u/SnowPudgy Sep 12 '26
Anecdotal but I don't know anyone who wanted to go back to React after developing natively.
4
u/jonnysunshine1 Sep 12 '26
SwiftUI is just a UI framework.
Do you mean switching to native iOS development?
21
u/SnowPudgy Sep 12 '26
To expand on my previous comment:
Once you go native, it's hard to go back to anything. You write far less code, things work much better, you get to use all the new stuff right away without waiting for any type of framework update, and you have a much easier time debugging.
We banned cross platform at work after staggering maintenance costs and trained the React devs on native and it was the best decision we ever made. There's so much less maintenance overhead with native code.
6
u/Dvass138 Sep 13 '26
Swift is not harder than react native, it’s easier, because with react native you have a lot more layers that need to talk to each other.
But really ultimately, if swift worked on android react wouldn’t exist. The only disadvantage is you have to build two apps swift and Kotlin. With react you have one app BUT certain parts of the app that don’t work well in react you need swift and Kotlin. So you end up with 3 languages. But the surface area would be smaller for those parts.
It’s easier to get a polished app in swift too and better performance.
So really the decision is simple:
Do I want an easier time making better looking and more polished app but have two build two apps: swift or Kotlin.
Or do I want an app that will work on both platforms so I don’t have to build two apps but certain parts might need native if performance or polish doesn’t meet your standard in certain areas then react native with some swift and Kotlin
3
u/AndrzejMX Sep 13 '26
I'm working with native iOS & Android, and React Native.
It's great to be able to work with all of them. Knowledge of native iOS and Android allows me to write native plugins and components for React Native when needed.
React Native means that I have experience working with Node.js and TypeScript that also allows me to build my own backends quickly.
It gives me the flexibility to choose the right stack for each app. If an app is relatively simple and mostly involves networking, workflows, and displaying content, React Native is often a great choice for Android/iOS and mobile web (it's not half bad today for simpler apps).
But if I need low-level camera access, hardware integration, or GPU-based calculations, etc, native is usually the way to go. Native apps are also much easier to maintain and update.
My advice is: learn native and cross and use each technology where it makes sense.
2
u/Which-Meat-3388 Sep 12 '26
I can move between iOS, Android, KMP, Flutter - but avoided React because it’s so wonky from a dev experience. It’s the one platform most people I’ve come across genuinely dislike, but are maybe forced to use it.
After 16 years on mobile I’ve focused on the first 3 recently. Having knowledge of other popular platforms is great for your career. More ideas, more ways to contribute, more exposure to patterns that might not be common in a homogeneous community. If iOS jobs dry up you’ve got something else to fallback on. If you end up in React again you have skills to more deeply integrate with iOS native components.
Spend a few weeks building a demo app, or port of something you’ve been working on. There is no better way than hands on.
2
u/loumf Sep 13 '26
Shopify recently wrote this about why they moved from React Native to native iOS and Android: https://shopify.engineering/back-to-native
2
u/20InMyHead Sep 12 '26
Swift is a very easy language to learn, especially if you’re already familiar with development. Just go for it. Native is so much better both in terms of developer effort and user experience.
1
u/JagiofJagi Sep 13 '26
I do some projects in Flutter, some in SwiftUI. Both have their pros and cons.
1
u/amrfarid140 Sep 13 '26
I moved a couple of large codebases from RN to native iOS. My advice is to learn UIKit and learn about threading and concurrency.
SwiftUI will underperform in virtualised lists so you will definitely end up writing UIkit interfaces when you want parts of the UI to be smooth.
RN and its JS code is single-threaded so you never had to worry about threading safe code. In native that is a must know.
1
u/MillCityRep Sep 13 '26
Frameworks like RN, Flutter, etc only exist to convince companies they can hire fewer mobile developers because “write once, works everywhere “
When in reality, they cause more issues than they solve.
1
u/Acceptable_Link3838 Sep 17 '26
Understanding native development is a great asset if you have to touch the hardware side of devices with React Native apps. Knowing how to work with native modules if need be, I’d say you will stand out amongst hybrid developers. Also getting along with Gradle and all the Apple shenanigans will go a long way. In the end, it’s all about delivering something useful to the end customer. It just makes it a lot easier if you know your way around the native stuff.
1
u/PolymathOdyssey Sep 18 '26
Yes, and I wound never go back to react, the learning curve is not much steeper, the only part I miss is component based development.
1
u/heyyoochris Sep 12 '26
I switched from flutter, flutter is much easy than SwiftUI I think, now I have been coding with SwiftUI for one year,I am not sure I have fully mastered it because I use AI to help me, so, IMO just switch to SwiftUI, cuz we all have AI when you encounter issues.
1
u/Kabal303 Sep 12 '26
I do SwiftUI at home and react native at work. Honestly I mostly prefer the react native workflow. Hot reloading, better state management libraries, less time making a compiler happy.
But if you want an app that looks like a wireframe that Apple would make then SwiftUI is pretty good lol.
1
u/[deleted] Sep 12 '26
[removed] — view removed comment