react-native-tvos VS react-native-hashing

Apple TV is a bit more complicated these days with React Native than Android TV. The most popular way is to use the fork of React Native called react-native-tvOS (https://github.com/react-native-tvos/react-native-tvos ). It’s a fork of react-native, so you’ll always be ~0-1 versions behind react native core for your project. This ain’t bad though, and is essentially the same version lagging “cost” as using Expo. I’d recommend this approach if you need Apple TV and Android TV platforms.

Are you using https://github.com/react-native-tvos/react-native-tvos ?

I went this route when the new arch was an up and coming thing, spent a lot of time learning how to do cpp stuff and i made this: https://github.com/TheRogue76/react-native-hashing From my experience, unless you are doing something that is computationally extremely expensive, or doing something that needs access to the Yoga and the whole of the rendering pipeline, you are better off doing it in Kotlin and Swift. Cpp is not a pleasant or modern language (from the generics to the null handling to enums, my experience was terrible). We are mobile developers, so there will never be a time in your career when Swift or Kotlin are not useful. For my part, I won’t touch cpp ever again unless i have to. But it’s up to you