Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(bridge-ui): UI/UX suggestion to better inform the user #13476

Closed
ablankstory opened this issue Mar 27, 2023 · 2 comments · Fixed by #13488
Closed

feat(bridge-ui): UI/UX suggestion to better inform the user #13476

ablankstory opened this issue Mar 27, 2023 · 2 comments · Fixed by #13488

Comments

@ablankstory
Copy link
Contributor

ablankstory commented Mar 27, 2023

Describe the feature request

I put together a few screens that I think would help to better inform users of what to expect when bridging. It seems that most of them are not using the tool tips and don't realize:

  1. relayer will auto-claim if fee is set to Recommended
  2. user needs to manually claim (with ETH on receiving chain) if fee is set to None

Descriptions of each screenshot:

Screenshot 1 - When user selects "None" for fee, show a pop-up message

Screenshot 2 - Change the Claim button to fluro background and white text, to match the button style of "Bridge" on the main site. Should make it look more like a button and would be more consistent

Screenshot 3 - If user selected Recommended and they click "Claim", show pop-up to remind them they should wait for the relayer to auto-claim

Bridge

Describe alternatives you've considered

N/A

Additional context

Happy to help modify them if needed, but I'm sure the UI/UX team will knock it out of the park.

@dionysuzx
Copy link
Collaborator

cc @shadab-taiko @jscriptcoder

@jscriptcoder
Copy link
Contributor

Hi @ablankstory , these are indeed great suggestions. Thanks a lot for your help... We're working on a new design, and these feedbacks are really valuable to us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants