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 }}
Repository navigation
[Due for payment 2025-07-04] Improve front end performance of opening an Expense Chat #63436
Please list out the steps you think we should take to solve this issue.
List any benchmarks after implementing the changes to show impacts of the proposed solution (if any)
Note: These should be the same as the benchmarks collected before any changes.
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Version Number: Reproducible in staging?: Reproducible in production?: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation Expensify/Expensify Issue URL: Issue reported by: Slack conversation:
Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.
This PR is the first one that should speed things up: #63655
My measurements indicate drop in open_report from 6.5s to 4s and send_message from 1900 to 1250 on Android. For now it's a draft PR as we are waiting for a final decision regarding the implementation.
Additionally, I am reviewing PRs that are part of this issue: #63439
It's strictly related to report screen and once we remove all useOnyx calls from list items, it should significantly speed things up.
I am also working on a couple of more proposals, I should share them soon
This issue has not been updated in over 15 days. @TMisiukiewicz eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
melvin-bot commentedon Jun 4, 2025
Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.
muttmuure commentedon Jun 4, 2025
@gedu can I assign you to this issue?
TMisiukiewicz commentedon Jun 4, 2025
@muttmuure you can assign me, I'm investigating this already
TMisiukiewicz commentedon Jun 10, 2025
This PR is the first one that should speed things up: #63655
My measurements indicate drop in
open_reportfrom 6.5s to 4s andsend_messagefrom 1900 to 1250 on Android. For now it's a draft PR as we are waiting for a final decision regarding the implementation.Additionally, I am reviewing PRs that are part of this issue: #63439
It's strictly related to report screen and once we remove all
useOnyxcalls from list items, it should significantly speed things up.I am also working on a couple of more proposals, I should share them soon
TMisiukiewicz commentedon Jun 12, 2025
Here is anotrher draft PR that should improve opening an expense chat and speed up the app in general: #63980
I'm currently working on providing a test plan and testing it in the app
TMisiukiewicz commentedon Jun 13, 2025
Let's keep an eye on the progress of sub-issues #63439, I asked if we can prioritize components related to Expense report
melvin-bot commentedon Jun 25, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
17 remaining items
melvin-bot commentedon Jul 11, 2025
@TMisiukiewicz Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Jul 15, 2025
@TMisiukiewicz 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Jul 17, 2025
@TMisiukiewicz 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
melvin-bot commentedon Jul 21, 2025
@TMisiukiewicz 12 days overdue now... This issue's end is nigh!
melvin-bot commentedon Jul 24, 2025
This issue has not been updated in over 14 days. @TMisiukiewicz eroding to Weekly issue.
melvin-bot commentedon Aug 19, 2025
This issue has not been updated in over 15 days. @TMisiukiewicz eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!