We need to improve the overall empty states wherever applicable for across all dapps. Fill spaces when no content has been added yet, or is temporarily empty due to the nature of the feature and should be designed to prevent confusion.
When designed thoughtfully, empty states become an essential part of a smooth user experience, providing enough context to keep users working in a productive way. There are several approaches to explore that will match the needs a developer in different situations:
Blank Slate - Basic empty state for first run experience
Informational - Alternative for first use empty state, including in-line CTAs and supplemental documentation links
Educational - Launch a contextual onboarding flow to gain deeper understanding about that area of the app
Guide - Starter content that allows users to interact with data and learn the system by tinkering or setting up their environment
Description
We need to improve the overall empty states wherever applicable for across all dapps. Fill spaces when no content has been added yet, or is temporarily empty due to the nature of the feature and should be designed to prevent confusion.
Reference:
Empty State Design Framework