UI/UX Design in Mumbai

Say you run a chain of diagnostic labs across Thane and Navi Mumbai and want an app for booking home sample collection. Your first idea is a home screen full of test packages, offers and a big banner. Before drawing anything, we would speak to a handful of real customers and front-desk staff. In this kind of business, the person booking is often a son or daughter booking for an older parent. They want to know three things fast: is the test available, when can someone come home, and how will I get the report?

So the wireframe puts a search box ("type a test name or upload your prescription") and the next free collection slot at the top. Offers move lower down. The booking flow asks for the patient's name separately from the account holder, because they are often different people. Login uses an OTP on the mobile number, with auto-read on Android so nobody has to type six digits while switching apps. Payment offers UPI first, with pay-at-home kept as an option because many families still prefer it.

Then we test a clickable prototype with people from the real target group, on a low-cost Android phone, not on a designer's laptop. One common finding in tests like this: older users miss small icon-only buttons, so we add text labels. Another: the Marathi version of a button label runs longer than the English one and wraps onto two lines, so we widen the button and shorten the copy with your team's help.

Only after these rounds do we polish the visual design and hand over the Figma file to developers. The result is an app that matches how your customers actually book, and far fewer changes once the code is written. The same approach suits healthcare businesses and any service where the buyer and the end user are different people.

The most common mistake is designing for the founder's phone. The team uses the latest iPhone on office Wi-Fi, so the heavy home screen with autoplay video feels fine. Most customers in India are on mid-range or budget Android phones, often with patchy data. Design for them first and the premium phones take care of themselves.

The second mistake is treating regional languages as a translation job done at the end. Hindi and Marathi text often needs more space, and literal translations of English labels confuse people. Plan language support in the wireframes. The third is skipping the empty, loading and error screens. Users see "no results", "payment failed" and "no internet" far more often than designers expect, and a blank screen at that moment loses trust.

Other mistakes: copying a big brand's app layout that was built for a different audience, hiding key actions behind icons with no labels, and asking for too much information at sign-up. Every extra field is a reason to leave.

You may not need a full project yet if you are testing an idea with a simple landing page, or if your current site works and only a few pages underperform. In that case a short audit, or a focused landing page, is the smarter spend.