You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
relayer will auto-claim if fee is set to Recommended
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
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.
The text was updated successfully, but these errors were encountered:
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
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:
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
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.
The text was updated successfully, but these errors were encountered: