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

Improve offer confirmation dialogue #1225

Closed
ripcurlx opened this issue Jan 18, 2018 · 7 comments
Closed

Improve offer confirmation dialogue #1225

ripcurlx opened this issue Jan 18, 2018 · 7 comments
Assignees

Comments

@ripcurlx
Copy link
Member

Maybe we could structure it more like:
You are selling
1.00 BTC
@ 7,487.61 AUD per BTC
(auto adapts to 1% distance from market price)
Payment method: OKPay ("OKPay dummy")
Total: 7,487.61 AUD

(I'm confused again what Price and Amount to spend means again for the user)

Similar to the the Take Offer screen, this is one of our most important screens and should be super clear and easy to digest and confirm.
I also think we should add the fees (Bisq trading and mining fees) to this popup to be as transparent as possible what the user will have to pay for doing a transaction on Bisq.

Create offer to sell - step 8.png

@tr37ion
Copy link

tr37ion commented Jan 18, 2018

Make descriptions more personal like 'Your offer ID:' instead of 'Offer ID'. Changes like this make entries more prominent and easier to understand.

@ripcurlx
Copy link
Member Author

Also using Your onion address or if I'm not the "maker" Seller's/Buyer's onion address would be more easy to grasp.

@tr37ion
Copy link

tr37ion commented Jan 18, 2018

I kind of feel technical terms like maker/taker might be good for a professional trading platform and pro traders know those terms, but with Bisq trading should be a bit more relaxed and using simple language flattens the learning curve a lot.

@ripcurlx ripcurlx self-assigned this Dec 18, 2018
@stale
Copy link

stale bot commented Mar 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Mar 18, 2019
@ripcurlx
Copy link
Member Author

Still relevant

@stale stale bot removed the was:dropped label Mar 18, 2019
@stale
Copy link

stale bot commented Jun 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Jun 16, 2019
@stale
Copy link

stale bot commented Jun 23, 2019

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants