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

pazza notifications at github.com
Mon Jan 24 03:01:48 CET 2022


@chimp1984 thanks for detailing the user journey for creating an offer.

> The idea is to have a process which is easy enough for newbies to follow. Pro traders can choose to get displayed all the steps in one screen to get a faster experience. All sections after protocol selection are optional and context specific to the chosen protocol. In many cases the summary section is shown after the protocol selection.

With regards simplifying the user journeys I wonder if making and taking should be treated slightly differently on the assumption that Bisq newbies are more likely to be takers. Therefore, this process can/should be simplified (also there are less options to choose from as they are essentially filtering the existing offers).

Therefore, if having an easy process for newbies to follow, maybe, it should focus on getting them to take not make an offer.

> An open question is if we should support multiple protocols to be selected for an offer. Power trader will probably like to have this feature but it increases UX complexity quite a bit. Maybe we prepare to support it technically but leave it in the UI with a singe protocol selection, which will likely be the default use case for most users anyway.

I think it would be ok to have only one protocol per offer. Each protocol will likely come with a different security model and would be priced accordingly. I imagine it would get too complex to have price being dependent on multiple variables eg; protocol, payment method, identity chosen etc. Maybe it would be good to define what is likely to be fixed per offer; eg price, protocol, identity?

> ### 1. Asset selection
> ```
> Swap 
> ---------------------------------------------
> From:  [BTC]
> To:    [USD] 
> ---------------------------------------------
> [NEXT >>]
> ---------------------------------------------
> ```

Do you anticipate the following will be possible?
 
```
Swap 
---------------------------------------------
From:  [BTC ] or [XMR] or [ETH] 
To:    [USD] or [EUR] or [GBP] 
---------------------------------------------
[NEXT >>]
---------------------------------------------
```

Would be great if Bisq 2 could allow offers to be created that increased liquidity by having multiple ways a taker could fund them, and allow them to be for multiple currencies. Similar to as proposed in [Proposal to increase liquidity on Bisq by allowing each offer to have multiple payment methods and currencies associated with it.](https://github.com/bisq-network/proposals/issues/288)

> ### 2. Set amount and price
> Here the previous screen expands to show also the input fields for the amounts and the price information, fields and toggle. A advanced option icon enables to enter an amount range as well.
> 
> ```
> Set amount and price
> ---------------------------------------------
> From: 	[  0.01] [BTC]
> @ Rate: [  0.00] % <-> [50 0000] BTC/USD 
> To: 	[   500] [USD] 
> ---------------------------------------------
> [NEXT >>]
> ```

Can a BTC Buyer can come along and say I would like to buy 500 USD of BTC what are the offers available. This would be great but also it would seem to add more challenges. I am not sure what assets will be constants and what assets will be variables, or if all assets will be variables. Probably not explaining myself very well :) It would be great if everything was variable but I would imagine this would not be possible technically?


### 3. Protocol selection

I am assuming one protocol per offer...

Therefore, how I would anticipate the protocol selection is a little different.

I would make this this first choice.

Eg:

1. Choose Buy / Sell
2. Choose protocol

In my imagination both these options would be in the GUI, and are selected prior to beginning to make an offer.

Also, I think it would be a better user experience for the more 'difficult / knowledge based' decisions to be made earlier on in the user journey. Things should get progressively easier not harder :)



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

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


More information about the bisq-github mailing list