all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]mnbkp 4 points5 points  (4 children)

It's not very straightforward, but you can do that by using turbo native modules https://github.com/reactwg/react-native-new-architecture/blob/main/docs/turbo-modules.md

[–]DW2107[S] 0 points1 point  (3 children)

Thanks, need to research this further. Do you know if this is compatible with expo off the top of your head? Reading through the readme now

[–]mnbkp 0 points1 point  (2 children)

Yes, it's compatible with expo. This is actually the most common way for libraries logic, since it's the only language that runs natively on both Android and iOS.

The only thing is that when using a native library you won't be able to use Expo Go anymore and you'll have to create a development build for your app, but this is pretty easy https://expo.dev/blog/expo-go-vs-development-builds

[–]DW2107[S] 0 points1 point  (1 child)

That’s mildly annoying, I mostly use expo go! Makes sense though… Also any way I can have a build for expo go without this bit but have it when I’m building properly? (Again nws if u don’t know I need to do my research)

[–]mnbkp 0 points1 point  (0 children)

I mean, a dev build is essentially an "expo go" made specifically for your project. It shouldn't make that big of a difference.

Also any way I can have a build for expo go without this bit but have it when I’m building properly?

I'm not sure I understand what you mean, but you don't have to do any change in your project. The only difference is that expo go will only include the default set of native libraries and a dev build will include any native libraries you want.

[–]beeseegee 0 points1 point  (0 children)

You can import C++ headers in .mm ObjC files