Xbox https://www.windowscentral.com/xbox-app-pc-gets-speed-boost-ditching-electron-react-native-uwp FB (Meta) Messenger Desktop Keep your eyes out for ReactConf on Dec 8th: https://conf.reactjs.org/ https://reactnative.dev/blog/2021/08/26/many-platform-vision#expanding-to-new-platforms firstname.lastname@example.org - @kelset 15/37
a big overhead: We need to balance doing what we need with what happens in RN core This makes it hard to have feature parity across the various platforms (see macos) Despite collaborating with FB directly, the feedback loop can still be improved We have weekly syncs to address main challenges, but FB’s approach to OSS means that there’s a lot of unknowns always OSS is hard! And when you are Microsoft, the barrier is even higher (security, tooling, practices, etc.) email@example.com - @kelset 16/37
Tooling Separating the dev from the toolchain Keeping dependencies aligned firstname.lastname@example.org - @kelset 19/37 Am I using the right OSS libs? Updating RN – when and by who? What if I target multiple RN versions?
understand the dependencies in a package.json and can modify it, based on a series of curated profiles. 7 versions of RN supported, over 40 libraries curated It can even fix misconfigured package.json – the developer simply defines a local dep-check configuration, and the tool will take care of declaring the right packages, at the right version, in the right section. if you want to learn more: aka.ms/dep-check email@example.com - @kelset 23/37
involved in the RN release process We are helping improving the testing and infra pipelines In the future: Potentially, an LTS More structure and clarity around the process itself firstname.lastname@example.org - @kelset 30/37
RN, that is reflected by a huge involvement in Open Source: • RN Windows & macOS • Releases • Hermes • We are constantly trying to push the boundaries: • Bundle group • Rnx-kit • <insert secret project #1212982374189723> email@example.com - @kelset 33/37