-
Notifications
You must be signed in to change notification settings - Fork 363
[Deployment Screen] Design #242
Comments
Couple of questions here:
|
This was discussed with @lukasschor: we'll keep the following approach:
@alongoni, FYI |
Hi @lukasschor , we define 6 steps that give to the user more information about the Safe deployment status. We use a variant of the 3 steps for creating a new Safe. Intentionally the 6 steps on the left don`t expand. This will improve the usability because all the steps are visible in all the proccess. If you are agree whith the design, I'll continue all steps. cc: @fernandomg |
I like this approach a lot. Let's add to the first step also this grey bar, saying "Please confirm the Safe creation in your wallet". And have a Retry button below (center-aligned). Error stateLet's call the "Abort" button "Cancel" and have both center-aligned to be more in line with other parts of the interface. |
@lukasschor, this are all steps: cc @fernandomg |
@alongoni, what about the last step. Shall we leave it for a few seconds and then redirect the user to the newly created Safe or add a button to navigate to it? |
@fernandomg. In my opinion I think that we shall leave it a few second. It's consitentent with the previous interaction pattern. Lukas, what do you think? |
Yes I would leave for 3 seconds, I would also use the checkmark illustration we use here for the last step: https://zpl.io/bP84XDD |
Gather some feedback within the office. Some insights contradict opinions I had earlier, so sorry about that. Could we use the same grey background as with the error message and say
Use a button for step 6 "Continue", no need to show a link to etherscan in this step Rename Step 6 in the progress bar to "Success" and leave out the "Waiting for confirmation on blockchain" screen. For steps 2-5 there should always be something moving on the screen. Either just using some dots "..." or have a loading spinner (e.g. in the progress bar on the left side). This would help the user understand that he does not need to take any action. |
Also, would it be possible to provide feedback on another tool than Github issues? e.g. Invision, or maybe Figma has a design review feature? The friction would be much lower to give feedback and link comments directly to parts of the screen. |
@lukasschor Here is the design in Figma, you can give feedback there. |
Nice! In the first screen the card background is a bit off compared to the other ones, but no need to change it in figma as long as the dev implementing it won't implement it 1:1. :) Looks very good! |
Story:
As a user deploying a new Safe I want to be better informed about the Safe deployment status so that I don't have to worry whether the deployment is going to be successful or not.
Improvement ideas:
Transaction submitted...``Validating transaction...
->Deploying smart contract...
->Generating your Safe...
->Setting up access policy...
->Waiting for confirmation on the blockchain...
)The text was updated successfully, but these errors were encountered: