-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
UI: Empty States #82
Comments
@bartosz-lipinski @bhgames what do you think guys? I can submit a PR for this if we discuss how it should roughly look. Without empty states, the store feels "wrong". Some screens show an infinite-load instead of an empty state, others just look like one can't be sure if it's a bug or it really is empty. This is a major UX need IMHO. |
Yeah I'm down, though the UI design is more @bartosz-lipinski 's territory so I'll leave it to him to decide if he wants an empty state or not. |
yeah 100% empty state will be great. |
@bhgames @bartosz-lipinski how do you want to tackle this? I can prepare a PR. Any guideline for your preferred UI? Or do you want me to give a stab at it the way I see fit and go from there? |
I think this has been done now. |
I'm willing to contribute a PR for these, but I'm opening this to discuss with the team first.
Right now almost nothing has any cohesive empty states, which feels like bad UX. Here's some reading material:
https://marvelapp.com/blog/empty-state-most-overlooked-aspect-of-ux-design/
https://uxdesign.cc/the-importance-of-the-empty-state-in-your-app-8b7f3921e0aa
This is a partial list of areas where empty states would be beneficial:
Ideally a good empty state would not "feel" like an error (right now some of those screens go to infinite loading mode upon an empty state) and would provide a call for action to change the state from empty (given the right state of authentication with the wallet).
The text was updated successfully, but these errors were encountered: