[tphan]

I've used React Native for a client and, whilst it was super clunky, I still enjoyed being able to write React to deploy to mobile. With React Native for Web, you can technical write code that writes to a bunch of different platforms, a big selling point for businesses.

[yesimahuman]

Check out Ionic which now fully supports React and will give you a similar benefit but without the need to use RNW or have different code for each platform. Also Ionic’s components are much more robust and widely used than RNW.

[crazypython]

I agree that Ionic's components are easier to work with and less of a hassle. However, React Native components let you talk directly to native, even using native components from the native platform's ecosystem in your code. It's a tradeoff developers have to make.

https://github.com/wix/react-native-navigation is beautiful, it uses iOS' own navigation APIs, but it's a pain.

[yesimahuman]

That’s fair! One other option is to do both: use Capacitor and embed it inside native navigation controls (i.e. a native shell), then use Ionic React for screens, etc.

One other aspect is that Ionic React uses react-dom so it will be a pretty normal react dev experience compared to RN which isn’t 1-1 (CSS being an example).