Article5 min readUpdated
UX Writing and Microcopy for Apps: Before and After Examples
UX writing for Indian apps: microcopy examples for OTP, UPI and KYC screens, with before and after rewrites for buttons, errors and empty states.
By Tithi Mondal, UI/UX Designer
The words inside your app are part of the design. A user who hits a failed UPI payment does not read your brand story. They read one line and decide whether to try again or give up. UX writing is the work of making those lines clear. This post shows the principles and then real before and after examples from Indian app situations: OTP, UPI and KYC.
What microcopy does
Microcopy is the small text in an interface: button labels, form hints, error messages, empty states, confirmation lines and notifications. Individually they are tiny. Together they decide whether an app feels clear or confusing.
Good app copywriting does three jobs. It tells people where they are, what to do next, and what will happen when they do it. It also keeps a steady voice. For most products aimed at Indian founders' customers, that voice should be friendly, respectful and direct.
The principles I use
- Use plain language. Write the way you would explain it to a neighbour. "Enter the 6-digit code we sent" beats "Authenticate using the one-time credential".
- Be specific. Name the thing. "Enter your 10-digit mobile number" beats "Invalid input".
- Lead with what the user can do. Put the action first, the explanation second.
- Keep it short, but not cryptic. Cut filler, not meaning.
- Do not blame the user. "That OTP does not match" is better than "You entered the wrong OTP".
- Use the same word for the same thing. Do not call it "Wallet" on one screen and "Balance" on the next.
- Match the user's language. Plain English or the regional language they chose. See regional language app design.
Button text that names the action
A button should say what happens when it is tapped. Generic labels like "Submit" and "OK" force people to guess.
- "Submit" becomes "Pay ₹499" or "Place order".
- "Continue" can stay when the next step is obvious, but "Verify mobile number" is clearer on a sign-up screen.
- "Yes" and "No" in a dialog become "Cancel booking" and "Keep booking".
- A destructive action should look and sound different from a safe one.
Before and after: Indian app situations
The table below shows rewrites from common screens. These are examples of the approach, not text from any particular app.
| Situation | Before | After |
|---|---|---|
| OTP entry | Enter OTP | Enter the 6-digit code sent to +91 98XXXXXX10 |
| OTP wrong | Invalid OTP | That code does not match. Check the SMS and try again. |
| OTP not received | OTP failed | Did not get the code? You can ask for a new one in 30 seconds. |
| UPI pending | Transaction error | Your payment is still being checked. If money was deducted, it will be refunded or confirmed soon. Do not pay again yet. |
| UPI failed | Payment failed. Try again later. | Payment did not go through. No money has been taken. Try again or choose another way to pay. |
| KYC upload | Upload document | Upload a clear photo of your PAN card. All four corners should be visible. |
| KYC rejected | KYC rejected | We could not read your PAN photo. Please upload it again in good light. |
| Empty orders | No data | You have no orders yet. Browse the menu to place your first one. |
| Network error | Error 500 | No internet right now. Your details are saved. Tap Retry when you are back online. |
Notice what changed. Each "after" says what happened, whether money or data is safe, and what to do next.
Money and trust screens deserve extra care
Anywhere money, identity or personal data is involved, vague text creates fear. Three rules help.
- State the money status first. Was money taken, held or refunded? Users want this answer before anything else.
- Give a time frame only if it is true. Do not write "within 5 minutes" unless the system can promise it. Say "usually" or point to where they can check.
- Explain why you need sensitive information. A short line like "We ask for your PAN to verify your account" reduces drop-off more than a long policy link. Keep it honest and brief.
On a fintech product, the KYC flow is where clear words matter most, because people are already nervous about sharing documents. I like to draft screen text along with the wireframes rather than leaving it for the end, and fintech flows are where that pays off most.
Error messages: a simple formula
A good error message has three parts.
- What happened, in plain words.
- Why, if it helps the user.
- What to do next, as a button or a clear step.
Example: "We could not send the code. The mobile number may be wrong. Check the number and tap Send again."
Place the message next to the problem, such as under the field, not only in a pop-up that disappears. Keep the user's typed data in place.
Tone, humour and politeness
Keep a calm tone for serious moments. Jokes in a failed payment screen are risky. A little warmth is welcome in success and empty states, such as a short "Your first order is on its way".
Be careful with local idioms and slang. They can feel natural to one region and strange to another. If your users span many states, choose simple words that travel well.
Test your words
Read the screen aloud. If you stumble, rewrite. Show the screen to someone outside your team for five seconds and ask what they would do next. If they hesitate, the copy needs work.
Keep a simple word list in your design file: the names of features, the tone rules and the button patterns. It saves arguments later and keeps the voice steady as the team grows. See also how this ties into the mobile app design process, where text is drafted at the wireframe stage.
If you want help with the screens and the words together, see my UI/UX design service or send me a note.
Frequently asked questions
What is the difference between UX writing and copywriting?
Copywriting usually sells or persuades, as in ads and landing pages. UX writing helps people finish tasks inside a product, so it is short, clear and tied to the screen.
How long should a button label be?
Usually one to three words, starting with a verb, such as Pay now or Verify number. If it needs more words, the screen may need a clearer title instead.
Should error messages apologise?
Only when the fault is yours, and briefly. Most users want to know what happened and what to do next, more than they want an apology.
Who should write the text in an app, the designer or a writer?
Ideally the designer drafts it with the screens, and a writer or the product owner refines it. Writing text late, after the layout is fixed, causes broken layouts and unclear screens.