Skip to content

feat(messenger): left-align the in-chat amount entry - #1362

Merged
bmc08gt merged 2 commits into
code/cashfrom
feat/chat-amount-entry-left-align
Aug 28, 2026
Merged

feat(messenger): left-align the in-chat amount entry#1362
bmc08gt merged 2 commits into
code/cashfrom
feat/chat-amount-entry-left-align

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

The tip and cash DM screens used the centred amount field with its currency flag. The updated design puts the amount at the screen inset under the app bar with the hint beneath it — the layout AmountEntryScreen already renders behind largeHeader, and the one the minimum-tip entry uses. The chat screen opts in; no new layout code.

Setting a tip needs the recipient's minimum stated somewhere, and the flag was not carrying it. A tip chat has both bounds, and AmountEntryDelegate has always described the ceiling, so the "enter up to" hint held the line while the floor — the rule the sender is likely to break — only appeared as an error after they broke it. AmountEntryStyle.standingHint lets a flow say which bound the resting hint describes; the chat's tip style picks the floor. The other consumers (withdrawal, tipping, minimum-tip, swap, cash DM) keep the ceiling by default. Errors are unchanged: an amount outside either bound still reports the bound it broke.

The chat's below-minimum prompt also becomes showInfo rather than showAlert, the same correction #1361 makes on the profile path.

Not in this change

  • The app bar chip. The design shows the recipient (avatar, name, chevron); the code shows TokenSelectionPill. Swapping it would remove the token switcher, which the design does not replace, so it stays.
  • The currency flag. largeHeader drops it, matching the design — this screen is denominated in the preferred currency, changed from settings.
  • TipAmountEntryScreen. The tip-card sheet is a different screen and is not in these frames; it is still centred.

The tip and cash DM screens used the centred amount field with its currency
flag. The updated design puts the amount at the screen inset under the app
bar with the hint beneath it — the layout AmountEntryScreen already renders
behind `largeHeader`, and the one the minimum-tip entry uses. The chat screen
opts in; no new layout code.

Setting a tip needs the recipient's minimum stated somewhere, and the flag
was not carrying it. A tip chat has both bounds, and the delegate has always
described the ceiling, so the "enter up to" hint held the line while the
floor — the rule the sender is likely to break — only appeared as an error
after they broke it. AmountEntryStyle.standingHint lets a flow say which
bound the resting hint describes; the chat's tip style picks the floor.
Everything else keeps the ceiling by default, and errors are unchanged: an
amount outside either bound still reports the bound it broke.

The chat's below-minimum prompt also becomes showInfo rather than showAlert.
Nothing has failed and nothing is being destroyed — the entry is under the
recipient's floor and needs raising.
@bmc08gt bmc08gt self-assigned this Aug 28, 2026
@github-actions github-actions Bot added the type: feature New functionality label Aug 28, 2026
@bmc08gt
bmc08gt merged commit 8a29c60 into code/cash Aug 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: feature New functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant