WhoBuilt

React Native @ Microsoft

Oct 9, 2019· 22 min· 2.9K views·Watch on YouTube

Speakers

Micah Lewis, a Microsoft PM focused on Windows UI, and EJ Layne, a Microsoft PM focused on Office experiences, discuss Microsoft’s use of React Native at React Native EU 2019, hosted by Callstack.

Why Microsoft adopted React Native

Microsoft teams use React and React Native across products including Word, PowerPoint, and Excel. Layne says the framework helps teams share business logic and UI while building experiences that still feel suited to each platform. Office’s long history and varied platforms make sharing more code especially useful.

Office features built with shared UI

Layne describes a shared people card experience and Excel cards for stock and geographic data. The cards work across multiple platforms. Fast Refresh also lets developers see UI changes within seconds, shortening the feedback loop compared with waiting minutes.

React Native for Windows and Mac

Lewis distinguishes the existing C# implementation of React Native for Windows from a newer version built on Facebook’s shared C++ core. The team was targeting React Native 6 support and working on APIs for desktop input, gamepads, accessibility, theming, and animations. Microsoft was also exploring React Native for Mac.

Controls, tooling, and open source

Layne describes extending Microsoft’s UI Fabric controls to native platforms, with accessible defaults and styling based on Fluent Design. Lewis covers Windows debugging support in VS Code and App Center services, including preview versions of Auth and Data. The speakers invite community feedback and contributions to their open source work.

Takeaways

  • Share UI code across platforms while tailoring the finished experience to each platform.
  • Use fast refresh to shorten the time between a UI change and seeing its effect.
  • When adopting React Native for a new platform, plan for platform APIs, accessibility, theming, performance, and debugging.
  • Build reusable controls with accessible defaults, while leaving room for app specific styling.
  • Open source platform work can support internal product needs and give other teams shared improvements.

Mentioned in this talk

Search inside this talk

What was claimed 15

Related talks