Skip to content

[Liquid Glass Follow Up][Design] Spend footer total overlapped by the (+) FAB #104206

Open

Description

@grgia
  1. Spend footer total overlapped by the (+) FAB - long totals (e.g. high exchange-rate currencies) go under the FAB. Options: truncate with an ellipsis or stack the total under the expense count. Same issue exists with the old tab bar, so it can be handled together with the FAB update. (comment, suggestion)

Action Performed

  1. Sign in to an account with a currency that has a high exchange rate (e.g. IDR, VND) or many expenses.
  2. Open the Spend tab on a phone.
  3. Select a few expenses so the footer shows the selected count and total.

Expected Result
The total amount and its dropdown arrow are fully visible.

Actual Result
A long total runs underneath the (+) floating button and is partly covered.

Notes

Platforms

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
Issue OwnerCurrent Issue Owner: @sumo-slonik

Activity

  1. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    @sumo-slonik Whoops! This issue is 2 days overdue. Let's get this updated quick!

  2. melvin-bot commented on Oct 21, 2026

    @melvin-bot

    @sumo-slonik Eep! 4 days overdue now. Issues have feelings too...

  3. melvin-bot commented on Oct 23, 2026

    @melvin-bot

    @sumo-slonik Still overdue 6 days?! Let's take care of this!

  4. sumo-slonik commented on Oct 27, 2026

    @sumo-slonik
    Contributor

    @Expensify/design I mocked up both options from the original thread with a very long total (IDR 98,765,432,109,876.54) so the difference is easy to see:

    Image
    • Before: the total runs under the (+) button and the dropdown arrow is hidden.
    • Option A, truncate: the total ends with an ellipsis before the (+) button, so the arrow stays visible and the footer keeps its current height.
    • Option B, stacked: the total sits under the expense count, both left aligned. The full total and the arrow fit next to the (+) button, but the footer gets one line taller.

    Which option would you prefer as the solution?

  5. dannymcclain commented on Oct 27, 2026

    @dannymcclain
    Contributor

    I think I personally prefer option B (stacked) so we don't lose any information to truncation. But let's see what the rest of the team thinks!

  6. shawnborton commented on Oct 27, 2026

    @shawnborton
    Contributor

    I also like Stacked, but I assume we can do it only when we need to? Otherwise we keep them on the same line if the values are shorter?

  7. dubielzyk-expensify commented on Oct 28, 2026

    @dubielzyk-expensify
    Contributor

    B looks good agree. Wonder if it looks a bit too prominent on mobile when you see the full screen though? I kinda wonder if we could actually get away with showing only one of the values on mobile given the use cases.

  8. shawnborton commented on Oct 28, 2026

    @shawnborton
    Contributor

    Fair, maybe we can see the whole screenshot. I do like the idea of only using this though when we don't have enough space. Another thing we can do is remove spend from Total spend to help save space as well.

  9. dannymcclain commented on Oct 28, 2026

    @dannymcclain
    Contributor

    I do like the idea of only using this though when we don't have enough space

    Oh yeah I thought this was the plan - I don't think I'd want to stack them all the time if we can avoid it.

  10. melvin-bot commented on Oct 30, 2026

    @melvin-bot

    @sumo-slonik Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions