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
The aim of this is to improve app performance, reducing the number of views rendered, reanimated shared values, etc.
What would be the best practice in this scenario?
Suppose I have many bottom sheets along the app. A portion of those are used with Tab screens in react-navigation's bottom-tab-navigator, so they are rendered in views that are kept mounted. In theory, after the 10th bottom sheet or so, it starts getting a little crowded in there, and performance is impacted.
So back to the main question: is wrapping the app in a BottomSheetContext with a swappable JSX.Element a good alternative to this? If not, please guide me toward the best practice. And thanks for the amazing work!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The aim of this is to improve app performance, reducing the number of views rendered, reanimated shared values, etc.
What would be the best practice in this scenario?
Suppose I have many bottom sheets along the app. A portion of those are used with Tab screens in react-navigation's bottom-tab-navigator, so they are rendered in views that are kept mounted. In theory, after the 10th bottom sheet or so, it starts getting a little crowded in there, and performance is impacted.
So back to the main question: is wrapping the app in a BottomSheetContext with a swappable JSX.Element a good alternative to this? If not, please guide me toward the best practice. And thanks for the amazing work!
Beta Was this translation helpful? Give feedback.
All reactions