It looks like your company was ill prepared for the transition/ is not capable of fully transitioning as most of your mentioned "issues with RN" read like issue

It looks like your company was ill prepared for the transition/ is not capable of fully transitioning as most of your mentioned "issues with RN" read like issues rather than problems with the framework itself. > - In the end, RN code is only something like 20% of our Android app. They weren't able to just "write once" and run on both. That has nothing to do with RN, that's on your company > - Instead of having 2 teams, an iOS and Android, now we have 3 teams, iOS native, Android native, and RN. And the RN team is split between iOS and Android. All sorts of additional complexity now. Again, your company/ mgmt. We shared code between iOS and Android and had zero native module maintenance. > - We still need a fully staffed Android specific team for everything that couldn't be done in RN. which was what exactly? > - The performance difference vs. a native app is blatantly obvious. The majority of apps within the app store could've been written in RN and you wouldn't know/ notice. Discords iOS App is written in RN and I bet a huge amount of commenters here wouldn't have know without reading the article.