Skip to content

Update personal card details UI#89396

Merged
nkuoch merged 9 commits into
Expensify:mainfrom
ShridharGoel:personalCardUI
May 29, 2026
Merged

Update personal card details UI#89396
nkuoch merged 9 commits into
Expensify:mainfrom
ShridharGoel:personalCardUI

Conversation

@ShridharGoel

@ShridharGoel ShridharGoel commented May 1, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Updated the personal card details page to match the finalized Figma layouts:

  • Moved the cardholder name onto the card artwork.
  • Centered the last updated text above the action buttons.
  • Used the shared card details action button helper for the personal-card action buttons.
  • Matched the personal card broken-connection error row spacing.
  • Updated the Fix card action to use the small danger button style.
  • Kept the card details rows in the Figma order.
  • Removed the extra gap between the PIN row and the next card menu item by grouping the menu rows under one top margin.

Fixed Issues

$ #87497
PROPOSAL: N/A

Tests

  1. Open the personal card details page from Wallet.
  2. Verify the cardholder name is shown inside the card artwork.
  3. Verify the last updated text is centered above the action buttons.
  4. Verify Update card and View transactions are shown as equal-width action buttons.
  5. Open a personal card with a broken connection.
  6. Verify the broken connection message appears below the action buttons.
  7. Verify Fix card is shown as a small danger button.
  8. Verify the card number, reimbursable setting, transaction start date, and remove card rows match the Figma order.
  9. Verify that no errors appear in the JS console.
  • Verify that no errors appear in the JS console

Offline tests

  1. Open the personal card details page.
  2. Turn off the network connection.
  3. Verify disabled card action buttons stay disabled where needed.
  4. Verify the page layout stays the same.

QA Steps

  1. Open the personal card details page from Wallet.
  2. Verify the cardholder name is shown inside the card artwork.
  3. Verify the last updated text is centered above the action buttons.
  4. Verify Update card and View transactions are shown as equal-width action buttons.
  5. Open a personal card with a broken connection.
  6. Verify the broken connection message appears below the action buttons.
  7. Verify Fix card is shown as a small danger button.
  8. Verify the card number, reimbursable setting, transaction start date, and remove card rows match the Figma order.
  9. Verify that no errors appear in the JS console.
  • 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
  • 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 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, 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 Screenshot 2026-05-21 at 2 37 22 AM
iOS: Native Screenshot 2026-05-21 at 2 51 28 AM
iOS: mWeb Safari Screenshot 2026-05-21 at 2 52 51 AM
MacOS: Chrome / Safari Screenshot 2026-05-21 at 2 36 38 AM

@codecov

codecov Bot commented May 1, 2026

Copy link
Copy Markdown

@ShridharGoel ShridharGoel changed the title Align personal card details with Figma Update personal card details UI May 1, 2026
@ShridharGoel ShridharGoel force-pushed the personalCardUI branch 5 times, most recently from ce85009 to b3c82da Compare May 19, 2026 22:14
@ShridharGoel ShridharGoel marked this pull request as ready for review May 20, 2026 21:07
@ShridharGoel ShridharGoel requested review from a team as code owners May 20, 2026 21:07
@melvin-bot melvin-bot Bot requested review from Pujan92 and trjExpensify and removed request for a team May 20, 2026 21:07
@melvin-bot

melvin-bot Bot commented May 20, 2026

Copy link
Copy Markdown

@Pujan92 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]

@trjExpensify trjExpensify requested review from flaviadefaria and removed request for trjExpensify May 21, 2026 01:21
@trjExpensify

Copy link
Copy Markdown
Contributor

Switching @flaviadefaria on for the product review.

@Pujan92

Pujan92 commented May 21, 2026

Copy link
Copy Markdown
Contributor

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 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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.js 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.
  • 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
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

@Pujan92

Pujan92 commented May 21, 2026

Copy link
Copy Markdown
Contributor

@ShridharGoel can we bring the changes of #91230 here in a single PR?

@flaviadefaria

Copy link
Copy Markdown
Contributor

For visibility, this is now blocking two other projects, so @ShridharGoel, we'd really appreciate it if you could prioritize fixing these issues. Let me know if I can help in any way.

@ShridharGoel

Copy link
Copy Markdown
Contributor Author

Updated

@flaviadefaria

Copy link
Copy Markdown
Contributor

@ShridharGoel is this ready for review? One of our internal engineers also wants to help review the PR so I'll assign him once you're ready.

@ShridharGoel

Copy link
Copy Markdown
Contributor Author

Yes it's ready

@Pujan92 Pujan92 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!

Image

#89379 (comment) -- Fixed

Image

#91138 - Fixed

Screen.Recording.2026-05-28.at.16.55.24.mov

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Refreshes the personal card details page to match the finalized Figma layouts: the cardholder name is rendered on the card artwork, last-updated text is centered above the action buttons, the shared CardDetailsActionButtons helper now drives the Update card / View transactions buttons, the broken-connection error row is restyled with a small danger "Fix card" button, and the menu rows below are grouped under a single top margin. The PR also drops redundant iconFill={theme.icon} props and the now-unused useTheme imports across several card-detail pages, and moves the Change PIN row in ExpensifyCardPage into the lower action-rows group.

Changes:

  • Restructure PersonalCardDetailsPage to add the cardholder name overlay, centered last-updated text, shared action buttons, and a redesigned broken-connection row.
  • Slim down PersonalCardDetailsHeaderMenu by removing the update/view-transactions/last-updated rows (now lifted to the parent) and grouping the remaining rows under a single mt4 wrapper.
  • Remove unused useTheme/iconFill={theme.icon} props across several card pages, and regroup the Change PIN row inside ExpensifyCardPage under the bottom action-rows section.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
src/pages/settings/Wallet/PersonalCardDetailsPage.tsx Adds cardholder overlay, centered last-updated text, shared action buttons, restyled broken-connection row, and grouped menu wrapper.
src/pages/settings/Wallet/PersonalCardDetailsHeaderMenu.tsx Drops update/view-transactions/last-updated rows (now in the parent) and wraps trailing rows in a single mt4 view.
src/pages/settings/Wallet/ExpensifyCardPage/index.tsx Moves Change PIN row into the lower action-rows group, removes useTheme/iconFill props, sets mb0 on action buttons.
src/pages/workspace/expensifyCard/WorkspaceExpensifyCardDetailsPage.tsx Removes unused useTheme import and iconFill={theme.icon} from action buttons.
src/pages/workspace/companyCards/WorkspaceCompanyCardDetailsPage.tsx Removes unused useTheme import and iconFill={theme.icon} from action buttons.
src/components/FrozenCardHeader.tsx Removes unused useTheme import and iconFill={theme.icon} from the unfreeze button.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/pages/settings/Wallet/PersonalCardDetailsPage.tsx Outdated
@nkuoch nkuoch merged commit bbea633 into Expensify:main May 29, 2026
37 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @nkuoch has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/nkuoch in version: 9.3.90-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no doc changes required.

I reviewed the changes in this PR against the help site articles under docs/articles. This PR is a purely visual/layout refinement to match the finalized Figma layouts for the personal card details page — it does not add, remove, or change any feature, behavior, copy string, or user flow.

The only article that documents this screen is Manage-Personal-Cards.md, and every behavior it documents remains accurate:

Documented action Status after this PR
Fix card (fix broken connection) Still present — restyled as a small danger button, same action
Update card (manual refresh) Still present — moved into the shared action-button row
View transactions Still present — equal-width action button
Rename card / Mark transactions as reimbursable toggle Unchanged
Remove / unassign card Unchanged
Last successful import ("last updated") info Still shown — now centered above the action buttons
Why no changes are needed

The changes here are layout-only: cardholder name moved onto the card artwork, the "last updated" line centered, action buttons unified via the shared CardDetailsActionButtons helper, the broken-connection error row re-spaced, Fix card restyled, and card-detail rows reordered to match Figma. None of these alter what a user can do on the page.

The help article describes the page in terms of the actions available (steps like "Choose Fix card", "tap Update card"), not the visual arrangement or positioning of those elements. Since all of those actions and their labels are preserved, the article text stays correct. The article's screenshots are illustrative and are already tracked separately for a design refresh (see the existing SCREENSHOT/Design-request placeholder in the file), so they're out of scope for a markdown docs PR.

ShridharGoel — no draft docs PR was created because no help site copy changes are needed for this layout update. If you believe a screenshot refresh or wording tweak is warranted, let me know which behavior changed and I'll prepare a docs PR.

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #92228 was identified to be related to this PR.

@OSBotify

OSBotify commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.90-3 🚀

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

@JS00001 JS00001 mentioned this pull request Jun 2, 2026
54 tasks
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.

9 participants