[CFI] Update table styles on NewDot web to use a more compact, information-dense layout

[MelvinBot]

Description

We're getting a lot of feedback from both internal employees as well as customers that the table style we use on NewDot web is a bit too airy. The lack of information density makes it harder to scan tables and causes a lot of vertical scrolling.

Proposed Solution

Update our table styles to use a more compact style. This should be a fairly straightforward front-end change focused on design tweaks to improve information density and reduce unnecessary vertical scrolling.

A rough POC was created and is available at: https://84676.pr-testing.expensify.com/

CleanShot.2026-03-23.at.07.54.53.mp4

Known Issues from POC

• Header overlap was observed in the POC and will need to be addressed in the final implementation

---

Original request from Slack by shawnborton

Issue Owner

Current Issue Owner: @Krishna2323

[shawnborton]

The PR for my POC is here, in case you want to see all of the changes I asked Melvin to do: https://github.com/Expensify/App/pull/84676/changes

Some things that we still need to handle:

• skeleton rows for this new style
• updating the icon size for bank feeds/etc to use the 28x28 "compact" version
• how to handle the layout shift we get when a mouse is plugged in (this could be a follow up, but we should move the table header as a fixed/absolute position element in the scrollable view?)

[Krishna2323]

@shawnborton @luacmartins I’m going through the PR conversation, and there’s a lot to grasp. I’m also considering opening a new PR, as the one by MelvinBot seems quite messy. Would that be okay?

Once I have all the context, I’ll post a summary of what @shawnborton has suggested so far to make sure we’re all on the same page. Working on the same PR might be a bit confusing.

[shawnborton]

Absolutely okay to use a new PR. The PR with Melvin was just to create the POC. If you use the url of the adhoc builds there, you can at least get an understanding of the design changes I want. Ideally you can do it in a much cleaner way :)