Skip to content

fix(chat): morph Send Cash out of the composer's glass - #1008

Merged
bmc08gt merged 1 commit into
mainfrom
fix/composer-cash-glass-morph
Oct 7, 2026
Merged

bmc08gt merged 1 commit into
mainfrom
fix/composer-cash-glass-morph

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

Follow-up to #1006. The $ splitting from the message field read as two shapes overlapping rather than one piece of glass dividing.

The main cause was the rim. The field and $ each drew their own 1pt composerRim stroke on the control, apart from the glass. While the glass joined into one shape, the strokes stayed separate, so a full circle outline sat inside the field and crossed it at the neck.

  • Rim: on iOS 26 composerRim draws nothing, and Liquid Glass's own edge light follows the joined shape. The stroke stays for the material fallback before 26.
  • Glyph: the $ travels from the field's trailing edge with the bud, shows once the bud is out, and fades out in 0.1s on the way back in, so it is never seen inside the field.
  • Timing: $ waits 0.1s for the send arrow to shrink away, and the arrow waits 0.16s for $ to merge (only when $ is beside the field, not while editing). Before, both crossfaded in the same spot.
  • Spring and join distance: bounce drops from 0.3 to 0.12 so the overshoot doesn't carry $ back into the field, and the container joins glass within 8pt against the 10pt resting gap, so no thread is left between them at rest.

On iOS 26 the field also loses its rim at rest, not only during the morph.

The `$` split from the field read as two shapes overlapping. Each had its
own 1pt rim stroke, and while the glass joined the strokes stayed apart, so
a full circle outline sat inside the field and crossed it at the neck.

- On iOS 26 `composerRim` draws nothing; the glass's own edge light follows
  the joined shape. The stroke stays for the material fallback.
- The `$` glyph travels from the field's trailing edge with the bud, shows
  once the bud is out, and fades fast on the way back in.
- `$` waits 0.1s for the send arrow to leave, and the arrow waits 0.16s for
  `$` to merge, instead of both crossfading in one spot.
- Bounce drops from 0.3 to 0.12 so the overshoot doesn't touch the field
  again, and the glass joins within 8pt against the 10pt gap so no thread
  is left at rest.
@bmc08gt bmc08gt self-assigned this Oct 7, 2026
bmc08gt added a commit to code-payments/code-android-app that referenced this pull request Oct 7, 2026
#1702 put the send button inside the field's clip at the field's
current edge, so typing showed it left of the $ and then slid it right
as the field widened. It now appears at the $'s centre and overhangs
the field's edge until the field catches up; the clip takes the
overhang into account. Clearing still lets it ride the field's edge in.

Timing follows code-payments/code-ios-app#1008: the $ shrinks to 0.4
toward the field's trailing edge, waits 0.1s before coming back, and
fades on its own 0.12s ease-in and 0.1s ease-out. The send button
waits 0.16s for the $ to merge, except while editing.

The field spring keeps iOS's damping ratio (0.88) but uses stiffness
520 instead of 224. On iOS the glass merge makes the edge read as
settled by about 200ms; Android has no glass merge, so at 224 the
field visibly took the full ~300ms.
@bmc08gt
bmc08gt merged commit d5eb1e2 into main Oct 7, 2026
3 checks passed
bmc08gt added a commit that referenced this pull request Oct 7, 2026
…cript-header-card

* origin/main:
  fix(chat): morph Send Cash out of the composer's glass (#1008)
  fix(profile): open profiles from favorite groups and username search (#1011)
  fix(photos): set the accent color to blue so picker controls are readable (#1013)
  feat(profile): link a chat's token from its profile (#1010)

# Conflicts:
#	Flipcash/Core/Navigation/AppRouter+Destination.swift
#	Flipcash/Core/Screens/Profile/ChatProfileScreen.swift
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.

1 participant