This React Native work is using the same "default UI framework" from Windows 8 (WinUI/WinRT, whatever you want to call it), the big thing that has shifted was W

This React Native work is using the same "default UI framework" from Windows 8 (WinUI/WinRT, whatever you want to call it), the big thing that has shifted was Windows 8 did JS bindings directly inside IE11 and "Spartan" Edge and now the preferred tool seems to React Native when working with JS (or TS). (Which in some ways is actually a regression from the Windows 8 approach because the IE11/"Spartan" Edge-backed plan supported WinRT bindings and WinUI user interfaces "progressively" in PWAs: rather than recompiling your JS for React Native with its own React Native "skin" there was a more direct path to "upgrade" a regular web-hosted app and boring "old fashioned" HTML DOM to WinRT/WinUI. Somewhat ironically, too, the WinUI name even came from these earlier Windows 8 efforts, but WinUI.js died as Microsoft decoupled WinRT bindings from IE11/"Spartan" Edge and never got a "3.0".) I think the narrative that Microsoft keeps switching their UI story is more about the confusion of the shifting bindings than actually about the stack as whole. The stack is relatively consistent over time, just things like .NET versions kept changing (and where .NET fits with respect to the application hosting model/lifecycle) and JS saw this regression from being a "first class" supported binding with a path for PWAs to it's finally back in React Native (and currently only React Native), and even is starting to feel "first class" again, if you don't mind React Native now as the only way forward.