Findings on the performance about fluidtransitions HOT 6 CLOSED

@MrLoh This library uses native animations for moving and scaling elements using a technique similar to FLIP like you are describing. The discussion here is about finding a way to open up for animating properties not supported by the native driver. There are several issues I'm working on to get this to work properly.

First of all we have the problem of not being able to use stateless components for animating (with Animated.createAnimatedComponent). This can be solved by creating a wrapper for the stateless component and transferring shared element/transition properties.

Next we have the issue with native vs. non-native animations. I'm close to solving this by creating another set of wrappers that basically creates two outer elements, one for native animations and one for non-native animations.

With these solutions I'm pretty confident that we can create a good-enough solution to the problems with animations, with the limitation in performance that @narendrashetty has pointed out for some of the animations, but with full native support where applicable.

from fluidtransitions.

Thanks for your feedback! It is really appreciated.

What I'm trying to do with combining native/non-native animations is to run native animations like transforms and opacity using the native driver while running other animations with the non-native driven animated value. This is not a trivial task to implement so we'll see what the results will be.

from fluidtransitions.

Totally makes sense. Will follow your development :)

from fluidtransitions.

The trick is that to be able to animate every component (also function-based stateless components which normally does not play well with animated) I'm wrapping my component and thought I could wrap in to components - one used for native animations and one for non-native animations. It's a little tricky to transfer the correct style props and build the component.

from fluidtransitions.

I was also thinking, since it's not possible for layout properties with native driver, how about we work on an addon which works with layout properties too. I know this is beyond the scope of this library, just thinking out loud. Don't know if it's even possible

from fluidtransitions.

I’m no expert on the matter but from my understanding the only performant approach to layout animations is using the FLIP technique. No matter what Plattform layout animations are just not performant because of how rendering works on native and web platforms. So animating layout properties should just be discouraged probably.

from fluidtransitions.