-
Notifications
You must be signed in to change notification settings - Fork 70
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
Improve completed screen at the trade process #1186
Comments
Following up with my last PR (on the Bisq Easy waiting states icons), I think I can work on this. |
See discussion at #1349 (comment) |
From discussion at #1349 I've created these mock-ups for the final step of the trade process for both seller and buyer. For the seller: For the buyer: @HenrikJannsen |
Looks great! Is it intended to be shown only on the right side or over the whole available width (hiding the left stepper box)? |
The idea is the latter. |
Maybe instead the fees we could show how long the trade took? We would like to add a feedback feature. Only to the peer as we dont know how to do that decentralized/secure. But I think it would be still nice to have the option to send and receive feedback from the peer (some simple with stars and a text msg and maybe some emoticons). But can be delegated for later as well. |
Yes that could be included. Why do you think this is important?
You mean in the buyer? I thought the buyer wouldn't care for a fee that he didn't pay, but could be included as well.
To the peer do you mean to the buyer? |
I think the trade duration is an important factor, but not sure how important. To keep all to the minimum is maybe better. We should avoid information overload.
For both, but true for the buyer its less important and the seller will know it anyway. Again maybe better to keep all to the minimum.
Both sides. Yes was meant as button which shows a new screen/popup for giving feedback. But I think that can be delegated for post-launch. |
The completed screen could need more love...
The text was updated successfully, but these errors were encountered: