wearenewt / config.fyi Goto Github PK

Column names on the web can get stretched and get close to one another

Estimate: 1 week of work

Details:
Add a feature with urls like this: config.fyi/aavev2/avalanche, for easier linking for specific markets and specific protocols

When selecting AAVE v3 on laptop sized screen (16' macbook in my case) the scaling of this protocol is not consistent with AAVE v2. the right side is cut out and can be side scrolled, however this does not look good from a user perspective.

V3 Scaling:

V2 Correct scaling:

This should be the default page on load:

As seen below, switching between markets can take up to few seconds (seen cases of longer than 15 seconds) and user experience might be compromised because of that since there is no good indication on when the new information is populated other than a brief refresh that's easily missed.

Two solutions come to mind:

1. Improve speed.
2. Make it obvious to the user that the data is being fetched i.e loading icon presented to user instead of "old data" from previous market.
   

Estimation: 1 week of work

Details: allowing for modularity of more protocols to be added to config.fyi UI (similar implementation as DeFi Llama)

ID is available in reserve object from UiPoolDataProvider, just need to copy the mapping from id to category label from aave/interface.

Right now, a user needs to select 'all' under 'market' in order to see the call to action "want to see config for another protocol? contribute to the github"

What we want:
the call to action comes up also when user just picks Uniswap and not the "all" in the dropdown

When user selects protocol and market and then clicks on the "more info" link, and then goes back to the config.fyi app the previous protocol and market selection are not caches which forces user to select again.

Not a big problem but would be a nic QOL if we could get that done

When selecting i.e Avalanche on AAVE V2 protocol and then switching the protocol to AAVE V3, the Avax market stays selected in the dropdown but the site does not populate with the right information, on top of that to see the avalanche market in this scenario, user needs to first select a different market and then go back to avalanche in the dropdown.