-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[HOLD][HIGH] Migrate the main chat list to FlashList #33725
Comments
Triggered auto assignment to @garrettmknight ( |
I expect this to be on HOLD until sometime in February, if not later, so I'm moving this back to monthly |
cc @muttmuure adding this to the New Expensify performance improvements project. I acknowledge that the problem statement is a bit of a reverse-solution but I think it's a good bet that this will provide substantial performance improvements, as FlashList is just much better for performance than FlatList. We've established that elsewhere where we've migrated to FlashList |
Still on HOLD |
on HOLD for comment linking |
HOLD, but could come off HOLD soon. Unclear if we'll prioritize |
@roryabraham we good to take this off hold? If so, where do you think it might fit in a wave, if any? I'm not 100% on the significance of this migration beyond general, better performance. |
Good question. As far as I know there's no significance beyond general, better performance of chat screens. |
@janicduplessis how is this going? |
I've been working on some other tasks, but should be good to come back on this soon. |
@janicduplessis @hannojg any updates here? |
@janicduplessis @hannojg same question! any updates here? |
Current status update to using FlashList We are still in the process of trying to fix
To summarise:
Something else we'd like to discuss is trying out a new list library called |
I think this is tricky as I bet there is many alternatives to explore. I think we should aim to look at the most popular and supported options. Feel free to check it out and if its really promising, consider doing some MVP and posting a proposal, but lets try not to spend too much time on it |
@hannojg @janicduplessis can you please post another update? thanks! |
We haven't progressed with that task yet. Janic unfortunately become unavailable for working on this. |
Posted in #expert-contributors
|
We re-evaluated this ticket internally and think that it's probably not worth the effort. We still want to work on making the chat list as fast as it can be. We want to build a few PoC (where we keep bidirectional scrolling in mind) and evaluate those. This will probably be a mix of:
We might want to either:
|
Thanks for the update @hannojg , I put the issue on hold for now. There's no big rush, I'm just going through HIGH and CRITICAL issues on the #quality project to ensure we're properly aligned and prioritized. |
Still on hold. |
HOLD on:
Problem
The main chat list is one of the most, if not the most important component in our app. If you scroll far or fast on this list, you may see frames drop. Furthermore, there are some known performance issues with this list (example). We have already migrated almost every other virtualized list in our app from FlatList to FlashList, because its performance is much better.
Solution
Let's build support for bidirectional pagination in FlashList, then enable it on the main chat list in E/App.
The text was updated successfully, but these errors were encountered: