Yesterday the React Native team launched an AUA(Ask us Anything) on Reddit, with the address at the bottom of this post. The first question that came to my mind when I saw this activity was, what do they think about Flutter? When I opened the event, I found that someone had already asked and received an official reply.

Questioner:

How do you think about a Flutter, how does React Native compare to a Flutter?

Official reply:

I think React Native and Flutter have completely different goals and therefore take completely different approaches to their implementation, so how you look at them depends on what you are trying to achieve. React Native, for example, prefers to preserve the features and component styles of each platform, whereas Flutter renders component styles through its own rendering engine instead of platform Native effects. Depending on what you want to do and what you want to accomplish, this should be the most important thing to consider.

Between the lines:

Did not say what is good, what is not good, very standard official reply. It seems that I have already thought of the answer, and I am sure someone will ask this question. And after reading this response, I feel like I’m saying, “Kids make choices, adults make choices!”

In addition to this unavoidable problem, there is another key issue that I think is about the future development of React Native. Of course, that question has been asked, and it’s at the top of the list.

Questioner:

React Native has been around for 4 years now, so what do you think it will look like in the next 4 years?

Official reply:

I think the future development of React Native will have two stages.

By the end of this first phase of development, I think React Native will be a framework for bringing the React syntax to any of the original platforms. We can already see how React Naitve is made easier to use and more versatile with Fabric and TurboModules. I expect React Native to support any mobile, desktop, AR/VR platform. For now, we can also see the company hoping React Native will run on devices other than Android and iOS.

Before I move on to phase 2, it’s important to understand what we’re trying to accomplish with React Native. We’re trying to bring React to Native interface development. We think React strikes a good balance between expressiveness, intuitiveness, and flexibility to provide good performance and a flexible interface.

At the end of the second phase of development, I think React Native will return to “React”, which means a lot of things, and its positioning will be more ambiguous. However, this means more aggregation and abstraction between React Native and React for Web. This could mean raising the level of abstraction to the Web level that developers are familiar with today. Interestingly, though, Twitter’s entire site is already written using React Native. Although this looks like the Holy Grail of code sharing. But it doesn’t have to be, and I believe it can deliver a high-quality experience on any platform.

Between the lines:

In the future, React Native plans to move React Native to all of its original platforms. In the second stage, React Native will gradually bridge the gap between React Native and React for web. The code is abstracted and aggregated in a direction familiar to Web developers

React Native is just an extension of React. Don’t always compare us with Flutter. We are different, OK? As far as the future goes, it won’t be out of touch with our huge React user base. This was not developed for your native developers, but for Web developers to augment their skill stack. So maybe also to avoid a direct confrontation with Flutter? After all, Google’s expertise in native development is deeper than Facebook’s.

There are more than 200 responses to React Native, and there are a lot of interesting questions that I think all developers using React Native should check out. Because there are so many contents, I will not translate them one by one.

Another point needs to be mentioned in particular. Why did React Native hold this AUA activity at this time? As they mentioned in the event details, the official RELEASE of RN0.59 is coming soon, and the official announcement is that it brings a “very exciting” update, so maybe they wanted to get some publicity for it.

If you are interested in React Native development, you can follow my official account to share the latest developments at home and abroad from time to time. Not only React Native, but also other original content about mobile development.

Address:(Asking for a ladder)

We’re the React Native team. AUA! from reactnative

Recommended reading:

  • Apk Ultimate Compression (Say something different)

  • Readhub+ has been updated to v1.8.0.

  • A macOS All-in-one Efficiency device