We should hopefully be able to open source a cleaned up version of the solution that Jordan alluded to, but we have a long list of components we&#x27;d like to work on, and only a finite in-house development resource.<p>I think it&#x27;s important to understand that React Native is not an attempt to replicate the entire iOS native framework - it&#x27;s a set of UI components that aim to provide a better developer experience for the common app development challenges we face at FB, combined with a framework for building new components.<p>When we encounter an uncommon challenge (i.e. something that we haven&#x27;t already had to solve and build a reusable JS component for), we simply drop down to the layer underneath and create a new native component.<p>That&#x27;s why I struggle to understand the argument that &quot;React Native doesn&#x27;t do this one thing I need, so I can&#x27;t use it&quot; - we put a lot of thought into the plugin architecture of RN, and making native plugins is trivial for anyone familiar with iOS or Android development.<p>If there is something you already know how to do natively, you can leverage that knowledge to build an RN plugin and then get the best of both worlds. If you don&#x27;t already know how to do it natively, there&#x27;s a good chance that someone else already made a plugin that will do what you want.