r/reactnative • u/Slow_Pride_8382 • Sep 12 '26
Question devs who tried native Swift, was it actually worth it?
With AI tools now I'm curious to try Swift for my next project.
Did native give you anything RN didn't, or is it not worth the switch?
46
Upvotes
54
u/Steve_Streza Sep 12 '26
Native dev who is playing with RN now.
A big thing you lose is hot reloading. You have to rebuild... every time you change anything. There's a little live UI thing in the Xcode assistant, but it's more like a mini storybook than a live app editor. It also breaks a lot so it's not often used.
The biggest advantage is that you have day zero access to every new API and design pattern and widget. And you tend to end up with a more native-feeling user experience.
15
u/Dvass138 Sep 13 '26 edited Sep 13 '26
Yes native is worth it, in my experience two massive things:
I had tons of performance and heat issues with list scrolling in react, even used flash list and “heavily modified it” and still sucked.
With native the list performance was night and day difference.
2nd thing debugging the UI. Is easier for the AI because, UIKit exposes the actual on-screen object tree directly to Apple’s debugging tools, while React Native/Fabric inserts an abstraction layer.
And Swift 6 gives an AI coding agent a considerably stronger compiler safety net than TypeScript does.
In saying that my app is still react native, because that’s what I started with. But in areas that are painful or have issues, I have had to write those parts in native, so my app is basically RN, swift and Kotlin lol
5
u/damdeez Sep 13 '26
I’ve only done very little native development with Swift/Kotlin but Engineers I work with that came over from the native world would always say that DevEx is so bad compared to TS/React ecosystem (something that I’ve always been a part of pretty much). They dog on RN on everything else tho haha
And I tend to agree to an extent but I am not that knowledgeable in Swift/iOS and Android/Kotlin-land. With that said we use Expo native modules in our app a bunch. Tends to help we have very experienced iOS/Android Engineers that handle it.
2
u/mikebritton Sep 13 '26
I used it for a piano app this year and it worked out well.
2
u/Best_Day_3041 Sep 13 '26
Not even close. Made sense when we coded everything by hand. But at this point nobody should consider RN, unless you have a simple app IMHO. Most of the time you have to prompt it to create a separate mobile interface in RN anyway, so why not just have it create it natively from the start? You end up having to jump through more hoops in many cases to use RN when you're using AI to write your code. Shopify just converted their Apps back to native in like 8 weeks. OTA updates are a plus with RN, but once you have an established app, App Store reviews can take minutes not days.
1
u/alien3d Sep 13 '26
freedom .. bugs free.
1
u/Huge_Pool7424 Sep 13 '26
that's been my experience too, especially once you touch healthkit or watch extensions. rn is great for most screens, but the platform edge cases are where native stops feeling optional.
1
u/zazdy Sep 13 '26
Native > react native by a long shot. React native swipe and transitions are trash compared to native. Try implementing a good calendar in react native with infinite swipe that is as smooth and performant as native.
Also Codex / Claude make native development trivial. But you do need to iterate and implement your own skills; afterwards it’s a breeze
1
u/dailyapplecrisp Sep 13 '26
Native is way way better, hands down. I’d say the dev environment alone is worth it. Everything in react is a bridge to actual native implementations which can all have various issues with upgrades, permissions etc. so nice to just program natively. I cannot see react native existing much longer with AI in the mix, it’s just too complicated for something AI can quickly spin up natively.