Why are empty, loading and error states important, and how do you design them?
What the interviewer wants to hear
- Users see these states often, especially new users
- Empty states should explain and guide to the first action
- Loading states should show progress and keep layout stable
- Errors should explain what happened and how to recover
Model answer
Many designs only show the happy path, but real users meet empty, loading and error states all the time. A new user sees empty screens first, so those states shape first impressions. For empty states I explain what will appear here and give one clear action to get started, like create your first invoice. For loading I use skeleton screens or progress indicators that keep the layout stable, and I show results as they arrive if the wait is long. For errors I write plain messages that say what happened and what to do next, keep the user data, and offer a retry or another path. I design these states as part of the main flow, not afterwards, and include them in the handoff so developers do not have to guess.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium UI/UX Designer questions
- You have only one week to design a new feature. How do you include user research?
- A stakeholder gives feedback on your design that you disagree with. How do you handle it?
- How do you measure whether a design change was successful?
- An engineer says your design will take three times longer to build than planned. What do you do?
- How do you plan and run user interviews for a new feature?
- You are asked to restructure the navigation of a large website with hundreds of pages. How do you approach it?
- A team wants a custom styled dropdown instead of the native select. How do you make sure it is accessible?
- How do you turn research findings into design decisions the team actually acts on?
- How do you run a design critique session that is useful rather than a debate about taste?