Core Contributor Summit 2025 Highlights

Tibo recalls an early 2017 gathering in London where contributors drafted the first autolinking design. In-person discussion helps Meta, Microsoft, and community developers compare different ways of using React Native and surface issues that may be less visible through GitHub discussions alone.

Jay describes a session about making React Native for macOS and Windows easier to adopt. He says the apps he built felt fast, but the desktop ecosystem has rough edges and limited library investment. The group identified a chicken-and-egg problem: more use could encourage libraries to support desktop, while better library support could attract users.

The contributors discuss React Native DevTools, where a summit conversation helped clarify Meta’s scope and roadmap after community developers had built a tool using internal hooks. Expo’s network inspector is another example of the community filling a gap while Meta develops a more stable option. They say sharing plans helps contributors coordinate work and avoid building against shifting assumptions.

The panel says the 1.0 label matters less than the changes behind it. They do not want it to be merely a marketing milestone; they want it to signal meaningful stability and a period of continued 1.x releases. The summit also covered developer experience, Swift support, and how projects such as Nitro Modules relate to React Native core.

Tibo says contributors can build toward summit participation by maintaining a library, working on React Native projects, attending events, and discussing community needs. Jay suggests identifying project pain points and open sourcing solutions, while the host recommends reading repository issues and RFCs to understand existing problems and direction.