Prepare for soft-launch of new architecture #988
Merged
+149
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TatianaKapos
commented
Nov 5, 2024
chrisglein
reviewed
Nov 5, 2024
chrisglein
reviewed
Nov 5, 2024
chrisglein
reviewed
Nov 5, 2024
chrisglein
reviewed
Nov 5, 2024
stmoy
reviewed
Nov 7, 2024
docs/NewArch.md
Outdated
|
|
||
| On Windows, the implementation of the previous "Paper" rendering architecture was based on UWP and WinUI/XAML. To meet the requirements of the new "Fabric" rendering architecture the Windows implementation now uses a direct WinAppSDK Scene Graph approach that can also host WinUI/XAML islands as needed. This evolution aims to unify rendering logic cross-platform in C++, aligning more closely with WinAppSDK and WinUI3 that favor Win32 applications. This means that apps built with the new architecture will default to Win32 rather than UWP, a change made to enhance compatibility with Windows’ latest frameworks. | ||
|
|
||
| For developers using UWP with RNW, **UWP Paper applications remain fully supported**—there are no immediate plans to remove support. However, **UWP and Fabric together are currently not supported**. We will provide clear migration guidance for UWP Paper apps once Fabric support is fully established. At this stage, Fabric on Windows is best suited for early adopters comfortable with a work-in-progress experience, and the documentation may not yet be as comprehensive. For those willing to dive in, the new architecture offers a glimpse into the future of React Native Windows development. |
There was a problem hiding this comment.
Suggested change
| For developers using UWP with RNW, **UWP Paper applications remain fully supported**—there are no immediate plans to remove support. However, **UWP and Fabric together are currently not supported**. We will provide clear migration guidance for UWP Paper apps once Fabric support is fully established. At this stage, Fabric on Windows is best suited for early adopters comfortable with a work-in-progress experience, and the documentation may not yet be as comprehensive. For those willing to dive in, the new architecture offers a glimpse into the future of React Native Windows development. | |
| For developers using RNW based on UWP, **UWP Paper applications remain fully supported** and there are no immediate plans to remove support. However, **UWP and Fabric together are currently not supported**. We will provide clear migration guidance for UWP Paper apps once Fabric support is fully established. At this stage, Fabric on Windows is best suited for early adopters comfortable with a work-in-progress experience, and the documentation may not yet be as comprehensive. For those willing to dive in, the new architecture offers a glimpse into the future of React Native Windows development. |
For those willing to dive in, the new architecture offers a glimpse into the future of React Native Windows development.
This is a good opportunity to include a list of things that work vs. things that don't. I covered this at React Universe, we can recycle some content (or create a new page that we keep up to date).
There was a problem hiding this comment.
Do you have link to your talk in React Universe? I can go ahead and add some of the content to this page!
docs/NewArch.md
Outdated
|
|
||
| ## Components | ||
|
|
||
| The new architecture introduces significant updates. By moving away from XAML, we gain the flexibility to incorporate components that weren’t previously available and reduce technical debt from legacy XAML components. Below is a list of components we plan to support in the new architecture, as well as those we are looking to deprecate. For developers currently using Flyout or Popup, we hope they’ll find Modal a suitable alternative. |
There was a problem hiding this comment.
Should we have a guide that helps with the migration from Flyout/Popup to Modal? Is it truly a 1:1 drop-in replacement?
There was a problem hiding this comment.
I don't think we are in a spot where we have a migration plan for Flyout/Popup, there's still a lot of properties/events missing on Modal and discussions on windows-specific properties that should be included. It won't be a 1:1 replacement though as the properties are different.
Will add that for future-work though!
Co-authored-by: Steven Moyes <[email protected]>
chrisglein
reviewed
Nov 8, 2024
chrisglein
reviewed
Nov 8, 2024
chrisglein
reviewed
Nov 8, 2024
chrisglein
approved these changes
Nov 8, 2024
Co-authored-by: Chris Glein <[email protected]>
Closed
jonthysell
reviewed
Nov 8, 2024
docs/NewArch.md
Outdated
There was a problem hiding this comment.
Can you rename to new-architecture.md to align with other file naming?
docs/getting-started.md
Outdated
| @@ -9,6 +9,8 @@ Make sure you have installed all of the [development dependencies](rnw-dependenc | |||
|
|
|||
| For information around how to set up React Native, see the [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started). | |||
|
|
|||
| > **Interested in exploring the new architecture?** We are "soft-launching" our implementation of the new architecture. If you’d like to be an early adopter, check out the instructions in the [New Architecture Guide](NewArch.md) and discover new templates available in [init-windows-cli](init-windows-cli.md#templates). | |||
There was a problem hiding this comment.
I think "soft-launch" is purely internal, and perhaps "preview" is better? Checking with others.
Suggested change
| > **Interested in exploring the new architecture?** We are "soft-launching" our implementation of the new architecture. If you’d like to be an early adopter, check out the instructions in the [New Architecture Guide](NewArch.md) and discover new templates available in [init-windows-cli](init-windows-cli.md#templates). | |
| > **Interested in migrating to [React Native's New Architecture](https://reactnative.dev/architecture/landing-page)?** New Architecture support in React Native for Windows is now available to preview in 0.76. Note there are several key changes, so if you’d like to be an early adopter, check out the information in the [New Architecture Guide](new-architecture.md). |
There was a problem hiding this comment.
changed to preview in documentation!
Co-authored-by: Jon Thysell <[email protected]>
|
@chrisglein @stmoy Jon added some more content (particularly the FAQ) if you wanted to take a look! |
chrisglein
approved these changes
Nov 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Closes #981 and #980
Why
We are soft-launching the new arch in 0.76, this aims to start the documentation for this change! All feedback and contributions is welcomed if not encouraged :)
Content mostly taken from
Microsoft Reviewers: Open in CodeFlow