Skip to content

[Due for payment 2025-07-04] Improve front end performance of opening an Expense Chat #63436

Closed

Description

@muttmuure

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


What performance issue do we need to solve?

Opening the Expense Chat has a deficit (acceptable minus actual) of -27.18 seconds

What is the impact of this on end-users?

End users will not tolerate a deficit of more than 2 seconds

List any benchmarks that show the severity of the issue

You can review the recording and retrieve logs here: https://expensify.slack.com/archives/C05LX9D6E07/p1749021762687029

Proposed solution (if any)

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:

View all open jobs on Upwork

Activity

  1. melvin-bot commented on Jun 4, 2025

    @melvin-bot

    Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

  2. muttmuure commented on Jun 4, 2025

    @muttmuure
    ContributorAuthor

    @gedu can I assign you to this issue?

  3. TMisiukiewicz commented on Jun 4, 2025

    @TMisiukiewicz
    Contributor

    @muttmuure you can assign me, I'm investigating this already

  4. TMisiukiewicz commented on Jun 10, 2025

    @TMisiukiewicz
    Contributor

    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

  5. TMisiukiewicz commented on Jun 12, 2025

    @TMisiukiewicz
    Contributor

    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

  6. TMisiukiewicz commented on Jun 13, 2025

    @TMisiukiewicz
    Contributor

    Let's keep an eye on the progress of sub-issues #63439, I asked if we can prioritize components related to Expense report

  7. melvin-bot commented on Jun 25, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  8. 17 remaining items

  9. melvin-bot commented on Jul 11, 2025

    @melvin-bot

    @TMisiukiewicz Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  10. melvin-bot commented on Jul 15, 2025

    @melvin-bot

    @TMisiukiewicz 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  11. melvin-bot commented on Jul 17, 2025

    @melvin-bot

    @TMisiukiewicz 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  12. melvin-bot commented on Jul 21, 2025

    @melvin-bot

    @TMisiukiewicz 12 days overdue now... This issue's end is nigh!

  13. melvin-bot commented on Jul 24, 2025

    @melvin-bot

    This issue has not been updated in over 14 days. @TMisiukiewicz eroding to Weekly issue.

  14. melvin-bot commented on Aug 19, 2025

    @melvin-bot

    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!

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions