Skip to content

perf: Split ExpenseReportListItemRow, defer ActionCell, extract Avatar#89083

Merged
luacmartins merged 19 commits into
Expensify:mainfrom
software-mansion-labs:perf/split-expense-report-list-item-row-defer-action-cell
May 12, 2026
Merged

perf: Split ExpenseReportListItemRow, defer ActionCell, extract Avatar#89083
luacmartins merged 19 commits into
Expensify:mainfrom
software-mansion-labs:perf/split-expense-report-list-item-row-defer-action-cell

Conversation

@jmusial

@jmusial jmusial commented Apr 28, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Split ExpenseReportListItemRow.tsx into a thin dispatcher that picks between ExpenseReportListItemRowWide (table layout) and ExpenseReportListItemRowNarrow (mobile layout) so each viewport only loads the code and dependencies it needs. Also extracted the avatar into a memoized ExpenseReportListItemAvatar] and introduced DeferredActionCell, which renders a skeleton on first paint and swaps in the real ActionCell after a transition to keep large lists responsive on initial render.

Perf gains

Big percived gain for web at a cost of button being behind skeleton on initial render.

image image

Fixed Issues

$ #89100
PROPOSAL:

Tests

  1. Start Spend/Expenses
  2. Navigate to Spend/Reports
  3. Should work as prod with possible skeleton loader on Row action buttons

Offline tests

Same as tests

QA Steps

Same as tests

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 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

MacOS: Chrome / Safari
Screen.Recording.2026-04-28.at.13.08.47.mov

@jmusial

jmusial commented Apr 28, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@codecov

codecov Bot commented Apr 28, 2026

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4ffed6fae7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +22 to +27
<PulsingView
shouldPulse
style={styles.w100}
>
<View style={[styles.w100, sizeStyle, {backgroundColor: theme.skeletonLHNIn}]} />
</PulsingView>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Block parent row clicks during deferred action placeholder

While DeferredActionCell shows the pulsing placeholder, the action column is no longer an interactive control, so clicks/taps in that area fall through to the enclosing list-row press handler (BaseListItem’s onPress) and open/select the row instead of running the row action. This is most visible on slower devices or busy initial renders where the transition keeps the skeleton visible longer, and it can trigger the wrong user action (e.g., opening the report when the user intended to approve/pay).

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

When skeleton shows there is no Action showed on a button just skeleton, we can assume that row click is with intention to see more details.

@jmusial jmusial changed the title Split ExpenseReportListItemRow, defer ActionCell, extract Avatar perf: Split ExpenseReportListItemRow, defer ActionCell, extract Avatar Apr 28, 2026
@jmusial jmusial marked this pull request as ready for review April 28, 2026 17:33
@jmusial jmusial requested review from a team as code owners April 28, 2026 17:33
@melvin-bot melvin-bot Bot requested review from DylanDylann and heyjennahay and removed request for a team April 28, 2026 17:33
@melvin-bot

melvin-bot Bot commented Apr 28, 2026

Copy link
Copy Markdown

@DylanDylann 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 the request for review from a team April 28, 2026 17:33
@jmusial

jmusial commented Apr 29, 2026

Copy link
Copy Markdown
Contributor Author

I'll be OOO until 10 May. @OlGierd03 will be looking after this PR until then.

isHovered={hovered}
isFocused={isFocused}
isPendingDelete={isPendingDelete}
isLargeScreenWidth={isLargeScreenWidth}

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.

NIT: Let’s remove the isLargeScreenWidth prop and handle the subscription inside the ExpenseReportListItemRow component.

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.

Good idea, moved it


return (
<View
style={[styles.flexRow, styles.alignItemsCenter, styles.gap3, styles.pt3]}

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.

Why do we need to add styles.pt3? This style seems new compared to before.

@OlGierd03 OlGierd03 May 7, 2026

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.

Before this PR pt3 was applied by the parent ExpenseReportListItem via a wrapping <View style={styles.pt3}> around the narrow render (1c4c652). Spacing is unchanged

@DylanDylann

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: efbf5ab16d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +17 to +21
<PulsingView
shouldPulse
style={styles.w100}
>
<View style={[styles.w100, sizeStyle, {backgroundColor: theme.skeletonLHNIn}]} />

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve action-cell click target during deferred render

Returning a non-interactive skeleton here removes the action button’s press handler during the initial deferred window. In BaseListItem, taps inside the row bubble to the row onPress, so clicking the action column before ActionCell mounts will navigate/select the row instead of performing the intended action. This creates a user-visible behavior regression on first paint (and each virtualized remount) for anyone who taps quickly.

Useful? React with 👍 / 👎.

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.

I think it's fine

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.

I think that's fine, too, as @jmusial mentioned we can assume that row click is with intention to see more details

@DylanDylann

DylanDylann commented May 3, 2026

Copy link
Copy Markdown
Contributor

@jmusial Let’s discuss the use of DeferredActionCell. While it helps improve list rendering performance, it will cause flickering when users switch between lists. I’d like to hear other thoughts on this change.

cc @luacmartins @Expensify/design

Before

Screen.Recording.2026-05-03.at.17.56.14.mov

After

Screen.Recording.2026-05-03.at.17.55.43.mov

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

Yeah same as design. If there's a benefit with going with 1 over 2, then that makes sense to me.

@DylanDylann

Copy link
Copy Markdown
Contributor

@jmusial Your solution looks great. Could you merge the latest main and complete the PR and ping me for the final review?

@mountiny mountiny requested a review from Copilot May 12, 2026 08:32
jmusial added a commit to software-mansion-labs/expensify-app-fork that referenced this pull request May 12, 2026

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

This PR refactors the expense report search list row to improve perceived performance in large lists by separating wide vs. narrow row implementations, extracting the avatar rendering, and deferring the heavier action-button cell behind an initial placeholder.

Changes:

  • Split ExpenseReportListItemRow into a dispatcher (index.tsx) with ExpenseReportListItemRowWide and ExpenseReportListItemRowNarrow.
  • Extracted the avatar rendering into ExpenseReportListItemAvatar.
  • Added DeferredActionCell and wired it into the wide layout to defer rendering the real ActionCell until after initial paint.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/types.ts Introduces shared prop types for the new narrow/wide row split.
src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/index.tsx Dispatcher component that selects wide vs. narrow layout based on responsive breakpoint.
src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/ExpenseReportListItemRowWide.tsx Wide/table implementation; uses extracted avatar component and DeferredActionCell.
src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/ExpenseReportListItemRowNarrow.tsx New narrow/mobile row implementation with compact summary/accessibility label.
src/components/Search/SearchList/ListItem/ExpenseReportListItemRow/ExpenseReportListItemAvatar.tsx Extracted avatar rendering + border-color logic.
src/components/Search/SearchList/ListItem/ExpenseReportListItem.tsx Simplifies rendering to always use ExpenseReportListItemRow (dispatcher handles layout).
src/components/Search/SearchList/ListItem/ActionCell/DeferredActionCell.tsx Adds deferred rendering wrapper with an initial disabled placeholder button.

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

Comment on lines +3 to +39
import ExpenseReportListItemRowNarrow from './ExpenseReportListItemRowNarrow';
import ExpenseReportListItemRowWide from './ExpenseReportListItemRowWide';
import type {ExpenseReportListItemRowProps} from './types';

function ExpenseReportListItemRow(props: ExpenseReportListItemRowProps) {
const {isLargeScreenWidth} = useResponsiveLayout();

if (isLargeScreenWidth) {
return (
<ExpenseReportListItemRowWide
item={props.item}
reportActions={props.reportActions}
showTooltip={props.showTooltip}
canSelectMultiple={props.canSelectMultiple}
isActionLoading={props.isActionLoading}
onButtonPress={props.onButtonPress}
onCheckboxPress={props.onCheckboxPress}
containerStyle={props.containerStyle}
isSelectAllChecked={props.isSelectAllChecked}
isIndeterminate={props.isIndeterminate}
isDisabledCheckbox={props.isDisabledCheckbox}
isHovered={props.isHovered}
isFocused={props.isFocused}
isPendingDelete={props.isPendingDelete}
columns={props.columns}
/>
);
}
return (
<ExpenseReportListItemRowNarrow
item={props.item}
onCheckboxPress={props.onCheckboxPress}
canSelectMultiple={props.canSelectMultiple}
isSelectAllChecked={props.isSelectAllChecked}
isIndeterminate={props.isIndeterminate}
isDisabledCheckbox={props.isDisabledCheckbox}
/>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Bundle splitting is not used for App and AFAIK we do not want to do this

Comment on lines +18 to +22
function ExpenseReportListItemAvatar({item, showTooltip, isHovered = false, isFocused = false, isLargeScreenWidth = false}: ExpenseReportListItemAvatarProps) {
const StyleUtils = useStyleUtils();
const styles = useThemeStyles();
const theme = useTheme();

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

React compiler handles memoization

@DylanDylann

Copy link
Copy Markdown
Contributor

@jmusial Could you check the failed Reassure Performance Tests? Is this intentional?

@jmusial

jmusial commented May 12, 2026

Copy link
Copy Markdown
Contributor Author

@DylanDylann checking, but I think there weren't failing before latest merge main 😢

@jmusial

jmusial commented May 12, 2026

Copy link
Copy Markdown
Contributor Author
 - [ReportActionsList] should render ReportActionsList with 500 reportActions stored [render]: 0.0 ms → 0.0 ms  | 3 → 5 (+2, +66.7%) 🔴🔴

This is the error 0.0 ms → 0.0 ms :(

And I think this is on ReportScreen so we;re not touching that in this PR

@DylanDylann

Copy link
Copy Markdown
Contributor

@mountiny Could you trigger again the Reassure Performance Tests?

@jmusial

jmusial commented May 12, 2026

Copy link
Copy Markdown
Contributor Author

@DylanDylann pushed empty commit to retrigger 😄

@DylanDylann

Copy link
Copy Markdown
Contributor

@MelvinBot Could you investigate why the Reassure Performance Tests failed? I suspect that using useDeferredValue is causing a change in the render count.

@MelvinBot

Copy link
Copy Markdown
Contributor

Your suspicion is correct — useDeferredValue is causing the extra renders.

What failed: The [ReportActionsList] should render ReportActionsList with 500 reportActions stored Reassure test has a render count 2 higher than baseline. The validation uses COUNT_DEVIATION: 0 (zero tolerance), so any increase fails.

Why: DeferredActionCell uses useDeferredValue(true, false), which by design causes two render passes per component instance — first with false (skeleton), then deferred with true (real ActionCell). Each deferred value transition triggers an additional render cycle in React's concurrent scheduler, which increases the overall render count measured by Reassure.

Investigation details

The Reassure validation at .github/actions/javascript/validateReassureOutput/validateReassureOutput.ts computes current.meanCount - baseline.meanCount and fails if this exceeds COUNT_DEVIATION (set to 0). The current difference is exactly 2.

The DeferredActionCell component:

const shouldRender = useDeferredValue(true, false);
// First render: shouldRender = false → skeleton button
// Deferred render: shouldRender = true → real ActionCell

This is the only new useDeferredValue introduced by this PR. The other usages (useSearchResults, useSavedSearchTitles, MoneyRequestReportPreviewContent) already existed on main.

Options to fix:

  1. Update the Reassure baseline — if the +2 renders are an acceptable tradeoff for the perceived perf gain (skeleton → real content), regenerate the baseline to account for the deferred render pass
  2. Gate DeferredActionCell behind the test environment — skip the deferred pattern in tests so the baseline stays stable (not ideal, hides real behavior)
  3. Adjust COUNT_DEVIATION — increase from 0 to 2 to tolerate the deferred renders (affects all perf tests though, so probably not desirable)

@jmusial

jmusial commented May 12, 2026

Copy link
Copy Markdown
Contributor Author

@MelvinBot I doubt :

DeferredActionCell.tsx is only referenced by ExpenseReportListItemRowWide.tsx:191.
ExpenseReportListItemRowWide is only used by ExpenseReportListItem.tsx:312 — i.e. Search's expense report row.
The failing test renders @pages/inbox/report/ReportActionsList — the chat report-actions list, which doesn't import any Search/SearchList/ListItem/* files.

Also getting green on local, re-merged latest main, possibly was still out of date before.
image

@DylanDylann

DylanDylann commented May 12, 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 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
    • MacOS: Desktop
  • 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
Screen.Recording.2026-05-12.at.17.09.39.mov
Android: mWeb Chrome
Screen.Recording.2026-05-12.at.17.05.51.mov
iOS: HybridApp
Screen.Recording.2026-05-12.at.17.06.26.mov
iOS: mWeb Safari
Screen.Recording.2026-05-12.at.17.05.10.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-12.at.17.02.43.mov

@melvin-bot melvin-bot Bot requested a review from luacmartins May 12, 2026 10:23
@luacmartins luacmartins merged commit 194f7f6 into Expensify:main May 12, 2026
38 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @luacmartins 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

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

This PR is a purely internal performance refactoring — it splits ExpenseReportListItemRow into separate wide/narrow layout components, extracts a memoized avatar component, and defers ActionCell rendering with a skeleton placeholder.

There are no user-facing feature changes, new UI text, behavioral changes, or navigation flow updates.

No help site changes are required.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.73-4 🚀

platform result
🕸 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.