Skip to content

Connect Bull Bitcoin account, wizard copy, metadata backup screen redesign - #161

Draft
BullishNode wants to merge 4 commits into
getpaid-2-62-activation-feedbackfrom
getpaid-2-63-connect-and-copy
Draft

Connect Bull Bitcoin account, wizard copy, metadata backup screen redesign#161
BullishNode wants to merge 4 commits into
getpaid-2-62-activation-feedbackfrom
getpaid-2-63-connect-and-copy

Conversation

@BullishNode

Copy link
Copy Markdown
Owner

Owner QA findings from the live walkthrough: the Bull Bitcoin connection surface, plus two copy/design items. Stacked on the activation-feedback PR.

  • "Connect", not "Reconnect." From the user's perspective nothing was ever connected; "re-" read as an error. Retitled and reworded, and the three competing small buttons (the "all weird" wrap) replaced with a notice panel and full-width stacked actions — one primary, the rest outlined — matching the screen's own conventions.
  • The silent login loop is gone. When a login round-trip completes but no scoped settlement credential arrives (tonight: prod accounts can't issue it; the same loop would hit any user on a server-side issuance failure), the screen now says so explicitly and distinguishes the two states: login unfinished → Connect again; logged in but no settlement permission → Connect again + Contact support. The draft is preserved either way. New local-only connection-status probe (no credential material crosses the boundary).
  • Wizard's backup deferral button is now exactly "Not now".
  • The metadata backup options screen rebuilt in the Backup Settings language (it was the old inline card transplanted onto a route): status first with a coloured value and muted sub-line, a bordered notice when a half-finished recovery needs answering, full-width actions. Behaviour unchanged — same rules, same delete confirmation, same cubit; wallet_backup_controls.dart deleted and its lifecycle test retargeted.

Gates: analyze clean, fiat_settlement 48 + wizard 27 + backup_settings 90 green; on this tip the FULL suite 2360, repo-wide format clean, arb validate clean.

Nothing was ever connected from the merchant's side, so "Reconnect your Bull
Bitcoin account" read as though something had broken. State it as the first
connection it is, with its own heading above the explanation.

The actions under it were a wrapped row of small buttons — a filled Connect
beside an outlined Contact support and an outlined Continue with Bitcoin only,
reflowing at odd widths. Stack them full-width, one primary and the rest
outlined, exactly like the Save and Turn off buttons on the same screen.
…t permission

Returning from the Bull Bitcoin login cleared the failure and put the merchant
back on the same form. When the login had not produced a scoped settlement
credential — what a production account that cannot issue one does every time, and
what any server-side issuance failure looks like — the next save failed
identically, and the merchant went round again with nothing ever said.

Diagnose the round-trip locally instead of assuming it worked, and distinguish the
two outcomes: a login that was never completed, and a login that succeeded
without granting the settlement permission (where trying again is not the answer,
so support is offered). The draft is preserved in both cases, and a credential
that did arrive still clears the failure exactly as before.
"Not now (enable later in Backup settings)" put a navigation instruction inside a
button label. The button declines the offer; where to change one's mind later is
not the button's job.
…reen

The page was the old inline "Bull backup" card lifted out of Backup Settings and
dropped onto a route: a card inside a page, its own title repeating the page
title, a bare switch row, and two half-width Material buttons side by side.

Rebuild it in the language of the Backup Settings screen it opens from: the state
first, as a label with a coloured on/off value and the single fact that matters
under it; a bordered notice, with its own action, when a half-finished recovery
needs an answer before anything else; then the toggle and the actions as
full-width BBButtons — primary for backing up now, error-outlined for deleting.
Behaviour is unchanged: the same enablement rules, the same delete confirmation,
the same status and attention lines, driven by the same cubit.
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.

2 participants