Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transition performance heavy screen #6775

Closed
AlexandreM59 opened this issue Nov 21, 2019 · 2 comments
Closed

Transition performance heavy screen #6775

AlexandreM59 opened this issue Nov 21, 2019 · 2 comments

Comments

@AlexandreM59
Copy link

This is not an issue, but this is a question for this new version of react-navigation.

Are the performance of transitions improved with this new version of react-navigation?

I am referring to this issue react-navigation/rfcs#51 (comment).
I have encountered the same problem, when I am loading a heavy screen or fetching data when a screen mounts in ComponentDidMount, the transition to the screen had most of the time a noticeable delay and I have to use InteractionManager to fetch the data after the screen has mount.
From what I understood, this delay was encountered since the animation was still calling the main thread and it was blocked since the screen rendering or the data fetching was using it.

I love react-navigation, it is super easy to implement and all, but my app feels slow because all this loading screen since I had to put InteractionManager a lot. It seams wix's react-native-navigation manage to handle this issue (see wix/react-native-navigation#3432) and I don't clearly see if it was resolved in the react-navigation V5. I have high hopes since the blog post on the website says "React Navigation meets native" 😄, so it should not use the Main thread for the transition and leave it for the data fetching or the rendering.

@rauchp
Copy link

rauchp commented Jan 28, 2020

Also wondering this.

@satya164 satya164 transferred this issue from react-navigation/navigation-ex Feb 7, 2020
@satya164
Copy link
Member

Closing since there's an RFC for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants