[bisq-network/bisq-desktop] Mobile notifications UI (#1622)

Manfred Karrer notifications at github.com
Tue Aug 14 12:48:01 UTC 2018


Before doing the PR I wanted to share the current UI and text string for the mobile notifications integration in Bisq. 

There are different notification types:
- My offer gets taken
- Trade state change (e.g. peer clicked payment sent button )
- Dispute messages (no content of msg, just notification that a new dispute msg arrived)
- Market alerts (if offer matching criteria gets published in offerbook)
- Price alerts (if price is above or below my trigger prices)

Market alerts are set up by payment methods, offer type (buy/sell) and trigger price in % (market based offer price). The offer type is the opposite of what the user is interested in, e.g. if I want to buy BTC I am interested in sell offers. If anyone has suggestions for UI improvements here, please share, its a common problem how to deal with that.
The trigger price is in % and independent if offer use % or fixed price. The alert gets triggered if any offer matching my payment account, offer type and price is broadcasted. You get only once an alert but if an offer is edited with a diff. price you will get it again if it is in the price target. The prices for fiat and altcoins are in diff. direction (e.g. if fiat is higher its better for seller, if altcoin is higher its better for buyer). So there is a bit of complexity how to display that all....

I am not happy with the wording for explaining the triggering price for the market price alert. 

Here is the text I use now (displayed on rollover at info icon):
Receive alerts if an offer gets published with a price better than the set percentage distance to the market price. E.g. If you are interested in 'buy BTC offers' (you want to sell BTC) and you set the triggering offer price to 1.5 % you will receive an alert when a new offer gets published with an offer price of 1.5 % below market price of higher (e.g. 1% or 0.5%).

The label and prompt text for the trigger price is also not really good:
<img width="1009" alt="screen shot 2018-08-13 at 23 59 16" src="https://user-images.githubusercontent.com/1449498/44092217-11dc7254-9fd0-11e8-907b-e7ca79b10b31.png">

Here are screenshots of the relevant market price alert screens:

<img width="1205" alt="screen shot 2018-08-14 at 14 35 08" src="https://user-images.githubusercontent.com/1449498/44092113-c9ccca54-9fcf-11e8-8d97-e58030430e6a.png">
<img width="1201" alt="screen shot 2018-08-14 at 14 35 28" src="https://user-images.githubusercontent.com/1449498/44092121-cdbde986-9fcf-11e8-9cea-67edeaf812a7.png">
<img width="1547" alt="screen shot 2018-08-14 at 14 35 45" src="https://user-images.githubusercontent.com/1449498/44092122-cf000dec-9fcf-11e8-9778-885f5eec127d.png">


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-desktop/issues/1622
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180814/cac896a2/attachment.html>


More information about the bisq-github mailing list