All New Architecture apps will now be Win32-based and built on the Windows App SDK, aligning with Microsoft\u2019s latest app development recommendations. Meanwhile, Old Architecture apps will remain UWP-based, and it\u2019s still possible to create and maintain them using legacy templates.<\/p>\n
While there are no immediate plans to deprecate Old Architecture, future investments are focused on the New Architecture.<\/p>\n
Have more questions? Check out the New Architecture FAQ<\/a>!<\/p>\n Let’s dive into creating a new architecture application. These steps are tailored for version 0.77, but you can visit our Getting Started page<\/a> for guidance on other versions. You’ll find the steps below are almost exactly the same as creating an old architecture application – with the only change being is specifying a new architecture template in step 4.<\/p>\n Congrats, you\u2019ve just created an RNW app using the new architecture! \ud83c\udf89<\/p>\n The new architecture has been built from day one using the precompiled Microsoft.ReactNative NuGet packages, enabling significantly faster build times. The preview release of the new architecture has brand new templates that take advantage of the precompiled NuGet packages.<\/p>\n We now offer two new templates:<\/p>\n cpp-app: For React Native Windows Applications (New Architecture, C++, Win32, Hermes)\ncpp-lib: For React Native Windows Turbo Modules (New Architecture, C++)<\/p>\n These templates can be easily used with the react-native init-windows CLI command: In version 0.77, we further refined these templates, updating CLI commands like Check out the full list of supported templates here<\/a>.<\/p>\n The old UWP-based implementation suffered from frustrating limitations in the underlying Windows platform including lack of Good news! Those limitations are a thing of the past! With the New Architecture, we\u2019re thrilled to introduce the new (for RNW)<\/em> Modal component<\/a> in 0.77. We hope customers using View Source Code<\/em><\/a><\/p>\n As a brand-new component, Modal is still a work in progress, and we\u2019re actively enhancing its functionality. Currently, Modal supports the The 0.77 release of the new architecture brings exciting updates to explore! You can now enable custom controls to implement the While we\u2019re focused on rolling out new features for the new architecture, we recognize the need to support the many folks that are still on the old architecture. Although no new features are being added to the old architecture, we recently made several key reliability improvements including resolving Flyout\/Alert crashes on Windows 10, optimizing the Text component, ensuring consistent button sizes when pressed, and more. Additionally, we’ve added support for TurboModule event emitters, enhanced new project namespace\/cleanup, and increased the method parameter limit from 7 to 10.<\/p>\n For a deeper dive into these reliability improvements, check out our 0.77 release notes<\/a> and our 0.76 release notes<\/a>!<\/p>\n If you\u2019re interested in getting started with React Native for Windows, check out our website at aka.ms\/reactnative<\/a>.<\/p>\n\ud83d\udee0\ufe0f Steps on creating on New Architecture application on 0.77<\/h2>\n
\n
npx --yes @react-native-community\/cli@latest init <projectName> --version \"latest\"<\/code><\/p>\n\n
cd <projectName><\/code><\/p>\n\n
yarn add react-native-windows@^0.77.0<\/code><\/p>\n\n
yarn react-native init-windows --template cpp-app --overwrite<\/code><\/p>\n\n
npx react-native run-windows<\/code><\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/react-native\/wp-content\/uploads\/sites\/76\/2025\/01\/new-fabric-app.gif\")
<\/p>\n\ud83d\udea7 New Architecture Changes in 0.76 and 0.77<\/h2>\n
\ud83d\udcd1 New Templates<\/h3>\n
yarn react-native init-windows --template <TemplateName> --overwrite<\/code><\/p>\nautolink-windows<\/code> and init-windows<\/code> to adapt their behavior based on the template used to create the application.<\/p>\n\ud83e\ude9f Introducing Modal<\/h3>\n
Modal<\/code> support. Although Windows developers could use Windows-specific components like Flyout<\/code> and Popup<\/code>, this created extra work for those transitioning iOS or Android apps, as they needed to rework their code specifically for Windows.<\/p>\nFlyout<\/code> and Popup<\/code> will find it easy to switch over to Modal<\/code> and enjoy a more seamless cross-platform experience.<\/p>\n![\"\"](\"https:\/\/devblogs.microsoft.com\/react-native\/wp-content\/uploads\/sites\/76\/2025\/01\/modal-playground.gif\")
<\/p>\nvisible<\/code>, onShow<\/code>, and onDismiss<\/code> properties\/events. We’re hard at work adding support for transparent<\/code>, backdropColor<\/code>, and exciting Windows-specific features like setting a title bar and moving the modal outside of the application boundaries. Stay tuned in our New Architecture tracking issue<\/a> for more updates!<\/p>\n\ud83d\udc69\u200d\ud83d\udcbb New Features for Accessibility, TextInput, and Custom Components<\/h3>\n
expand<\/code>\/collapse<\/code> action, support a wider range of accessibility features, and take advantage of new properties like autocapitalize<\/code> and cursor<\/code> in TextInput. Check out all the details in our release notes for 0.77<\/a> under the section New Architecture-Specific Changes<\/code>.<\/p>\n\ud83d\udee1\ufe0f Commitment to Reliability in the Old Architecture<\/h2>\n
\n