[bisq-network/bisq] Bisq-2 UX challenges (Discussion #5959)

chimp1984 notifications at github.com
Sun Jan 23 18:37:48 CET 2022


Here an update of my current prototype:
<img width="1321" alt="Screenshot 2022-01-23 at 12 31 31" src="https://user-images.githubusercontent.com/54558767/150690522-23f2e76a-40ee-498c-8c97-41d4f8434bcb.png">
<img width="1323" alt="Screenshot 2022-01-23 at 12 31 39" src="https://user-images.githubusercontent.com/54558767/150690529-204f04be-4de1-44fd-829f-9949777665aa.png">

Instead of settlement methods it will be the user settlement accounts. If the user has none yet setup they can add one...

I tend to not support multiple protocols as that makes UX much more complex.
I will probably still support it in the domain so it can be added later, but I guess the extra costs on UX and dev effort do not justify the benefits (likely only used by some pro traders). A trader can publish multiple offers with diff. protocols. The extra cost for reserving BTC for an offer will likely be not present in Bisq 2 anyway and if still its only for the MultiSig based protocol.
But we plan the improve the MultiSig based protocol as well with the ideas around the one-tx protocol proposals...
 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5959#discussioncomment-2028354
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/repo-discussions/5959/comments/2028354 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220123/3dd25ec3/attachment.htm>


More information about the bisq-github mailing list