Skip to content

Use lazy loading for company cards#75279

Merged
mollfpr merged 13 commits intoExpensify:mainfrom
ShridharGoel:lazyLoad
Dec 10, 2025
Merged

Use lazy loading for company cards#75279
mollfpr merged 13 commits intoExpensify:mainfrom
ShridharGoel:lazyLoad

Conversation

@ShridharGoel
Copy link
Contributor

@ShridharGoel ShridharGoel commented Nov 17, 2025

Explanation of Change

Use lazy loading for company cards

List of migrated assets:

  1. AmexCardCompanyCardDetail
  2. BankOfAmericaCompanyCardDetail
  3. BrexCompanyCardDetail
  4. CapitalOneCompanyCardDetail
  5. ChaseCompanyCardDetail
  6. CitibankCompanyCardDetail
  7. MasterCardCompanyCardDetail
  8. PlaidCompanyCardDetail
  9. StripeCompanyCardDetail
  10. VisaCompanyCardDetail
  11. WellsFargoCompanyCardDetail
  12. Large versions of all the above cards
  13. PendingBank
  14. CompanyCardsPendingState

Fixed Issues

$ #75247
PROPOSAL: #75247 (comment)

Tests

  1. Open Workspace > Cards > Company cards; confirm each card feed in the list shows the correct bank logo.
  2. On the “Add new” flow (Select bank step), verify every bank option renders its logo properly.
  3. In “Assign card” (selecting cards from a feed), ensure the feed icon renders for each card row and the search results still show the right logos.
  4. In Workspace member details, check the assigned card tiles show the correct bank icon and badge.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@melvin-bot
Copy link

melvin-bot bot commented Nov 17, 2025

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot removed request for a team November 17, 2025 08:31
@codecov
Copy link

codecov bot commented Nov 17, 2025

@brunovjk
Copy link
Contributor

@ShridharGoel Could you take a look at the errors here? Thank you.

@ShridharGoel
Copy link
Contributor Author

@brunovjk Updated.

@brunovjk
Copy link
Contributor

Great! Reviewing ASAP.

@mollfpr
Copy link
Contributor

mollfpr commented Nov 18, 2025

@ShridharGoel Could you resolve the conflict? Thank you!

@ShridharGoel
Copy link
Contributor Author

Updated.

@brunovjk
Copy link
Contributor

brunovjk commented Nov 18, 2025

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
75279_android_nattivv.mov
Android: mWeb Chrome
75279_android_web.mov
iOS: HybridApp
75279_ios_web.mov
iOS: mWeb Safari
75279_ios_web.mov
MacOS: Chrome / Safari
75279_web_chrome.mov

import {COMPANY_CARD_BANK_ICON_NAMES, COMPANY_CARD_FEED_ICON_NAMES} from '@libs/CardUtils';
import {useMemoizedLazyIllustrations} from './useLazyAsset';

function useCompanyCardFeedIcons() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ShridharGoel should we add explicit return types? Thanks.

@brunovjk
Copy link
Contributor

We have some falling checks here @ShridharGoel, could you fix them for us? Thank you.

@ShridharGoel
Copy link
Contributor Author

@brunovjk Updated.

@brunovjk
Copy link
Contributor

Reviewing ASAP

Copy link
Contributor

@JmillsExpensify JmillsExpensify left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No review required from a product perspective. Unsubscribing.

@mollfpr
Copy link
Contributor

mollfpr commented Nov 20, 2025

@ShridharGoel Could you resolve the conflict? Thank you!

@brunovjk
Copy link
Contributor

I'll review it now, @ShridharGoel, we still have some conflicts. Thank you.

@ShridharGoel
Copy link
Contributor Author

@brunovjk Actually this keeps getting conflicts because it seems these files are being frequently changed. I'll update to fix them.

@ShridharGoel
Copy link
Contributor Author

@brunovjk Updated.

@brunovjk
Copy link
Contributor

Sorry for the delay @ShridharGoel, I've been busy. I'll review it here today. Could you resolve the conflicts? Thank you very much.

@ShridharGoel
Copy link
Contributor Author

@brunovjk Updated

@brunovjk
Copy link
Contributor

@ShridharGoel Do we need to provide steps to test this PR? I tested the app's overall functionality and it seems fine.

@ShridharGoel
Copy link
Contributor Author

We just need to check that the various icons are being rendered properly. Is it fine to mention it as NoQA ?

@brunovjk
Copy link
Contributor

Good question. @mollfpr can you help us confirm if we need QA here? Thank you.

@mollfpr
Copy link
Contributor

mollfpr commented Dec 2, 2025

Let's not add NoQA here since it only focuses on the company card assets, and list out the assets that migrated so the QA team will be aware of the migrated assets.

@brunovjk
Copy link
Contributor

brunovjk commented Dec 2, 2025

Great, thanks for the clarification.

@ShridharGoel please update the PR and the Test Steps accordingly. Let me know if you need anything. Thanks.

@ShridharGoel ShridharGoel changed the title [NoQA] Use lazy loading for company cards Use lazy loading for company cards Dec 2, 2025
@ShridharGoel
Copy link
Contributor Author

Updated

Copy link
Contributor

@brunovjk brunovjk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@melvin-bot melvin-bot bot requested a review from mollfpr December 2, 2025 15:32
@brunovjk
Copy link
Contributor

brunovjk commented Dec 2, 2025

@mollfpr do you think the "Test Steps" here are sufficient? Thank you.

cc: @ShridharGoel

@mollfpr
Copy link
Contributor

mollfpr commented Dec 6, 2025

@ShridharGoel, could you give a few example steps to verify the asset?

@ShridharGoel
Copy link
Contributor Author

Added

@mollfpr mollfpr merged commit 6016c0b into Expensify:main Dec 10, 2025
32 checks passed
@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.2.75-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.2.75-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mollfpr in version: 9.2.77-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 cancelled 🔪
🍎 iOS 🍎 cancelled 🔪

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.2.77-1 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants