Shared element transition #941

lintonye · 2017-04-06T18:04:20Z

Motivation

See #175, this PR is the first part: built-in support for shared element transition. The second part would be an API for custom transitions, which would come after the implementation of shared element transition becomes solid.

Here are some videos: on Android (Nexus 5X, Nougat), on iOS simulator.

Usage Example

import { Transition } from 'react-navigation';
// PhotoGrid.js
<Transition.SharedElement.Image id='image1' ... />
// PhotoDetail.js
<Transition.SharedElement.Image id='image1' ... />

If the "from" and "to" routes contain elements with matching ids, shared element transition will be played. The actual animation is a combination of cross fade and shared element transition.

Otherwise, the platform default transition (as implemented in CardStyleInterpolator) will be used.

Similar to Animated, built-in components include Transition.SharedElement.Image, Transition.SharedElement.View and Transition.SharedElement.Text. Transition.SharedElement.createComponent() can be used to create a shared-element component from another component.

Quick guide to the code

This PR includes changes in the following areas:

CardStack is slightly modified to wrap the original CardStack component with a HOC withTransition. Code related to transitions is moved to withTransition.js.
Card is modified to render to <Transition.View> instead of <Animated.View>. A couple of context fields are added to propagate route and transition information to its descendants.
src/views/Transition: This is the "meat", which includes main classes and functions that add custom transition support.
src/views/__tests__: Added some unit tests
examples/NavigationPlayground: An example app is added here. All the images are from unsplash.com which should not introduce any license issues.

Test plan

Test on both platforms with and without Transition.SharedElement items
Test share element transition using different components, including Image, View, Text and custom components
Verify that the platform default transition is used when there are no shared elements with matching ids
Perform normal user interaction to the interface, such as scrolling, and verify that the shared element transition behaves correctly
Test the performance impact on the UI after adding shared elements

Known issues

Animating fontSize of <Text> is implemented but not working yet.
The frame rate on iOS seems to be lower than on Android (Nexus 5X Nougat).

* master: Docs: Added clarification for header configuration (react-navigation#891) Fix gesturesEnabled regression (react-navigation#886) bump react-native-drawer-layout-polyfill (react-navigation#882) Fix rebase commands (react-navigation#870) Possibility to overwrite label's style if defined as string. (react-navigation#731) add example for DrawerNavigatorConfig (react-navigation#552) Workaround for screenProps in TabViewAnimated (react-navigation#862) Update Guide-Nested.md (react-navigation#813) remove ReactComponentWithPureRenderMixin (react-navigation#809)

* multi-transitions-rewrite: initTransition => bindTransition

* multi-transitions-rewrite: Add unit tests for transitions Update comments Use default transition if can't find matching one Default transition

* multi-transitions-rewrite: Restructure a bit _findTransitionContainer

* master: add jest config for react-navigation in docs (react-navigation#256) (react-navigation#331)

ericvicenti

This is exciting but it feels like a bit more complexity than is needed. For example, do we really need 'compositions' to implement the shared element functionality? Also it seems there is more indirection than needed with extra classes like TransitionItems.

Are there additional features being added here, other than shared element? I hope we can simplify it. For example, I see that there is additional logic to coordinate the CrossFade, which may be nice but I think should be done separately from the shared element implementation. I think the existing CardStack transition should work with shared elements.

Also, a bit of mechanical feedback: lets avoid using lodash and instead use language features. Also, is flow passing? I see it is overlooked in a few places

src/views/Transition/withTransition.js

+      // already registered.
+
+      const onLayout = async () => {
+        const toRouteName = that._toRoute && that._toRoute.routeName;


src/views/CardStack.js

@@ -571,6 +523,8 @@ class CardStack extends Component<DefaultProps, Props, void> {
    const SceneComponent = this.props.router.getComponentForRouteName(
      props.scene.route.routeName
    );
+    const extraProps = this.props.createExtraSceneProps &&


lintonye · 2017-04-06T20:50:50Z

@browniefed @ericvicenti Thanks for the feedback. I'll fix those flow errors and ListView in a few days.

A few things that I'd appreciate further clarification:

For example, do we really need 'compositions' to implement the shared element functionality?

I see that there is additional logic to coordinate the CrossFade

Composition with CrossFade is needed because simply doing shared element transition and then immediately switching to the new scene doesn't look good IMHO. I'll upload a video for your comparison later.

This PR is based on my previous work on custom transitions. Yes it contains extra features, i.e. the support for custom transitions. This is the easiest way that I can see compared to trying to extract shared-element only code. After all, most of the code in this implementation is required for shared-element transition, such as creating an overlay, cloning items, and measuring view bounds. I just generalized them and made them usable by other transition types. If we have any plan to support custom transitions, trying to make the code specific to shared element seems counterproductive to me.

Also it seems there is more indirection than needed with extra classes like TransitionItems.

How so? Would renaming it to SharedElements or something address the indirection issue? Or did you mean something else?

I think the existing CardStack transition should work with shared elements.

Did you mean the CardStyleInterpolator etc? This PR actually uses those classes to create default platform transitions. It's more of a "container" of existing transition though since we need a lot more logic to implement shared element transition. Does this make sense?

lets avoid using lodash

I could replace lodash. I used it because it's convenient and it's in the dependency list of react-native: https://github.com/facebook/react-native/blob/master/package.json#L178. Will it eventually be removed there?

ericvicenti · 2017-04-10T19:53:47Z

So I think that a more advanced transition API would be nice, but we seem to have a long way to go before the API is decided on. If we try to implement it before the API is fully designed, we are likely to wind up with a very confusing implementation.

If we have any plan to support custom transitions, trying to make the code specific to shared element seems counterproductive to me.

I am concerned by adding all this extra code for generic custom transitions, when we aren't even sure what that API will look like. Instead, maybe this PR could focus on adding shared transitions, while leaving the card transition intact? So that the card will still come from the right or bottom, but the shared elements will float to the destination location.

Did you mean the CardStyleInterpolator etc? This PR actually uses those classes to create default platform transitions. It's more of a "container" of existing transition though since we need a lot more logic to implement shared element transition. Does this make sense?

I'm not sure exactly why the card style needs to change at all in this diff. We should just be adding shared elements.

lodash

Ah, the lodash usage seems OK. I didn't notice that RN already uses it. Generally it is best to use language features when possible, but this usage actually seems fine.

Also it seems there is more indirection than needed with extra classes like TransitionItems.

My main question here is: why do we need a full class for TransitionItems? Couldn't this data be represented with a bit of state in an existing module?

lintonye · 2017-04-19T17:39:34Z

To everyone who's watching this PR, as discussed with @ericvicenti, we've decided to do another round of refinement of the custom transitions API, before moving on with shared element transition. I'll post updates to the proposal on #175. Please stay tuned!

tlvenn · 2017-04-25T04:49:01Z

Thanks for the update and your hard work on this @lintonye ! Much appreciated.

facuacostag

Users need more transitioning options and this PR is perfect for that

chrsk · 2017-07-12T13:54:49Z

Are you currently working on the open tasks? Do you need any help?

nonameolsson · 2017-08-24T23:08:51Z

I would love to see this one merged! What's missing to get it merged?

JCMais · 2017-09-05T18:53:14Z

Can we please get an update on the status of this PR?

ronal2do · 2017-10-14T16:22:56Z

Any update?

nonameolsson · 2017-10-27T15:40:58Z

What is the state on this?

behzad888 · 2018-01-31T20:21:37Z

What is the state on this? @lintonye

brentvatne · 2018-02-09T17:54:23Z

this is an incredible effort! it seems like now it's a bit out of date -- @lintonye if you'd like to pick up where you left off here, @ericvicenti and I are working on react-navigation close to full-time now and we can support you in this with quick reviews and discussions. let's move over to react-navigation/rfcs#17 and turn this into a RFC, then circle back to a PR once that's ready.

sorry to everyone who is waiting for this, feel free to weigh in on the rfc thread mentioned above with your ideas around this API, or to vote on https://react-navigation.canny.io/feature-requests/p/shared-element-transitions if this is important to you.

lintonye added 30 commits March 31, 2017 13:14

Add transition files

185966e

Add transition Playground example

f3ca1d0

Transition-ify CardStack

69e2e56

No need to use prevTransitionProps to create styleMap

8653f17

Remove prevTransitionProps

e308188

Fix warning about keys

1186320

Enable transition for Card

7884929

Transition.SharedElement.Image

557ff88

initTransition => bindTransition

a9add5b

Merge branch 'multi-transitions-rewrite' into shared-element

2ce0f75

* multi-transitions-rewrite: initTransition => bindTransition

Add initial sharedElement transition

85c6817

Default transition

4a0c27d

Use default transition if can't find matching one

deca625

Update comments

b28a0c3

Add unit tests for transitions

46fa6ba

Merge branch 'multi-transitions-rewrite' into shared-element

f94f9bc

* multi-transitions-rewrite: Add unit tests for transitions Update comments Use default transition if can't find matching one Default transition

Use sharedElement transition if applicable

e9af592

TransitionItem: pass a config param instead of individual fields

6f8ed4d

Transition.SharedElement.*

eb808f9

Restructure a bit _findTransitionContainer

bd87bae

Merge branch 'multi-transitions-rewrite' into shared-element

243bf5b

* multi-transitions-rewrite: Restructure a bit _findTransitionContainer

Fix error due to useNativeDriver=true

936224d

Update playground root description

412fafc

Switch back to Playground root

198148b

Add go back button on shared element example

025a1a6

Add some type annotations

eeff31b

Merge branch 'master' into shared-element

4df9b89

* master: add jest config for react-navigation in docs (react-navigation#256) (react-navigation#331)

Remove transitionConfig hooks in StackNavigator

f4073c3

Clean up comments

b861bfd

ericvicenti requested changes Apr 6, 2017

View reviewed changes

lintonye added 2 commits April 6, 2017 11:44

that => this

b1ac1e6

Fix flow errors

6d8d944

lintonye and others added 8 commits April 9, 2017 23:12

Fix flow errors

a1c311b

Only call transition methods during transition

3b196e5

Fix flow errors

b328d0a

Make defaults for getItemsToMeasure and getItemsToClone

ab410d6

Fix Flow errors

ebf9e27

Fix failing unit test

d3ef6ec

Fix flow errors

43e8fab

Merge branch 'master' into shared-element

fe586bf

lintonye added 3 commits April 11, 2017 06:56

Create overlay only when requesting some items to clone

2aae2ac

Use position to interpolate overlay style

416ffe5

Use position to interpolate cloned items on scene

5aa7ace

facuacostag approved these changes May 10, 2017

View reviewed changes

Sam1301 mentioned this pull request Jun 12, 2017

Add slide animation view. zulip/zulip-mobile#682

Merged

brentvatne mentioned this pull request Feb 9, 2018

Shared element transitions react-navigation/rfcs#17

Open

brentvatne closed this Feb 9, 2018

react-navigation locked and limited conversation to collaborators Feb 9, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Shared element transition #941

Shared element transition #941

lintonye commented Apr 6, 2017 •

edited

Loading

ericvicenti left a comment

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

lintonye commented Apr 6, 2017 •

edited

Loading

ericvicenti commented Apr 10, 2017

lintonye commented Apr 19, 2017

tlvenn commented Apr 25, 2017

facuacostag left a comment

chrsk commented Jul 12, 2017

nonameolsson commented Aug 24, 2017

JCMais commented Sep 5, 2017

ronal2do commented Oct 14, 2017

nonameolsson commented Oct 27, 2017

behzad888 commented Jan 31, 2018 •

edited

Loading

brentvatne commented Feb 9, 2018

Shared element transition #941

Shared element transition #941

Conversation

lintonye commented Apr 6, 2017 • edited Loading

Motivation

Usage Example

Quick guide to the code

Test plan

Known issues

ericvicenti left a comment

Choose a reason for hiding this comment

This comment was marked as abuse.

This comment was marked as abuse.

This comment was marked as abuse.

lintonye commented Apr 6, 2017 • edited Loading

ericvicenti commented Apr 10, 2017

lintonye commented Apr 19, 2017

tlvenn commented Apr 25, 2017

facuacostag left a comment

Choose a reason for hiding this comment

chrsk commented Jul 12, 2017

nonameolsson commented Aug 24, 2017

JCMais commented Sep 5, 2017

ronal2do commented Oct 14, 2017

nonameolsson commented Oct 27, 2017

behzad888 commented Jan 31, 2018 • edited Loading

brentvatne commented Feb 9, 2018

lintonye commented Apr 6, 2017 •

edited

Loading

lintonye commented Apr 6, 2017 •

edited

Loading

behzad888 commented Jan 31, 2018 •

edited

Loading