Guide7 min readUpdated
Form Design Best Practices for Signup and Checkout
Form design best practices for Indian apps: labels, field order, keyboards, inline validation and clear error messages, with exact examples.
Imagine a tiffin service in Durgapur that wants customers to sign up before ordering. The first version of the form has 9 fields, placeholder text instead of labels, and a red message that says "Invalid input" when something goes wrong. Half the people who start the form leave. This guide shows how to fix a form like that, field by field. These are the form design best practices I apply on every product.
Delete fields before you design them
Every field costs attention. On a mid-range Android phone with a weak network, every field also costs patience.
Ask one question for each field: "What will we do with this answer in the next 7 days?" If the answer is "nothing yet", remove the field. You can ask for it later, once the person trusts you.
For a tiffin signup, the real needs are:
- Mobile number (to send the OTP, the one time password)
- Name
- Delivery address, but only at the first order, not at signup
That is a 2 field signup form. Address belongs to checkout. Splitting one long form into two short moments is often better than one long form. I covered the same idea for first-run screens in app onboarding UX best practices.
Labels go above the field and stay visible
Placeholder text is the grey hint inside an empty field. It disappears the moment the user types. A person who looks away, then comes back, no longer knows what the field wanted.
Do this:
- Put a short label above each field: "Mobile number", "Full name".
- Use the placeholder only for an example: "98765 43210".
- Keep the label visible while the user types.
Do not do this:
- Do not use the placeholder as the only label.
- Do not use a label like "Enter your details here".
- Do not set label text in light grey. Labels need strong contrast so people with weak eyesight can read them. My accessibility guide explains the contrast rule in plain terms.
Mark the exception, not the rule. If most fields are required, mark the optional ones with "(optional)" after the label. A red star on every field adds noise.
Put fields in the order people think
People answer in the order they would tell a friend. They say who they are, then how to reach them, then where to deliver.
A good order for a delivery form:
- Full name
- Mobile number
- PIN code
- House number and street
- Landmark (optional)
Notice that PIN code comes before the street. Once a person types a 6 digit PIN code, you can fill in the city and state for them. That saves two fields and removes spelling mistakes.
Use a single column. Two fields side by side look tidy on a laptop, but on a phone they force the eye to jump. Keep a pair on one row only when they are tiny and obviously related, such as the PIN code and a "Check" button.
Match the keyboard to the field
The wrong keyboard is one of the most common form mistakes I see. A person typing a mobile number should see a number pad. Not the full letter keyboard.
| Field | Keyboard to open | Extra help |
|---|---|---|
| Mobile number | Number pad | Show "+91" as fixed text before the field |
| PIN code | Number pad | Limit to 6 digits |
| Email keyboard (shows the @ key) | Turn off auto capital letters | |
| Name | Letter keyboard | Capitalise the first letter of each word |
| OTP | Number pad | One field, auto-read the SMS if the platform allows it |
| PAN | Letter keyboard | Capitals, 10 characters |
Your developer sets these with the input type and input mode of each field. As a designer, I write the keyboard type next to every field in the Figma handoff, so nothing is left to guess. My Figma developer handoff checklist has a line for this.
Indian formats: mobile, PIN code, PAN and GSTIN
Indian products need fields that respect local formats. Here is what I design.
Mobile number. It has 10 digits. Show "+91" as fixed text outside the typing area, so people do not type it twice. Accept a space after the 5th digit, and remove spaces yourself. Do not make people type the number again in a special pattern.
PIN code. The Postal Index Number has 6 digits. Use a number pad. When 6 digits are entered, look up the area and show it as plain text: "Kolkata, West Bengal". Let the user edit it if the lookup is wrong, because some areas share a PIN code.
PAN. The Permanent Account Number is a 10 character code made of letters and numbers in a fixed pattern. Convert what the user types to capital letters automatically. Do not shout at them for typing small letters. Show the pattern once under the field: "Example: ABCDE1234F".
GSTIN. The Goods and Services Tax Identification Number is a 15 character code. People copy it from an invoice, so allow pasting and remove spaces before you check it. Make the field optional unless your business truly needs it, because many small buyers do not have one.
Two rules apply to all of these. Check the format on the user's device before sending. And never reject a correct number because of a formatting habit, such as a space or a small letter. Fintech products need these fields most.
Inline validation and form validation messages
Inline validation means checking a field while the person fills the form, not only when they press the button.
The timing matters:
- Check a field after the user leaves it, not on every key press. Nobody likes a red error while they are still typing the 3rd digit of 10.
- Once an error appears, remove it as soon as the value becomes correct.
- Show a small green tick only when it helps, such as "Username is available".
- On submit, move the screen to the first error and place focus in that field.
Now the wording. A good form validation message does three things: it says which field, what is wrong, and how to fix it.
| Do not write | Write instead |
|---|---|
| Invalid input | Enter a 10 digit mobile number |
| Error in PIN | PIN code must have 6 digits. You entered 5. |
| Wrong format | Email needs an @ sign, for example name@gmail.com |
| Field required | Please enter your full name |
| Password too weak | Add 2 more characters. Use at least 8. |
Put the message directly under the field, in a dark red with an icon, so it does not depend on colour alone. Keep it in the same language as the form. For readers who prefer Bengali or Hindi, see regional language app design.
Never clear the form after an error. Losing typed data is the fastest way to lose a customer.
Mobile form design for mid-range phones
Most Indian traffic comes from mobile, and many phones have small screens and slow connections. A few rules help a lot:
- Make each field at least 48 pixels tall, so a thumb can hit it.
- - Keep the main button visible above the keyboard. When the keyboard opens, it covers half the screen, so scroll the active field into view.
- Allow autofill for name, phone and address. Do not block pasting.
- Save the draft. If the network drops at field 6, the person should return to field 6.
Test the form on a real phone, not only in a Figma preview. Open it with the keyboard up and ask: can I still see the field and the button? A small test with 5 people is enough to find the worst problems, and my guide to usability testing on a small budget shows how to run one.
The button and the moment after it
Name the button after the result. "Create account" and "Place order" are better than "Submit". Disable it only when no action is possible, and prefer showing an error to a button that is simply grey and silent.
After the form is sent, say what happens next: "We sent a 6 digit code to 98765 43210. It arrives within a minute." Add a "Resend code" link that appears after 30 seconds. A form that goes quiet after pressing the button feels broken.
If your signup or checkout form needs a clean-up, I look at forms as part of UI/UX design for apps and websites, and you can send me the screens through the contact section.
Frequently asked questions
How many fields should a signup form have?
+
As few as you can. Ask only for what you need to start, which is often a mobile number and a name. Ask for everything else later, when the person has a reason to give it.
Should I use placeholder text as a label?
+
No. Placeholder text disappears when the user types, so they forget what the field wanted. Use a visible label above the field and keep the placeholder for an example.
When should a form show an error message?
+
Show it after the user leaves the field, not while they are still typing. Remove it as soon as the value is correct.
How do I design a mobile number field for India?
+
Show +91 as fixed text, open a number pad, accept 10 digits, and remove spaces automatically. Tell the user exactly what is wrong if the number is too short or too long.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.