What Is UX Writing and Why Interface Text Matters
Basics4 minInnovialabs editorial team
In short
UX writing is designing the words inside an interface: buttons, labels, hints, errors, empty states and onboarding. Good microcopy is clear, short and consistent in tone, and it helps people complete tasks without guessing what to do next.
What UX writing is
UX writing is the work of choosing the words people see while using a product. These short texts are called microcopy: button labels, form hints, error messages, confirmations, empty states, notifications and onboarding screens.
Interface text is not decoration added at the end. Users read words before they interpret icons and layout. If a button says "Submit" and the user does not know what will happen, the design has failed regardless of how it looks. That is why UX writing works best when text is designed together with screens, not pasted in after.
Where microcopy does the most work
| Place | Job of the text | What to watch |
|---|---|---|
| Buttons | Say what will happen | Use a verb and the object: "Save changes", "Book a visit" |
| Form labels and hints | Explain what to enter and why | Format examples, why data is needed |
| Errors | Explain what went wrong and how to fix it | No blame, no codes without explanation |
| Empty states | Explain why the screen is empty and what to do | A clear next action |
| Confirmations | Prevent accidental, irreversible actions | Name the consequence |
| Onboarding | Show value and the first step | Brief, skippable, focused on the user's goal |
| Notifications | Report what changed | Specific, timely, not alarming without reason |
Core principles
- Clarity first. Use familiar words, not internal jargon. "Payment failed" is clearer than "Transaction declined by acquirer".
- Brevity. Cut words that do not help the user act. Short does not mean cryptic: a slightly longer, clear sentence beats a vague short one.
- Useful. Every text answers a user question: what is this, what happens next, what should I do.
- Consistency. One action, one name. If it is "Cart" on one screen, it should not be "Basket" on another. Keep a short glossary.
- Tone. Friendly and calm, matching the brand and the moment. Jokes in an error about a failed payment irritate.
- Front-load the key information. People scan; the first words should carry the meaning.
- Accessibility. Text must make sense without colour or icons, and link and button labels should be meaningful when read out of context by a screen reader.
Before and after
| Situation | Before | After |
|---|---|---|
| Button on a booking form | Submit | Book a visit |
| Password error | Invalid input | Password needs at least 8 characters |
| Generic failure | Error 500 | We could not save your changes. Check your connection and try again |
| Empty orders list | No data | You have no orders yet. Browse the catalogue to place your first one |
| Delete confirmation | Are you sure? Yes / No | Delete this project? All files in it will be removed. Delete / Cancel |
| Phone field hint | Enter phone | Phone number, for example +998 90 123 45 67. We will call to confirm |
Notice the pattern: the "after" versions name the action or the problem, explain the consequence, and give a next step.
How to write microcopy in practice
- Start from the user's question at that moment: "What will this button do?", "Why did it fail?"
- Write a first draft fully, then cut everything that does not help.
- Read it in context on the actual screen, at real size, on a phone.
- Check consistency with the glossary and other screens.
- Plan for translation. In multilingual products text length changes between languages; leave room in the layout and avoid words glued to icons or numbers.
- Test it. Watch users in usability sessions: hesitation on a button often means a wording problem.
Common mistakes
- Placeholder text left in production: "Lorem ipsum", "Button", "Text here".
- Error messages that blame the user or show technical codes only.
- Hints placed inside fields that disappear when the user starts typing.
- Generic buttons such as "OK" and "Submit" for important actions.
- Different names for the same thing across the product.