Installer UX: wallet setup flow review

[nondiremanuel]

This is to track the brainstorming activity on the installer part to improve the usability of the setup of the descriptor. I will ask for the help of India on the design part and possibly come out with some proposals

This could also include design activities on the new Liana Connect installer flow (e.g. xpub sharing feature). To be decided if those are needed to be tracked in a separate issue

[nondiremanuel]

Just to keep the issue updated: after a first UX proposal and some discussion, we are now finalizing a prototype including the following templates/options at wallet creation:

• Inheritance: single sig as primary path, inheritance single sig as recovery path
• Safer Recovery (we should find a better name): single sig as primary path, recovery single sig as recovery path
• Safer Recovery and Inheritance: single sig as primary path, recovery single sig as 1st recovery path, inheritance single sig as 2nd recovery path
• Custom setup: you can set the primary path and recovery path(s) as you prefer

Once the figma prototypes are finalized, we will conduct some user interviews and adjust accordingly. The objective is to arrive to the start of v8 development phase with a final version of the design.

[nondiremanuel]

Some remarks from the in person discussion we had after testing the first draft of the implementation:

In general:

• We should use primary buttons when there is a specific suggested next click step. For example, when I enter a template, the primary button should be to set my primary key. After setting it, the primary button should be adding the next key, while editing the primary should become secondary.

For the custom "template":

• It would be better for now to have primary and recovery paths in separate steps. In the recovery paths definition, each recovery path should be visibly separated from each other, e.g. by including them in separate containers.
• For the recovery path, the timelock definition should come as first information and should be a very short sentence (such as: "Available after timelock value"). Such timelock value should be set as the default and should be viewed as a field that the user can click to be edited in a popup.
• The definition of the threshold for multisig could be represented by a small button below the keys that indicates the default value (N of N) which, if clicked, opens a popup with the possibility to edit it.