WhoBuilt

React Native at Microsoft

Sep 19, 2022· 56 min· 2.0K views·Watch on YouTube

Speaker

Lorenzo Sciandra, a Microsoft engineer working on cross-platform experiences and React Native, discusses Microsoft’s React Native work with host Lucas on Callstack’s React Native Show podcast.

How React Native took hold at Microsoft

Sciandra describes React Native’s adoption as a grassroots effort, with teams across Microsoft exploring it around the same time. Skype’s ReactXP effort helped build confidence, while teams went on to use React Native in products including Outlook, Teams, Office, Xbox Game Pass, and Windows features.

Sharing experiences across apps

React Native lets Microsoft add shared experiences to large, existing apps while keeping the surrounding apps native. Teams can share business logic and data code, while using platform-specific UI files to fit Android and iOS patterns. Sciandra says this can make features such as avatar cards more consistent across products.

Windows, macOS, and the new architecture

React Native for Windows is an out-of-tree platform that tracks Core releases closely; React Native for macOS is a fork and takes more work to keep aligned. The Windows team is also moving from UWP and System XAML to Windows App SDK, alongside its work on the new architecture. Sciandra says the timing for full readiness was uncertain.

Tools for large React Native projects

Microsoft open-sourced RNX Kit, a collection of tools that includes Metro support for symlinks and an esbuild plugin intended to reduce bundle sizes through tree shaking. Sciandra also describes React Native Test App, which helps library maintainers test against different React Native versions and the new architecture.

Open collaboration and emerging priorities

Sciandra explains that Meta owns React Native, while company partners and the wider community contribute through meetings, pull requests, and public discussions. He points to working groups focused on developer experience and bundling, and says cross-platform UI and migration to the new architecture are key areas of work.

Takeaways

  • Share business logic across apps while keeping platform-specific UI where user expectations differ.
  • An out-of-tree platform can reduce the work needed to stay aligned with React Native Core.
  • Test libraries against the new architecture early using a React Native template or Test App.
  • Public working groups and open repository discussions give company engineers ways to coordinate ecosystem improvements.
  • Large organizations can use React Native to add shared features to existing native apps, but need CI and rollout practices suited to broad impact.

Mentioned in this talk

Search inside this talk

What was claimed 18

Show all 18 facts

Related talks

React Native at Microsoft, Lorenzo Sciandra · WhoBuilt