[UX/UI redesign] Wallet Creation

[editwentyone]

tackling the following issues: #10408, #10367, #10583

🎨 Figma Flow to experience yourself and to leave comments on the canvas (you need a free figma account)

Explanation Video

wasabi_walletcreation.webm

[nopara73]

Very good. To progress forward, let's break it down to parts those expected to have little resistance, so the UI team can already work on it:

1. I'd suggest to create a new issue about the Welcome Workflow. Let's improve a little bit on the wordings and it should be good to go.

2. I'd also suggest to open a new issue on the recovery word UX upgrade.

[BTCparadigm]

Nitpick:
In the video, the software gives a popup and says that wallet was created but then in "Backup Recovery Words" it asks user to back up the words and it says these wont be shown again after the wallet is created.
So was it created during the popup or after I confirm the words?
It will also ask for a password in the next screen, which is part of the backup, so it doesn't make sense that the software says a wallet was created before I set a password.

[turbolay]

Nitpick: [...]

IMO this is not a nitpick, this is really wrong. Basically we signal the user "Congrats! You did everything important" when in fact everything important is yet to be done.

[Kruwed]

The "verify words" part seems too easy for a user to skip without writing anything. When there are 4 blanks on the verify page and the entire correct words are already shown as options for the user, "brute forcing" all of the choices results in a only a maximum of 9 possible wrong guesses before they get the right combination. Users can even guess the correct order on the first try 1/16 times.

Another requirement to prevent the user from cheating is to randomize the 4 missing words on the verify screen if the user goes back to view the previous screen that shows all 12 words. This prevents them from going back memorizing the order of the 4 missing words since the missing words have changed once they go forward again.

I will brainstorm how to make the introduction texts better as well.

[editwentyone]

Nitpick: [...]

IMO this is not a nitpick, this is really wrong. Basically we signal the user "Congrats! You did everything important" when in fact everything important is yet to be done.

the idea is, that something (wallet) was basically created (the user knows something already happened) and now its about to secure it (backup). because backups have nothing to do with the creation of a wallet.

but if its generating to much of a hickup in the expected behaviour, we can also fall back to the known way.

[editwentyone]

The "verify words" part seems too easy for a user to skip without writing anything. When there are 4 blanks on the verify page and the entire correct words are already shown as options for the user, "brute forcing" all of the choices results in a only a maximum of 9 possible wrong guesses before they get the right combination. Users can even guess the correct order on the first try 1/16 times.

even if, thats not a problem, different user with different skills can game this screen. but not the majority.

Another requirement to prevent the user from cheating is to randomize the 4 missing words on the verify screen if the user goes back to view the previous screen that shows all 12 words. This prevents them from going back memorizing the order of the 4 missing words since the missing words have changed once they go forward again.

randomizing when going back and forth is a must here, but thats already implemented

I will brainstorm how to make the introduction texts better as well.

thanks :)