Empty state
Todo: define the differences in each of the below and have clear design guidelines
Onboarding Empty States
Purpose: Introduce new users and help them take the first meaningful action.
Design focus: Clarity, motivation, and next-step CTAs (e.g., setup guides, tooltips, quick-start wizards).
System / No Data Empty States
Purpose: Occur when the system has no data to show (e.g., new account, filtered-out view, or data hasn’t arrived yet).
Design focus: Neutral tone, explain why it’s empty, and suggest next steps.
Placeholder skeletal loading Empty States
Purpose: Temporarily fill an area while content loads or before it’s customized.
Design focus: Reduce perceived loading time, maintain layout stability.
No Access / Permission Empty States
Purpose: Inform users they don’t have the required permissions or their plan doesn’t include access.
Design focus: Transparency, clear rationale, upgrade or request-access CTA.
Error Empty States
Purpose: Communicate issues preventing data from showing — usually transient or recoverable.
Design focus: Empathy, retry option, diagnostics or support link.
Filter / Search Empty States (Often Overlaps with System)
Purpose: Triggered when a user applies filters or search queries that yield no results.
Design focus: Helpful suggestions or “clear filters” actions.
Success or Completion Empty States
Purpose: Not technically “empty,” but sometimes used when a process is done (e.g., task completed).
Design focus: Positive reinforcement, sometimes prompts next action.
Simple Example
Stick to your structure
Tell Funnel about your conventions and we’ll tell you how well your data follows them.
