Q&A Panel

Panelists recommend keeping up with React Native regularly so annual device and operating system releases bring fewer surprises; one contributor watches commits and alerts teams to potential issues. They point to React Native’s production use and community as strengths, while describing Flutter as newer and smaller at the time. They also see value in competition and in learning from Flutter’s different rendering approach.

Panelists describe contributing through dedicated work time, personal interest, and fixing dependencies that block their own projects. They say healthy project setup makes it easier to contribute, and technical leaders can help newcomers by suggesting approachable issues and showing how quickly a first pull request may be reviewed. Filing an issue can also help others recognize and investigate a shared problem.

Panelists praise Airbnb’s detailed account of its decision to move away from React Native, while emphasizing that its conclusions depend on an organization’s needs. They identify brownfield integration and onboarding native engineers as challenges, and say Fabric was intended to address some technical issues. One panelist estimates that React developers may need a week or two to become productive with React Native, while native developers also need time to learn the JavaScript library ecosystem.

The panel says complex brownfield apps may need custom navigation and may expose existing native functionality through native modules. Expo’s Queen describes JavaScript runtime differences, such as a function available in Chrome’s V8 but not JavaScriptCore, as a source of confusion. On accessibility, panelists advocate making it part of team culture and point to Facebook Marketplace’s accessibility work and React Native props that support features such as Invert Mode.

Panelists wish for better debugging, faster issue and pull request handling, broader company participation, and a stronger community that shares experience from both JavaScript and native developers. They also cite the RFC process and Fabric as steps toward better coordination and improvements to rendering and bridge-related constraints. One panelist asks that commits not land while CI is failing, and that the person responsible fix the breakage.