Your use case is the situation where React Native thrives. You get code sharing across platforms and a leg up with election and stuff like that. I view Airbnb'

Your use case is the situation where React Native thrives. You get code sharing across platforms and a leg up with election and stuff like that. I view Airbnb's failure with it more of a (justified) lack of will. They already had native apps rolled out and were tacking things on with React Native. I feel it's best to invest in the largess of the codebase being in React Native and digging into native apis when needed "A common misconception is that when Airbnb decided to use React Native, that they made a complete switch. This is not only not true, but to this day the React Native code represents only 15-20% of the codebase and developer resources. It was never a majority platform for the company, and part of that was the immense upfront cost to enable even the first set of components for the mobile platforms. Even though React Native is a framework and vastly simplifies mobile development, it is not trivial to get up and running, particularly if you have an existing codebase. Expect to invest a substantial amount of time and energy to integrating React Native into your existing mobile codebase" Airbnb decided it wasn't a priority to finish the job. That's a fine choice I just don't see it as wholesale indictment of React Native as it was originally sold in that article.