RoboSats
Sort by premium when the order type is defined
Is your feature request related to a problem? Please describe.
The offers tab displays orders without a deterministic sorting and that makes it hard to navigate. I would expect users looking at a better premium more than anything else, then taking a look at the order terms such as bond size, or deposit time.
This is related to https://github.com/RoboSats/robosats/pull/1613, although the proposed change doesn't work because buy and sell orders are mixed when no order type is defined.
In that PR, it is argued that coordinators get a higher change of appearing at the top of the list based on their dev funds donation percentage as a perk, but I don't think that is too beneficial for them, because if the premium is too high (say 20% for buying) people won't even look at it. However, it does make the user experience worse.
I definitely think that coordinators donating more to the developer funds should be recognized, but using badges or other UI "boosts" would be much better.
Describe the solution you'd like
It would be great if the orders were automatically sorted by premium when selecting a BUY or SELL action.
Buy: sort by premium ASC Sell: sort by premium DESC Swap out: sort by premium DESC Swap in: sort by premium ASC
Only if there was no sorting applied yet.
That way, the list is more intuitive and easier to understand, particularly for new users. Cheaper options are shown at the top and there's no need to go through the list or sort it manually.
[!Note] The option to change the sorting should remain as it is right now.
Yup, this was one of the proposals on the PR, maybe we should just apply in the cases the user didn't apply jet any sorting to not confuse them.
I think that we should just re-think the way coordinators get compensated, keep it beneficial but maybe in a more obvious way than just a badge
@KoalaSat Definitely, only as the default sorting and without overwriting pre-existing sorts.
Regarding coordinator compensations I can't think of other than what is currently taken into account: priority on issues/features/support and UI distinction.
Apart from that, it is hard to implement something without functional impact that actually incentivizes users to choose one over the other. And changing functionality/UX based on the donations percentage is not acceptable nor a good idea.
I sent you a DM on nostr with some concerns.
