Article6 min readUpdated
Login Screen Design: Mobile Number, OTP and Sign Up
Login screen design for Indian apps: the elements in order, exact OTP wording, resend timer rules, every error state and the mistakes that lose users.
Imagine a first-time user in Siliguri who opens your app on a mid-range Android phone with a weak network. She types her mobile number, waits for an SMS, switches apps to read it, loses her typed number, and gives up. Login screen design is the work of making that moment short and forgiving. A login screen is the screen where a returning person proves who they are so the app can open their account.
This article covers the login and OTP flow only. For what comes after the first login, read app onboarding UX best practices.
What must a login screen do?
A login screen must get the user into the app with the fewest taps, and it must never leave them stuck. Three jobs matter most.
- Identify the person with one field, usually a mobile number.
- Prove it is really them, usually with a one time password (OTP) sent by SMS.
- Handle every failure with a plain message and a next step.
In India a mobile number login is the natural choice. Almost every user has a number, many do not use email daily, and typing a 10 digit number is easier than choosing a password. A password can stay as a small secondary option.
What goes on the login screen, from top to bottom?
The login screen has six elements, and the order matters because people read from the top and the thumb works near the bottom. Here is the order I use.
- Logo and one line of purpose. Keep it small. Example: "Order fresh vegetables from your local farm."
- Heading. "Enter your mobile number".
- Phone field. A fixed "+91" prefix, a flag only if you serve other countries, and a numeric keypad that opens by itself. Placeholder: "10 digit mobile number".
- Helper line. "We will send a 4 digit code by SMS. Standard rates may apply."
- Primary button. "Get OTP". It stays grey until 10 digits are typed.
- Footer. "By continuing you accept our Terms and Privacy Policy", with both words as links.
Put the field high enough that the keypad does not cover the button. On small phones, test with the keypad open. If the button hides, the whole flow fails for that user.
If you offer Google or other social login, place it below the mobile number option as a quiet text button. The phone number stays the main path. For more on field rules, see form design best practices.
How should the OTP screen work?
The OTP screen must make the code easy to receive, easy to enter and easy to request again. The OTP screen UI has its own order.
- Back arrow. So the user can fix a wrong number.
- Heading. "Enter the code".
- Sentence with the number. "We sent a code to +91 98765 43210." Add a "Change number" link beside it.
- Code boxes. 4 or 6 boxes with a numeric keypad. Where the phone allows it, read the code from the SMS and fill the boxes automatically. Also allow pasting the whole code at once.
- Resend timer. Described below.
- Verify button. If the boxes fill automatically, verify without a tap and show a short loading state.
How does a resend OTP timer work?
A resend OTP timer blocks the resend button for about 30 seconds and shows the countdown in words. Without it, anxious users tap "Resend" five times and receive five codes, and then enter the wrong one.
- While waiting: "Resend code in 0:28" in grey text.
- When finished: "Resend code" as a clear text button.
- After 2 or 3 resends: add "Get the code on a call" or "Get the code on WhatsApp", only if your team supports it.
Never restart the timer when the user only goes back and forth between screens. Keep the time running in the background.
What are all the states of the login flow?
Every screen has states, and login has more than most. Plan them before you draw the happy path. For the general method, see empty, loading and error screens.
| State | What the user sees | Example wording |
|---|---|---|
| Empty | Button disabled | "Get OTP" in grey |
| Typing | Digits grouped | "98765 43210" |
| Invalid number | Red helper text under field | "Enter a 10 digit number that starts with 6, 7, 8 or 9." |
| Sending | Button shows a spinner | "Sending code..." |
| Code sent | Move to OTP screen | "Code sent to +91 98765 43210" |
| Wrong code | Boxes shake, red text | "That code is not right. Check the SMS and try again." |
| Expired code | Message plus resend | "This code has expired. Get a new one." |
| Too many tries | Field locked for a time | "Too many attempts. Try again in 10 minutes." |
| No network | Banner at top | "No internet. Check your connection and try again." |
| SMS delayed | After 30 seconds | "Not received yet? Check the number or get the code on WhatsApp." |
| Success | Short check mark | "You are logged in" then the home screen |
Write the error text for the person, not for the system. "Error 401" tells a shopkeeper nothing. For more on wording, see UX writing and microcopy for apps.
How is sign up different from login?
With a mobile number and OTP, sign up and login can be the same screen. The app checks whether the number is new. If it is, the user lands on a short "Tell us about you" step. If not, they go straight to the home screen.
For the new user, ask only what you need to start. Usually that is a name. Ask for email, address and preferences later, when the app needs them. When I design sign up screen design for a marketplace or seller app, I add profile steps one at a time and show progress, such as "Step 2 of 3", so nobody feels trapped.
If your app has two kinds of users, such as buyers and sellers, ask "I am a" with two large choices right after the OTP. Do not make them guess from a menu.
Which login mistakes lose Indian users?
Most login failures come from small decisions that a team never tested on a real phone. These are the ones I check first.
- Asking for email and password first. Many first-time users do not remember an email password.
- Not saying where the OTP will go. Always show the number again on the next screen.
- No fix for a wrong number. The user must be able to go back without starting again.
- A timer that hides the button forever. Show the text and keep the "Change number" link active.
- Tiny code boxes. Boxes should be at least the size of a thumb.
- Blocking users with a spinner and no timeout. After 10 seconds, show a message and a retry.
- Forcing English only. Offer the app language on the first screen where it makes sense. See regional language app design in India.
- Asking for permissions before login. Notifications and location can wait. Read designing apps for Indian users for the wider picture.
A short test helps. Give a friend a phone with a slow connection and ask them to log in while you watch. Note where they pause. That one test finds more than a long meeting does.
If you want this flow designed and tested for your own app, see my mobile app design service.
Frequently asked questions
Should an Indian app use a password or an OTP to log in?
+
For most consumer apps, a mobile number with an OTP is easier, because many users forget passwords and share one phone number across all their services. Keep a password option only if your users log in from laptops often.
How long should the resend OTP timer be?
+
Thirty seconds is a sensible default, because SMS usually arrives within that time. Show the countdown as text, such as "Resend code in 0:28", and turn it into a button when it ends.
Should login and sign up be separate screens?
+
With a mobile number and OTP, one screen can do both. The app checks the number and sends the user to either the home screen or a short profile step.
How many OTP attempts should I allow?
+
Allow a few tries, then pause the screen for a short time and say so. Your developer sets the exact limit, but the screen must always explain what happened and what to do next.
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.