I work on League of Legends: Wild Rift at Riot games. I used to work on the Call of Duty Companion App at Activision Blizzard using React Native.
BEST WAY TO CONTACT ME: Twitter DM.
One time in a bar Nader Dabit told me he liked it better. Just kidding. Though that did happen.
RNN wasn't a good fit for us. A lot of apps that have a significant enough amount of native modules tend to use it. But we basically don't have any native modules. Nor do we care about features RNN offers. We felt RN was simpler, had a more reliable buy-in (meaning better maintained), & fit our upcoming use cases for deeplinks better. We liked how it worked with react-native-screens too. It has cool stuff like lazy loading too which was easy for us to take advantage of.
Thanks for response! We've lived with RNN for a while now and found it quite difficult to work with, however have enjoyed the native feel and performance.
I'll have a look into react-native-screens with react-navigation, so thanks for that tip.
I work on League of Legends: Wild Rift at Riot games. I used to work on the Call of Duty Companion App at Activision Blizzard using React Native.
BEST WAY TO CONTACT ME: Twitter DM.
Personally I can't tell any difference in terms of performance. If it's there it feels negligible enough that the pros of RN still count much more heavily in its favor. Though to be fair we did a lot of performance improvements alongside moving away from RNN so I don't have a proper comparison - I just know our performance now with RN doesn't appear to be any sort of problem.
If your application uses a lot of native modules your experience may indeed be different. That is not an area I am particularly knowledgeable about.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One time in a bar Nader Dabit told me he liked it better. Just kidding. Though that did happen.
RNN wasn't a good fit for us. A lot of apps that have a significant enough amount of native modules tend to use it. But we basically don't have any native modules. Nor do we care about features RNN offers. We felt RN was simpler, had a more reliable buy-in (meaning better maintained), & fit our upcoming use cases for deeplinks better. We liked how it worked with react-native-screens too. It has cool stuff like lazy loading too which was easy for us to take advantage of.
Thanks for response! We've lived with RNN for a while now and found it quite difficult to work with, however have enjoyed the native feel and performance.
I'll have a look into react-native-screens with react-navigation, so thanks for that tip.
Personally I can't tell any difference in terms of performance. If it's there it feels negligible enough that the pros of RN still count much more heavily in its favor. Though to be fair we did a lot of performance improvements alongside moving away from RNN so I don't have a proper comparison - I just know our performance now with RN doesn't appear to be any sort of problem.
If your application uses a lot of native modules your experience may indeed be different. That is not an area I am particularly knowledgeable about.