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

New selection criteria for the Liquidity Pools section of the dApp is too narrow in scope #3030

Open
o0j4yj4y0o opened this issue Nov 22, 2023 · 0 comments

Comments

@o0j4yj4y0o
Copy link

o0j4yj4y0o commented Nov 22, 2023

Is your feature request related to a problem? Please describe.
The new, consolidated UX looks fantastic and overall, I love it. That said, the Liquidity Pool section is very aggressive with its filter and has, in my opinion, largely neutered its utility.

image

We now have three pools shown, one is POL and another is liquidity in Tokemak that's not really relevant to what's happening today (It just got put there 'cause it looks like we filter by top TVL). All the Arb One pools aren't even shown nor are they selectable as a chain. Last, we have a link that directs the user to go to another site (Not our own) to find what they're looking for.

Recommendations:

  • Make the default display and row selection 10 and empower the user to electively change their preference rather than taking the choice away.
  • If the goal is to manage real-estate on the infinite scroll or above the fold, use more of the filter buttons at the top and again, empower the user to pick what they want to see. The obvious one that's missing from the old filter is Arbitrum One. It doesn't exist. I even tried changing my connected wallet to that chain to see if maybe that made it show up but, no dice, it's just missing. Ideally we would show a selectable filter for any chain that has OHM/gOHM liquidity on it. We already have the data from the API so if a person wants to click Polygon and Avalanche, they should get what's there. This will let the tool grow as we scale out and give choice and autonomy to the user.
  • Wack the Explore More button and just let the 'View Details' button do the lift. If we fix our filtering problem, a user should be able to find all the things of interest right here and then drill down as needed. Ultimately we want to keep them on our site, even if it's using iFrames and API calls to source data. A catch all that redirects almost admits a deficiency in the data and says, "You can go here. It's where we're getting to from anyway."

Otherwise, love the new design and excited to see it grow!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant