Tempted to Abandon React Native for Native Android
To summarize this article: The author really enjoyed using React Native up until he hit some performance issues related to loading large images on certain versions of Android.<p>He doesn&#x27;t go into what specifically the performance issues were, any techniques he used to profile his app, what third party libraries he tired or anything.<p>Performance issues happen all the time with native apps that don&#x27;t use React Native. Optimizing is a core part of what a software engineer does. Giving up on weeks of learning without a good reason seems like a poor choice to me.<p>As it so happen&#x27;s I have been working with a colleague of mine who just fixed a React Native performance issue relating to images on Android on older devices. The author might want to check out the following article:<p><a href="https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;docs&#x2F;performance.html#moving-a-view-on-the-screen-scrolling-translating-rotating-drops-ui-thread-fps" rel="nofollow">https:&#x2F;&#x2F;facebook.github.io&#x2F;react-native&#x2F;docs&#x2F;performance.htm...</a><p>Our particular issue was solved by the following:<p>&quot;This is especially true when you have text with a transparent background positioned on top of an image, or any other situation where alpha compositing would be required to re-draw the view on each frame. You will find that enabling shouldRasterizeIOS or renderToHardwareTextureAndroid can help with this significantly.&quot;<p>Apart from the above, this article is pretty shallow, which is sad because I would love to read a good article on React Native&#x27;s performance. Perhaps I will write one if people are interested.