Friction is a Feature: Rethinking Onboarding for Bharat

Modern UX gospel says: eliminate friction. Every extra tap is a conversion leak. Every form field is a drop-off point. Reduce steps. Simplify flows. Make it seamless. This advice is everywhere. In design blogs, in conference talks, in every "UX best practices" article you have ever read.

And to be clear, for many products and many users, this advice is correct. If you are designing a checkout flow for Amazon or a ride-hailing app for urban millennials, yes, fewer taps is almost always better.

But when your users are first-time smartphone owners in tier-3 India, this advice does not just fail. It actively harms the experience.

The context most designers never encounter

Let me paint you a picture. You are a frontline health worker in a district in Madhya Pradesh. You are 54 years old. You received a government-issued smartphone six months ago. Before that, you used a feature phone for calls and SMS. You have never filled out a digital form. You have never navigated a multi-step flow. You are not sure what the difference between "save" and "submit" is.

Now you are asked to use a mobile app to log nutrition data for children in your district. The app needs to capture the child's age, weight, health status, mother's details, and immunization records. There are 15 fields. Some are mandatory. Some depend on previous answers. The data you enter directly affects government resource allocation in your district.

If you make a mistake, you are not sure if you can fix it. If the screen changes unexpectedly, you are not sure if you lost your work. If the app asks you to confirm something, you are not sure what will happen if you say yes.

This is not a hypothetical. This is the actual user context I design for at Digital India Corporation.

When "seamless" backfires

We discovered the friction problem the hard way. Our first version of a critical onboarding flow was, by every standard UX metric, well-designed. Clean layout. Minimal steps. Clear labels. Progressive disclosure. Auto-advance where possible.

The completion rate was terrible. Not because the flow was confusing in the traditional sense, but because users did not feel in control. They were not sure their data was being saved. They were afraid of making irreversible mistakes. The speed and smoothness we designed for actually made them less confident, not more confident.

In our field research sessions, we heard the same feedback repeatedly:

• "It moved too fast. I was not ready for the next screen."
• "I am not sure if it saved. Can I check?"
• "What happens if I press the wrong button? Will I lose everything?"
• "I wanted to go back and check what I entered, but I could not find how."

The problem was not usability in the traditional sense. The problem was confidence. Our users lacked the mental model that experienced digital users take for granted. They did not know that data auto-saves. They did not know that they can go back. They did not know that pressing "Submit" was not permanent and irreversible.

What intentional friction looks like

We went back and redesigned the flow with deliberate, intentional friction. Not the annoying kind. Not CAPTCHAs and unnecessary loading spinners. The reassuring kind. The kind that makes a nervous user feel like the system is on their side.

Here is what we changed:

• Confirmation screens after every major section. We showed users a summary of what they had just entered, in plain language, and asked them to verify before moving on. "You entered: Child's name is Priya. Age is 3 years, 4 months. Weight is 12.5 kg. Is this correct?"
• Explicit "Are you sure?" dialogs before any action the user could not reverse. Not a generic modal, but a specific one: "You are about to submit this record. Once submitted, the data will be sent to your district office. You can still edit it for the next 24 hours."
• Persistent, visible progress indicators. Not dot-style progress or thin bars at the top that are easy to miss, but prominent text: "Step 3 of 6. You are halfway done. Keep going."
• Success screens that celebrated the completion. Not just a checkmark and a redirect, but a full screen with a congratulatory message, a summary of what was submitted, and clear next steps.
• A visible "save draft" button on every screen. Even though the app auto-saved, we added an explicit button so users could see and control the save action.

The results

The v2 flow had more screens, more taps, and more steps than v1. By every traditional UX heuristic, it should have performed worse.

It did not.

Completion rates increased by 34%. Error rates dropped by over 50%. And in our qualitative research, users consistently reported feeling "more confident" and "more in control." One user said something I will never forget: "This app respects me. It waits for me. It does not rush me."

That single piece of feedback taught me more about user-centered design than any conference talk or design article I have ever encountered.

The broader lesson

Friction is not inherently bad. Seamlessness is not inherently good. The appropriate level of friction depends entirely on who your user is, what they know, what they fear, and how much they trust the system.

Most UX best practices are written by and for users in San Francisco, New York, and London. They assume a baseline of digital literacy that does not exist for a huge portion of the world’s population. When you design for Bharat, you are designing for a fundamentally different set of user needs, anxieties, and mental models.

Sometimes the best thing a designer can do is slow the user down. Give them a moment to breathe. Let them verify their input. Celebrate their progress. Believe me, it will show up in your metrics.

The craft is not in the tool. It is, and has always been, in the thinking.