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
I didn't find the discussion title to make more sense than this.
This is what I have observed while testing mobile applications in low-end android devices, especially with Bottom Tabs.
When the user press on any other tab first time it takes around 300ms-500ms based on how many components that screen is having.
We were having this issue in the static Setting screen page in which we were just rendering 3 sections components (Not SectionList)
and when the user click on the tab it was literally taking 400ms to 500ms to render that page.
Now I completely agree it depends on the components We could have optimized and we did but still, the lag between the user clicks and the first render was noticeable.
Then we had to use the hack called lazy load to avoid the below components rendering initially. This was the worst solution we ever came up with.
But I think we can totally improve the first-click experience. I don't know if someone has faced a similar issue or not. Let me know your thought in the thread.
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
-
I didn't find the discussion title to make more sense than this.
This is what I have observed while testing mobile applications in low-end android devices, especially with Bottom Tabs.
When the user press on any other tab first time it takes around 300ms-500ms based on how many components that screen is having.
We were having this issue in the static Setting screen page in which we were just rendering 3 sections components (Not SectionList)
and when the user click on the tab it was literally taking 400ms to 500ms to render that page.
Now I completely agree it depends on the components We could have optimized and we did but still, the lag between the user clicks and the first render was noticeable.
Then we had to use the hack called lazy load to avoid the below components rendering initially. This was the worst solution we ever came up with.
But I think we can totally improve the first-click experience. I don't know if someone has faced a similar issue or not. Let me know your thought in the thread.
Beta Was this translation helpful? Give feedback.
All reactions