Communication & UX
Telling people what happened, and what to do next.
Most software that feels broken simply failed to say anything. Every action has four states — idle, loading, success, failure — and each one needs a visible response.
The state switcher shows the same form across all four states. The rewrite panel shows the same error message before and after a plain-language edit. Both are things you can ship today.
Visual walkthrough
Drag through the life of one click
Nothing has happened yet — the button says what it will do.
One clear verb beats “Submit”.
Interactive demo
The four states of every action
Alex
Product team
No messages yet. Type one below and send it.
The rewrite gallery
What makes this work
The pieces underneath
Try it
10 minPick any screen you have built. Write out all four states out loud — what the user sees at idle, loading, success, and error. Then ask your builder to implement the two you are currently missing.
- Rewrite one error message so it names the fix instead of the fault.
- Replace one 'Submit' label with the actual outcome, like 'Send message'.
Free account
Save your progress and earn your certificate
Keep reading as long as you like — everything here stays open. Add your email and we will track your completion, sync it across devices, and issue your Vibe Coding micro-credential when you finish.
Just enter your email. We will send you a link — no password needed.