[lrichardson]

> the AirBnB team even stopped using it seriously

This just isn't true. Airbnb is actively using React Native a lot and has not "stopped using it seriously". I'm not sure where you got this impression. Some people responding to this are mentioning the transition of the potential native-navigation library to react-community. This is a library that we never actually used in production, though the plan was to move off of our internal library to this one shortly after open sourcing it. Priorities shifted internally (to other, more pressing react-native related things that aren't OSS), and we have not yet been able to do that. Since the community really wanted to work on the library despite us not actively maintaining it, transitioning it to react-community seemed like a better thing to do than further fragment the community by having people fork it. I'm still hopeful that we will be able to migrate to it in the future.

Source: I am the tech lead of React Native infrastructure at Airbnb and the primary author of native-navigation.

[TeeWEE]

Thanks for your reply @lrichardson. I got the impression that ReactNative was having a hard-time within AirBnB lately due to a lukewarm response from Native Developers. (You mentioned this in an interview). Sorry for my mis-interpretation.

Where does AirBnB actually use ReactNative, and where is it purely native? I was in the understanding the move to ReactNative was not going "the way you preferred".

I can imagine there are some roadblocks using it everywhere. Or some hesitation from Native Developers.

For me also: Using JavaScript as a language run inside a interpreter inside my app doesn't seem like a smart move. Also native like navigation, activity lifecycle, animation etc are probably hard to get right with React Native.