Repository navigation
[SET] SETBoundary - #9036
Closed
bartlomiejbloniarz wants to merge 2 commits into
Closed
[SET] SETBoundary#9036bartlomiejbloniarz wants to merge 2 commits into
bartlomiejbloniarz wants to merge 2 commits into
Conversation
##Summary: This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case ##Test Plan: Screenless example [ghstack-poisoned]
##Summary: This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case ##Test Plan: Screenless example [ghstack-poisoned]
This was referenced Mar 2, 2026
bartlomiejbloniarz
added a commit
that referenced
this pull request
Mar 11, 2026
##Summary: This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case ##Test Plan: Screenless example ghstack-source-id: 0464881 Pull Request resolved: #9036
bartlomiejbloniarz
added a commit
that referenced
this pull request
Mar 19, 2026
This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case Screenless example ghstack-source-id: 0464881 Pull Request resolved: #9036
kasperski95
pushed a commit
to kasperski95/react-native-reanimated
that referenced
this pull request
May 18, 2026
This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case Screenless example ghstack-source-id: 0464881 Pull Request resolved: software-mansion#9036
This file contains hidden or 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
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.
Stack from ghstack (oldest at bottom):
##Summary:
This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen.
Main pros of this solution:
Cons:
##Test Plan:
Screenless example