diff options
| author | Adam Soltys <[email protected]> | 2026-09-07 00:35:09 -0700 |
|---|---|---|
| committer | Adam Soltys <[email protected]> | 2026-09-07 00:35:09 -0700 |
| commit | 037f025deba86713a470916964e9a388789f3b74 (patch) | |
| tree | b374863e2ebff3e1cf0f8a29372faaffb75ff83f /android | |
| parent | cbce9a56e2ed41cf8586a467af5ab5a5f43bc430 (diff) | |
| download | coinosv3-037f025deba86713a470916964e9a388789f3b74.tar.gz coinosv3-037f025deba86713a470916964e9a388789f3b74.zip | |
Tap payments: no recipient-form flash before the pay animation.
A scanned/tapped/pasted payment (NFC LNURL, a pasted lnurl/lnaddr) briefly showed the recipient form — heading, recipient chip, "finding…" spinner and a Back button — while the LNURL was fetched over the network, before flowing into the pay animation + success. That resolving skeleton read as a form the user had to look at on every tap.
Now a tap carries a `tap` flag (set for the scan/paste/NFC entry points: matchSendText with !typed, lnAddressFallback, offers), and during resolve/invoice it renders a minimal centered paying shell — the same autopay-card the ark pay animation uses (spinner-ring ⚡ badge, no Back button) — so a tap goes straight spinner → animation → success with no form in between. Typed lightning addresses keep the normal form (they still resolve through the send form, not a tap). The resolved recipient name/amount arrive on the next screen; the shared card class makes the handoff into the ark autopay animation seamless.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01MGzU12QrAA4G6BYGzGVdXz
Diffstat (limited to 'android')
0 files changed, 0 insertions, 0 deletions