Moyes describes React Native as a way to build experiences for Microsoft products across mobile and desktop. He connects that approach to React Native’s vision for iOS, Android, desktop, web, VR, and native platforms, and says Microsoft is investing in iOS, Android, Windows, and macOS.
React Native at Scale: How Microsoft is betting big on React Native to target BILLIONS of users
Speakers
Stephen Moyes, a program manager on Microsoft’s React Native team, presents with software engineer Shivan and Windows contributor Slobo at React Native EU about how Microsoft uses React Native across mobile and desktop.
Moyes says the Windows and macOS teams aim to keep desktop React Native capable and current with React Native core, including Hermes by default and the new architecture. Windows rebases had taken less than a week in recent releases; he notes macOS still had work to do, with version 0.68 released on July 7.
Slobo demonstrates the Microsoft Account page in Windows 11 Settings, built with React Native inside an otherwise native C++ and XAML app. The team can load a development bundle, change a feature flag, and see the page update with payment method details. Moyes points to Windows-specific modules that expose native SDK and presentation APIs.
Shivan describes React Native experiences in Word, Excel, PowerPoint, and Office apps, including the Office mobile app’s Feed tab, which shipped recently and serves millions of users on iOS and Android. Microsoft moved some mobile features from V8 to Hermes and uses a shared JavaScript instance for long-running features, while creating other instances on demand. Shivan says these choices reduced runtime memory and bundle size.
Shivan says Microsoft is also working on developer tooling and a smoother experience for React Native developers. He recommends Adam Foxman’s talk on changing React Native from within, while Moyes points viewers to Microsoft’s React Native talks and resources.
Takeaways
- Choose a JavaScript engine and hosting model based on each feature’s startup and resource needs.
- A brownfield React Native screen can fit into a native app while preserving platform look and feel.
- Keep desktop implementations aligned with core releases to reduce the lag in adopting platform improvements.
- Expose native platform APIs through modules when an experience needs capabilities beyond shared UI.
- Investing in developer tooling can support both internal products and the wider ecosystem.
Mentioned in this talk
Search inside this talk
What was claimed 12
- uses
Microsoft uses React Nativein brownfield apps“how Microsoft is using React Native at scale”
YouTube Verified14 sources· Talk
- role atStephen Moyes is senior product manager at
Microsoft“I'm a program manager on the React Native team at Microsoft.”
YouTube Verified3 sources· Talk
- role at
“I'm a software engineer working on React Native for mobile.”
YouTube Unverified1 source· Talk
- integrates with
React Native for Windows integrates with Windows 11“when your React Native for Windows app runs on a Windows 11 machine”
YouTube Unverified1 source· Talk
- useshundreds of apps in the Microsoft Store use it
“The Settings team is using React Native”
YouTube Verified6 sources· Talk
- featureWindows Settings: The Accounts page is implemented with React Native; the rest of the app is native C++ XAML.
“The Windows Settings app uses React Native on the Accounts page; the rest of the app is a native C++ XAML app.”
YouTube Unverified1 source· Talk
- uses
“The Windows Settings app uses React Native on the Accounts page”
YouTube Unverified1 source· Talk
- featureOffice mobile: Available on Android and iOS; opens and edits Word, Excel, and PowerPoint documents.
“It allows you to open and edit Word, Excel, and PowerPoint documents, all within the same app.”
YouTube Unverified1 source· Talk








