Previous article mainly analyzed React Native's initialization process from a Native perspective and summarized several optimization points for React Native container initialization based on source code. This article focuses on JavaScript and summarizes some JS-side optimization points.
Web development has a classic question: "What happens from entering a URL to page rendering in the browser?"
According to my research, this question has at least ten years of history. In the ever-changing, hard-to-learn frontend circle, this question continues to be asked because it's a very good question involving many knowledge points. When doing some performance optimization, you can start from this question, analyze performance bottlenecks, and then optimize accordingly.
But today we're not talking about Web performance optimization. Just borrowing the analysis approach of that classic question, from React Native startup to the first page render completion, combining React Native source code and the new 1.0 architecture, explore React Native's startup performance optimization path.
Article updated on 2022-08-29 with "Image" optimization content
Article updated on 2022-01-22 with "Fabric" architecture chapter
Article updated on 2021-07-01 with Redux optimization content
Talking about React Native in 2020, in the ever-changing frontend circle, might be considered quite alternative. Before writing this article, I hesitated, but then I thought that writing technical articles isn't about following trends - writing about whatever is trendy. So I decided to write this React Native performance optimization article.
The React Native performance optimizations discussed in this article haven't reached the level of modifying React Native source code, so they are highly universal and useful for most RN developers.