Skip to content

[Due for payment 2025-12-25] [Due for payment 2025-12-11] Temporarily use static assets instead lottie animations on web #76166

Closed

Description

@mountiny

Coming from this thread (check out for more context), we are going tomove to use static assets in web instead of lottie as it has high impact on cpu and memory usage.

@Expensify/design Could you please help us prepare the assets to use for all these pages we need to update? Thank you!

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 26, 2025
  2. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Triggered auto assignment to @dubielzyk-expensify (Design), see these Stack Overflow questions for more details.

  3. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  4. dannymcclain commented on Nov 26, 2025

    @dannymcclain
    Contributor

    Is there any chance we have a list of pages/places these animations show up? Would be super helpful to know when prepping assets to export.

  5. mountiny commented on Nov 26, 2025

    @mountiny
    ContributorAuthor

    @fabioh8010 will help with that

  6. fabioh8010 commented on Nov 26, 2025

    @fabioh8010
    Contributor

    @dannymcclain I will confirm which ones represent a performance problem to us.

  7. dubielzyk-expensify commented on Nov 27, 2025

    @dubielzyk-expensify
    Contributor

    Let's start here, but there are also animations on all of the empty states:

    Image Image
  8. dubielzyk-expensify commented on Nov 27, 2025

    @dubielzyk-expensify
    Contributor

    Here's the screens we'll start with and the zip with illustrations:

    Image

    illustrations.zip

    Let's add them all here

  9. 28 remaining items

  10. melvin-bot commented on Dec 11, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @fabioh8010 is from an agency-contributor and not due payment
    • Reviewer: @ahmedGaber93 owed $250 via NewDot
    • Contributor: @staszekscp is from an agency-contributor and not due payment

    BugZero Checklist (@NicMendonca)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  11. mountiny commented on Dec 16, 2025

    @mountiny
    ContributorAuthor

    $250 to @akinwale and to @ahmedGaber93

  12. NicMendonca commented on Dec 16, 2025

    @NicMendonca
    Contributor

    Payment Summary

    Contributor: @akinwale due $250 via NewDot
    Contributor: @ahmedGaber93 due $250 via NewDot

  13. changed the title [-][Due for payment 2025-12-11] Temporarily use static assets instead lottie animations on web[/-] [+][Due for payment 2025-12-25] [Due for payment 2025-12-11] Temporarily use static assets instead lottie animations on web[/+] on Dec 18, 2025
  14. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  15. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.81-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-12-25. 🎊

    For reference, here are some details about the assignees on this issue:

  16. melvin-bot commented on Dec 18, 2025

    @melvin-bot

    @mjasikowski @NicMendonca @fabioh8010 / @VickyStash / @ahmedGaber93 / @staszekscp The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  17. quinthar commented on Dec 19, 2025

    @quinthar
    Contributor

    Approved $250 to @akinwale

  18. JmillsExpensify commented on Jan 4, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @ahmedGaber93

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DesignWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions