We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For a nice and smooth UX, I think we should be showing users skeleton components whenever a component is loading or data is being fetched via API. Right now, when the data is being fetched, a message is shown: "No data available" and then after a few seconds the actual data shows up. IMO, this is not an optimal UX. e.g: https://github.com/thenewboston-developers/thenewboston-Frontend/assets/52558124/9b2b5ec7-0482-4112-9a5b-dcab58ed0108
Skeleton e.g:
Let's do this gradually, one by one:
... will be adding more here, if needed
The text was updated successfully, but these errors were encountered:
MAbdurrehman1
Successfully merging a pull request may close this issue.
For a nice and smooth UX, I think we should be showing users skeleton components whenever a component is loading or data is being fetched via API.
Right now, when the data is being fetched, a message is shown: "No data available" and then after a few seconds the actual data shows up. IMO, this is not an optimal UX.
e.g:
https://github.com/thenewboston-developers/thenewboston-Frontend/assets/52558124/9b2b5ec7-0482-4112-9a5b-dcab58ed0108
Skeleton e.g:
Let's do this gradually, one by one:
... will be adding more here, if needed
The text was updated successfully, but these errors were encountered: