2 min read

Yesterday, Lorenzo Sciandra, a React Native developer shared his experience on how the React Native Community took an added ownership over the development of React Native and also enhanced collaboration with Facebook in 2018. In 2019, the community will be sharing guidelines for ensuring quality code that complies to community-agreed standards.

Here are the three channels they created for better transparency and sharing the recent happenings in React Native Community:


As the name suggests, the react-native-releases repository was created to keep everyone up-to-date about new releases of React Native in a more collaborative manner and get a clear idea of what features would be a part of a certain release. This allowed the team to follow a long-term support approach instead of the monthly release cycle, which they are using in version 0.57.x.


The discussions-and-proposals repository was aimed at providing a more open environment for discussing new features or enhancements to React Native. It provided better transparency from the Core and Facebook teams and acted as a communication channel for all the members of the community.

The team wanted to adopt an RFC (request for comments) approach instead of having all the discussion and proposals on the main repository. This repository provides a consistent and controlled path for new features to be proposed. Also, the Facebook team is using the RFC process to discuss what could be improved in React and is co-ordinating their efforts around the Lean Core project.


The team has created this new Twitter account to give users regular updates on everything going on in the React Native Community i.e. from releases to active discussions.

In addition to enhancing the collaboration in the community, the team is also aiming for creating a formal structure. For this, they are planning to enforce a set of standards for all the packages and repos. With these guidelines in place, they will be able to help each other and contribute quality code that conforms to community-agreed standards.

In his blog post,  Lorenzo also said, ”This organization can set the example for everyone in the larger developer community by enforcing a set of standards for all the packages/repos hosted in it, providing a single place for maintainers to help each other and contribute quality code that conforms to community-agreed standards.”

Read Next

JavaScript mobile frameworks comparison: React Native vs Ionic vs NativeScript

The React Native team shares their open source roadmap, React Suite hits 3.4.0

React Native 0.57 released with major improvements in accessibility APIs, WKWebView-backed implementation, and more!