Open peterjah opened 1 year ago
@gregLibert @peterjah @Thykof
With Pierre we propose the following way for 'upload website' feature:
All this needs to be presented before first signing request to the user. So frontend refactoring is needed of the right-side panel.
Follow up tasks would include:
We need to decide on the approach so share thoughs :)
What do you mean by sign ? Does this means that the user need to type in his password 3 times to deploy a website ?
If we stay like this yes. If we add the ability for user to choose to sign without providing a password (for specific or all dApps) we remove the need to type passwords.
That'd be the 1st follow-up task.
This is an industry standard. Users are given possibility to choose whether to enter passwords each time or not.
I think that the 1st task on this subject is more about informing the user that a batch of transactions is being signed. Then we could go two directions:
Wdyt @peterjah and @longgamma-massa
From the UX point of you it means things don't change for users functionally, but he must see more information. @LucasF243 here we need that Scenario 1 described in Figma
We designed 3 flows. This is the flow to implement for "Keeping batch operations (user signs once), showing info about operations and fees to user. Designs: https://www.figma.com/file/LSaOibVDFb1reF6FePVn5l/Massastation?type=design&node-id=6365-27176&mode=design&t=Hp8cwqcX4eQ0YcTj-0
Error implemented for showing 'domain name taken' error before signing: https://www.figma.com/file/LSaOibVDFb1reF6FePVn5l/Massastation?type=design&node-id=6365-27290&mode=design&t=Hp8cwqcX4eQ0YcTj-0
Context The correlation ID is used to allow a dApp to send several operations when use is signing only one request. Today, this behaviour is hidden from the user point of view, and it is also quite risky in term of security because the dApp can send any operations without the explicit user approval.
There is to aspect to focus on:
Tasks
Idea of rules