Interested as well. I’ve heard a number of tech companies use react native on iOS targets which allows for easy reuse of components developed for web UI, and any mobile... certainly where I’d lean given the choice based on current information.

There was an engineering blog post from discord a number of months ago discussing their use of react native bottlenecking iOS app performance, and they ended up converting some key react data structures to native iOS constructs within the react native app and crushed those bottlenecks. My takeaway was that developer ease and reusability should be prioritized until you hit a performance wall at scale such as discord did, at which point you’ll have the money to pay other engineers to optimize the important parts of you don’t have the time or know-how ;)

For a more balanced measure of Discord's performance, try using it on a five-year old iPhone.

AFAIK that was the device subset they were optimizing for, I have an iPhone SE lying around so I’ll try it out.

React Native will get you to an MVP way faster than native/SwiftUI development. However there is the massive risk that you'll find yourself shackled to React Native if you want to grow the capabilities of your app to beyond what React Native can accommodate. React Native make development faster, but traditional native development is the safer option in the long term.

The advice I give roughly to clients is to go native if your business heavily depends on mobile. Otherwise React Native is pretty viable, especially for small teams of generalists. In terms of SwiftUI, most businesses aren’t building entire apps in it yet.

i've never used react native but regularly use react for the web and find swift/swiftui development to be faster and less complicated overall