Loading Designed
What the screen shows while waiting, so it does not look broken.
Web App UX Design
Web App UX Design for the States Nobody Draws
Application designs are drawn in one state: loaded, populated, and everything working. Real use includes loading, empty, partially failed, offline and error — and those states are where users get confused. Web app UX design means designing all of them rather than leaving them to whatever the framework does.
We Design Every State, Not the Happy One
The states left undesigned are the ones users encounter when something matters.
Empty States
Every list and table before it has anything in it.
Errors Explained
What failed and what to do, not a generic apology.
Partial Failure Handled
When one part of a screen loads and another does not.
Unsaved Work Protected
Because losing input is the fastest way to lose a user.
Web App UX, Explained
Which States Get Skipped?
Four, and all four appear in ordinary use.
Discuss Your App →- 1
Loading
A blank area, or a spinner with no indication of what is coming.
- 2
Empty
A table with no rows and nothing explaining why or what to do.
- 3
Error
A message that names a failure without naming a remedy.
- 4
Partial
Half the page loaded, half not, and no indication which is which.
What Web App UX Work Covers
The full state matrix, plus the interaction patterns that hold it together.
The build is covered by web application development.
How We Design Web Apps
Enumerate the states per view, then design each one.
List the Views
Every screen the application has.
Enumerate States
Loading, empty, error, partial and populated for each.
Design Them
Including what the user should do in each.
Standardise
Consistent patterns rather than per-screen invention.
Test on Bad Connections
Where the skipped states actually appear.
States
Why the Error State Is the Least Designed and Most Read
Users read error messages with more attention than anything else on the screen, and they are usually written last.
What makes an error message useful?
Saying what failed, why if it is knowable, and what the person can do next. "Something went wrong" satisfies none of those.
It should also distinguish between what the user can fix — a field, a permission, a connection — and what they cannot, where the useful advice is to retry or contact someone.
These messages get read carefully, because the user is stuck. That makes them the highest-attention text in the application and the last thing anyone writes deliberately.
Why does partial failure confuse people?
Because the screen looks like it worked. Most of the page is populated, one section is empty, and there is nothing distinguishing "no data" from "failed to load".
The user draws the wrong conclusion — that there is nothing there — and acts on incomplete information without knowing it.
Marking a failed region as failed, rather than letting it render as empty, is a small change and it is the difference between an inconvenience and a wrong decision.
Questions,answered.
Web app UX design covers the experience inside a web application, including the states most designs skip — loading, empty, error, partial and offline — alongside navigation, forms and feedback.
Because designs are drawn in the populated, working state and reviewed with good data on a fast connection. The other states are then left to whatever the framework produces by default.
Saying what failed, why if knowable, and what to do next. Error text is the highest-attention writing in an application because the user is stuck, and it is usually written last.
Marked as failed rather than rendered as empty. A section that failed to load but looks like "no data" causes users to act on incomplete information without knowing it.
Depends on the use case, but unsaved work should survive a connection drop regardless. Losing input is one of the fastest ways to lose a user's trust in an application.
Still deciding if web app ux design is right for you?
Talk to UsThe Design Had One State
Application interfaces get designed populated: realistic data, everything loaded, nothing failing. It is the state that photographs well and the state the team looks at for months.
Then it ships, and users encounter the version where the connection is slow, the list is empty, one panel failed and the error says something went wrong.
Nobody designed any of that. It is whatever the framework does by default, and it is a substantial fraction of what people actually see.
Free UX Review
See Your App in Its Other States
Give us access to your application. We will look at it empty, loading, offline and failing, and tell you what a user makes of it.
Claim Your Free Marketing Audit
Enhance Your Brand Potential At No Cost!
- Expect a response within 24 hours
- NDA available upon request
- Dedicated product specialists