Designing for the small screen first, and actually meaning it
Web design in India means three things a generic brief leaves out. The first draft is a phone screen rather than a desktop comp that gets narrowed later. Every decorative image is treated as a cost someone else pays. And the page has to carry the signals an Indian buyer uses to decide a business is real before they will call it.
Most Indian sites are still designed on a wide canvas and then squeezed. The desktop layout is the one presented, argued over and approved; the phone version is derived from it in an afternoon. Since nearly all the traffic is on a phone, the version almost nobody sees got the attention and the version everybody sees got the leftovers.
You can recognise a reflowed design without being told. The hero is a wide photograph with its subject cropped out of frame on a phone. Three columns of equal weight stack into a long scroll with no hierarchy, so the important thing is fourth. A navigation built for hover becomes a hamburger hiding the one link people came for. And near the top sits a large decorative image carrying no information, downloaded over mobile data by every visitor, most of whom scroll past before it arrives. None of this showed up in the desktop review where the design was approved.
When this work makes sense
Questions worth asking any supplier
Will the first design you are shown be a phone screen, or a desktop layout with a phone version promised later? Whichever comes first gets the real thinking.
Does the designer have a view on how many images a page should carry, and can they defend each one? Without that, image count is set by whoever has the most pictures.
Does the design include your address, a named person and your registration details, or are those treated as footer clutter? Indian buyers check them before they call.
If a regional script is involved, has the designer set it rather than pasted it? Indic scripts need their own line height and size relative to the Latin beside them.
Is the design reviewed on a phone in daylight? Contrast that reads well on a monitor indoors can fail outdoors, which is where a great deal of Indian browsing happens.
Deliverables
Small-screen layouts designed first and signed off first, with wider layouts derived from them
An explicit image budget per template, how many, at what size, and what each one is doing
Art direction that replaces decorative photography with type, colour and space where the photograph added nothing
A trust block designed into the page rather than dropped in the footer: full address, a named contact, and photographs of the actual premises
Type scales set separately for Latin and for your Indic script, so mixed headings sit on the same optical line
Tap targets, form layouts and thumb reach tested on a real handset rather than a resized browser window
A component set your developers can build from, with states and spacing defined rather than implied
Built with
Process
We design the phone screen first and present it on a phone, not as a rectangle in a slide. The client sees the design at the size their customers will, held in one hand, before anyone discusses a desktop layout. This changes what gets approved. Hierarchy arguments resolve quickly because only one thing can be first on a small screen, and decorative images lose the argument once they are seen taking a whole screen of scroll. The wider layouts then follow from decisions already made.
The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.
What moves the number
Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:
Three ways teams arrive at a mobile layout
Design desktop, reflow to phone
Fits: Internal tools and sites where the audience genuinely works at a desk
Limits: The phone layout inherits a hierarchy built for a wide canvas, and the fix is a redesign rather than an adjustment
Design the phone first
Fits: Almost every Indian consumer or local service business
Limits: The desktop layout can look sparse unless someone deliberately designs the extra space rather than stretching the small one
Two separate designs
Fits: Rare cases where the phone and desktop tasks are genuinely different
Limits: Two design systems to maintain, and in practice one stops being updated within a year
Case studies
No published Indian web design case study yet. Design work runs from our head office at SL Jubilee, Jubilee Hills, Hyderabad. We will publish client work once we have permission to name the business and results we can evidence.
MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.
Frequently asked questions
What does designing mobile-first actually change?
The order in which decisions get made. On a small screen only one element can be most important, so hierarchy has to be settled before anything else. Designing wide first lets you avoid that decision, and the phone layout then inherits an unresolved hierarchy that stacking will not fix.
Why do you push back on decorative images?
Because someone pays for them, and it is not you. A large photograph that carries no information is a download charged to a visitor on a data pack and a delay before they see anything useful. We are not against imagery. We are against imagery nobody can explain the purpose of.
What trust signals do Indian buyers look for?
A complete physical address rather than a city name, a phone number that gets answered, a named person with a designation, photographs of the real premises rather than stock, and registration details where you display them. These matter more here than a testimonial slider, and they are usually the cheapest thing on the page to add.
Should we show our GST number on the site?
Many Indian businesses do, and B2B buyers often look for it. Whether you display it, and where, is a question for your accountant rather than for us. What we will do is design a place for it that reads as a credential rather than as small print, alongside the address and registration details.
Our Hindi pages look wrong but we cannot say why. What is happening?
Usually line height and relative size. Devanagari occupies more vertical space than Latin at the same point size because matras sit above and below the headline, so a leading value tuned for Latin crowds or clips it. Setting a separate scale for each script fixes most of it.
Can you work with our existing brand?
Yes, and often the brand is not the problem. What usually needs work is the type scale, the spacing system and the image policy, none of which most brand guidelines cover. We would rather extend what you have than present you with a rebrand you did not ask for.
Do you design and build, or only design?
Either. If we hand over, you get a component set with states, spacing and behaviour defined, because a handover that is only flat screens leaves every ambiguous decision to whoever builds it. If we build it too, the image budget agreed in design is the one enforced in the code.
Services that connect to this
Talk to us about this
Tell us what you are trying to build and we will come back with scope, approach and an estimate.