- What copy should designers use for an empty state component when the default
no datadoes not accurately describe the empty state?
- How can designers maintain consistent messaging when they change empty state component copy for their use case?
List of options
- Option 1: Select appropriate empty state copy from a content library when default copy does not apply.
- Option 2: Keep using the default
no datacopy for all instances of the empty state component.
- end users would find specific empty state copy more useful than "no data"
- designers can maintain message consistency by choosing from a content library
- designers have clarity when deciding on what copy to use for their empty state use case
- maintaining a content library will take time and energy
- the library may become stale and unusable as designers stop evolving it
- changing the empty component copy per instance will take more time and energy than using the default copy
Option 2: Keep using the default
no data copy for all instances of the empty state component.#
- consistent messaging in the empty state with no added effort from design and development
- poor ux for end users in certain use cases where
no datadoes not apply
- designers lose a valuable messaging space to provide direction and clarity to their end users in particular user flows
Option 1. The added effort of maintaining the content library and changing the empty state content copy per use case is not significant when compared to the added ux value better copy provides to end users.
How the content library will work:
- The library will be housed within the empty state component usage docs.
- Content will be added to the library after being vetted by the design circle.