Tithi Mondal

Article6 min readUpdated

App Onboarding UX: Patterns to Reduce Signup Drop-Off

App onboarding UX for Indian products: phone-first signup, OTP login, permission timing, progressive profiling and empty states that reduce drop-off.

By Tithi Mondal, UI/UX Designer

Most people who install your app will never finish signing up. That is normal, but a lot of the loss is avoidable. App onboarding UX is the set of screens and choices between the first tap on your icon and the first time the user gets value. This post covers the patterns I use most, with a focus on Indian users on mid-range Android phones and patchy networks.

Start with the first useful moment

Before you draw any screen, write one sentence: "A new user is onboarded when they have done ___." For a food app it is seeing restaurants near them. For an exam prep app it is attempting a first question. For a loan app it is seeing an eligible amount.

Every screen before that moment is a cost. Ask of each one: does the user need this now, or do we only want it? If you only want it, move it later. This one habit removes more drop-off than any visual polish.

If you want a full view of how I get from this sentence to screens, see my mobile app design process.

Mobile app onboarding screens: keep the count honest

Many founders ask how many onboarding screens are right. There is no magic number. The test is whether each screen does a job.

  • Splash screen: Show it only while the app loads. Do not add a delay for branding.
  • Value carousel: Three slides at most, with a visible Skip button. Many users will skip, so the app must still make sense without it.
  • Language choice: If your users speak Hindi, Bengali, Tamil or other languages, offer language on the first screen, with each language written in its own script. Do not hide it in settings.
  • Signup or login: One screen, one primary action.
  • First task: Drop the user straight into the product.

I do not recommend a long tutorial with arrows pointing at every button. People forget it in seconds. Teach in context, at the moment a feature becomes relevant.

Signup flow design: phone number first

In India, a phone number is the identity most people trust and remember. An email address is often unused, or shared across a family. So for most consumer apps, phone number first is the right default.

A good signup screen has:

  1. A country code field pre-filled with +91 and a numeric keypad that opens automatically.
  2. One button: "Get OTP" or "Continue".
  3. A short line under the button about how the number will be used.
  4. Google sign-in as a secondary option, only if your users actually have Google accounts they use.

Do not ask for name, email, city and password on the same screen. Each extra field gives the user a reason to leave. If you need a password, ask yourself honestly why. OTP login is faster for most people and removes the "forgot password" problem.

OTP login UX: where most drop-off hides

The OTP step is where I see the most avoidable friction. Small decisions matter here.

  • Auto-read the SMS on Android so the user does not switch apps. Show the code field clearly as a fallback.
  • Show the number they entered, with an Edit link, so a typo is easy to fix.
  • Resend timer: A 30 second countdown, then a clear Resend button. Offer a WhatsApp or call option if your system supports it, because SMS delivery can be slow.
  • Wrong code: Say "That code does not match. Check the SMS and try again." Do not clear all six boxes without telling them why.
  • Expired code: Explain it expired and offer a new one in one tap.
  • Keypad: Number pad only, with the code boxes large enough for a thumb.

Design the failure states as carefully as the happy path. A user who never receives an SMS and sees no help will simply uninstall.

Permission timing: ask when the reason is obvious

A common mistake is firing notification, location, contacts and camera requests on the very first launch. The user has not seen any value yet, so most will tap Deny, and on Android and iOS a denial is hard to undo.

Use this pattern instead:

  1. Wait until the user takes an action that needs the permission.
  2. Show a short in-app message first: one line on why, one benefit.
  3. Only then trigger the system dialog.
  4. If they decline, keep the feature usable another way. For location, offer "Enter your pincode instead".

A delivery app asks for location when the user opens the home screen to find restaurants, not at splash. A camera permission is requested when the user taps "Scan", not at signup. Notifications can wait until after the first order or first completed lesson, when you can say what you will notify about.

Progressive profiling: collect details over time

Progressive profiling means asking for information gradually, when it becomes relevant, instead of in one long form.

DetailAsk it when
Phone numberSignup
NameAfter OTP, as a single friendly field, or at first order
AddressAt checkout, not before
EmailWhen sending an invoice or receipt
Date of birth, ID or KYC detailsWhen the user starts a feature that needs them
Interests or exam targetOn the first home screen, as a one-tap choice

The rule: never ask for a detail before the user can see why. If a regulated product needs identity checks, tell people up front which step needs documents and roughly how long it takes, so it does not feel like a trap. I cover that in more detail in my post on fintech app UI UX design in India.

Empty states: the screen after signup

The first time a user lands on a list, feed, cart or dashboard, it is empty. This is a design moment, not a gap to leave blank.

A strong empty state has three parts: a short line saying what will appear here, one clear action button, and optionally a small illustration. "No orders yet. Find something to eat" with a button to browse is far better than a blank white screen.

Other good uses:

  • Pre-fill with sample content or suggestions so the screen never looks dead.
  • Show a short checklist, such as "Add your photo, choose your language, place your first order", with progress ticking as they go.
  • Explain what to do if the empty state is caused by a problem, such as no internet, and offer a Retry button.

Test the flow on real conditions

Check your onboarding on a mid-range Android phone with a slow connection, in a regional language, with a long name that might break the layout. Count taps from install to first value. Test with five people who have never seen the app. Watch where they hesitate rather than asking what they think.

For wider habits on language, data and device constraints, read designing apps for Indian users.

If you want help shaping your signup and first-run screens, you can see my mobile app design service or get in touch.

Frequently asked questions

How many onboarding screens should an app have?

As few as it takes to reach the first useful moment. A language choice, a single signup screen and then the product is a good target. Use a skippable intro of three slides at most.

Should I use phone number or email for signup in India?

For most consumer apps, phone number with OTP is the better first choice, because it is the identity people use daily. Add email later when you need it for receipts or account recovery.

When should an app ask for notification permission?

After the user has seen value, such as after a first order or first completed lesson. Explain what you will send, then show the system dialog.

What is progressive profiling?

It means collecting user details gradually, at the moment each one is needed, instead of one long signup form.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.