Closed NicoSerranoP closed 1 year ago
Submit
button activates before the user has added their text entropy. edit: after further investigating, users are able to actually submit without entering any text entropy..If there is a reason for the interface to persist information, there should be a way for them to log out an address out in case they want to use a different one.
@tvanepps I got most of the observations finished but we should consider the following:
SnakeProgress
component that gets colored with the mouse movement. We need to reexport this graphic and check out with SVGator (the animation library) to see how we fix the misalignments in the snake head & body. Maybe @tkmct could you give us a hint?5.1. Wallet Choosing: I was not able to make the background blurred because it is an external component that doesn't let us set many options. I was able to make the background darker so the back image is not that visible. What do you think?
I increase the animation time from 12s to 40s in the waiting lobby. The rounding animation is slower now. The pulse animation is applied when the contribution is being computed. I think a more explicit animation (rounding) is better to notify the user he might have to wait a bit in the lobby.
The SIWE is done between the user, the external OIDC (SIWE) and the sequencer. After the exchange, the sequencer gives the user a session id to use it as an authentication method for the other routes (lobby and contribution phases). The double signing re-asks the user to sign a message because it is done between the user, the wallet provider and the frontend. After the signature, the frontend sends the signed message along with the contribution to the sequencer.
We could keep the main navbar (logo in the left and language switcher on the right) but it would cut out a piece of the pizza because its height. I feel we can leave the back arrow redirecting to home but what do you think?
@NicoSerranoP - your replies make sense, thanks for looking into my suggestions!