You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
When designing UI with React, developers are able to implement animations using CSS transitions. CSS transitions are very useful as a quick way to stylize different transitions between the developers UI, and in some cases allows them to be more performant.
As for Roact, most animations are currently implemented using Otter. While Otter is very powerful, it lacks the performance of TweenService. This is due-to:
Repeated reconciliations (can be mostly negated by optimizing your Roact components)
Multiple engine bridges for each property assignment
If implemented correctly, with TweenService property changes can act like CSS transitions. The developer only needs to be concerned about the target value, and Roact + TweenService can take care of the rest under the hood.
I have looked at implementing this myself with bindings, unfortunately this is not an option as bindings eventually call setRobloxInstanceProperty which would negate the performance gain from using TweenService.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When designing UI with React, developers are able to implement animations using CSS transitions. CSS transitions are very useful as a quick way to stylize different transitions between the developers UI, and in some cases allows them to be more performant.
As for Roact, most animations are currently implemented using Otter. While Otter is very powerful, it lacks the performance of TweenService. This is due-to:
If implemented correctly, with TweenService property changes can act like CSS transitions. The developer only needs to be concerned about the target value, and Roact + TweenService can take care of the rest under the hood.
Such an implementation could look like so:
I have looked at implementing this myself with bindings, unfortunately this is not an option as bindings eventually call
setRobloxInstanceProperty
which would negate the performance gain from using TweenService.The text was updated successfully, but these errors were encountered: