Service · UI UX design agency

UI/UX design

Mostly by unique screen count, then research depth, number of platforms and whether a reusable design system is included. Screens that are variants of one template count once.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Good features fail when users cannot find them, and a UI UX design agency is there to close the gap between what your product does and what people manage to do with it. Red Balloon designs apps, web platforms and SaaS products for insurers, lenders, HR software firms and consumer brands, working as a product design agency that sits beside your engineers rather than handing over pictures. We research real users, map the journeys that drive revenue, prototype and test before polishing, and deliver a design system developers can build from directly. Accessibility, Indian languages and low-end phones are considered from the start. Designs are judged by conversion, task completion and support tickets, not awards.

Specialist services

Go deeper

Also covered on this page

Product designDesign systemsUsability testing
Where this works

Real-world situations we're built for

Illustrative · not a client
Insurtech

Gurugram insurtech's quote journey loses mobile users at the medical-details step

What we'd do
Usability tests, then a step-by-step form with plain Hindi and English labels and prefilled answers
What moves
Goal: quote completion rate up, drop-off at the medical step down, measured as quote completion rate before and after, over a fixed period
HR SaaS

Noida HR SaaS has strong features but trial users never find them

What we'd do
Onboarding redesign with checklists, useful empty states and a Figma component library
What moves
Trial activation rate up, time to first value down
NBFC lending

Delhi NBFC loan app collects low ratings over confusing EMI screens

What we'd do
Redesign EMI and repayment screens with UPI Autopay flows, tested with 8 borrowers
What moves
EMI-related support calls down, app rating up
How a project runs

5 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Research

1–3 weeks

Analytics, interviews, heuristic review, competitor review

You get: Findings and problem priorities

We need: Analytics access and users to interview

Structure

1–2 weeks

User flows, information architecture, wireframes

You get: Approved wireframes

We need: Workshop time with product owners

Prototype and test

1–2 weeks

Clickable prototype and moderated usability tests

You get: Tested prototype

We need: Test participants

UI and design system

2–5 weeks

Visual design, components, tokens, WCAG 2.2 AA checks: 4.5:1 text contrast and 24×24 CSS px minimum targets

You get: Figma library and final screens

We need: Brand guidelines and feedback

Handover and design QA

1–2 weeks, then during build

Dev Mode specs, design QA of builds, iteration

You get: Signed-off build

We need: Developer access to staging

A typical engagement

From first call to result

Illustrative · not a client

Delhi online pharmacy, 25-person tech team, app and website, design done ad hoc by developers

Weeks 1–2ResearchAnalytics review, Microsoft Clarity recordings, 8 interviews with buyers aged 25–65Problems ranked by impact
Weeks 2–3Information architectureCard sort for categories, navigation rework, search log reviewNew navigation map
Weeks 3–5Wireframes and prototypePrescription upload and checkout redesigned; prototype tested with 6 users on mid-range Android phones, five tasks eachValidated flows
Weeks 5–8Visual design and systemFigma components with variables, WCAG 2.2 AA contrast checks, Hindi type scaleDesign system v1
Weeks 8–9Developer handoverFigma Dev Mode specs, exported tokens, acceptance criteria per screen; check first that every frame is marked Ready for devBuild-ready files
Weeks 10–16A/B test and iterateNew upload flow shown to half of users until each arm reaches the precomputed sample size, then compared on conversionShip decision and next design backlog
Where it starts1.8% checkout conversion on mobile web, 45% abandon prescription upload, four different button styles in the app
Where it endsA tested checkout, a design system the team builds from and a testing habit. Weekly watch: checkout conversion, prescription upload completion, order-related support tickets.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Task success rateParticipants completing a task unaided ÷ participantsRule of thumb: 80% or more of participants complete each key task unaided; rework any task below itModerated tests, Maze or LyssnaEach test round
System Usability Scale (SUS)Standard 10-item questionnaire scored 0–10068 is the average in MeasuringU's published SUS benchmark data; aim above itSurvey after usability testsEach release or quarter
Conversion on redesigned flowCompletions ÷ starts for the flowSet from baseline; judge changes by a statistically valid A/B testGA4, PostHog, Optimizely or VWOWeekly during tests
Accessibility conformanceFailed WCAG 2.2 AA checks per key screenZero AA failures on key flowsaxe DevTools, Lighthouse, manual screen reader testsEvery release
Time on taskMedian seconds to complete the key taskSet from baseline, then aim downwardUsability tests and analytics timing eventsEach test round
Design system adoptionComponent instances from the library ÷ all component instancesRule of thumb: 80% or more of component instances on new screens from the library; review detachments monthlyFigma library analyticsMonthly
UX-related support ticketsTickets tagged usability or 'how do I' per 1,000 active usersAt or below the benchmark agreed at kickoff per 1,000 active users within two quarters of launchFreshdesk or ZendeskMonthly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Library publishedDesign tokens to codeFigma variables exported via Tokens Studio or Style Dictionary into the codebaseRemoves: Colours and spacing drifting between design and code
When: Every pull request and design reviewAccessibility checksaxe-core in CI and contrast plugins such as Stark in FigmaRemoves: Shipping inaccessible screens
When: Every pull requestVisual regressionChromatic with StorybookRemoves: Unintended UI changes reaching users
When: Always on, reviewed weeklySession recording reviewMicrosoft Clarity or Hotjar with personal data maskedRemoves: Guessing where users struggle
When: New test roundTest participant recruitingScreener in Typeform or Google Forms feeding a panel sheet, invites via CalendlyRemoves: Days lost finding the right users
Rules we work to

Standards and regulations

W3CWCAG 2.2

Level AA covers contrast, visible focus, target size and accessible authentication

Central Consumer Protection Authority (CCPA), IndiaGuidelines for Prevention and Regulation of Dark Patterns, 2023

Prohibits patterns such as false urgency, basket sneaking and confirm-shaming in interfaces for Indian consumers

AppleHuman Interface Guidelines

Platform patterns and accessibility expectations for iOS apps

GoogleMaterial Design 3

Component and interaction guidance for Android apps

What's changing

Platform and policy updates that affect this work

We track: Figma release notes, Apple Human Interface Guidelines change log, Material Design blog, W3C WAI news.

GoogleMaterial 3 Expressive announced at Google I/O

Android component libraries may need updates for new shape and motion styles

FigmaConfig 2025 launched Figma Make, Figma Sites, Figma Draw and Figma Buzz

More of the prototype-to-site workflow can now stay inside Figma

AppleLiquid Glass design language announced for iOS 26 and Apple's other platforms

iOS app designs need a visual review when rebuilt with the new SDK

European UnionEuropean Accessibility Act obligations began to apply

Indian products selling to EU consumers need accessible interfaces

Before you hire anyone

Questions to ask any agency, including us

Can you show research that changed a design decision?

Why ask

Design without research is decoration

A good answer

A real case showing the finding, the design change it led to and the measured effect

Who will do the work: senior designers or juniors supervised remotely?

Why ask

Seniority shapes quality and speed

A good answer

Named designers, their portfolios and time allocation

How will you check that the built product matches the design?

Why ask

Designs lose quality between Figma and production

A good answer

Design QA on staging, a design-bug tag in your tracker and agreed fix turnaround

How do you design for users on small, older Android phones?

Why ask

Many Indian users are on budget phones and slow networks

A good answer

Designs checked at 360 px width, on low-end devices and with slow-network simulation

How many revision rounds are included, and what counts as a revision?

Why ask

Unclear revision terms cause disputes

A good answer

A fixed number of rounds per phase and a written process for new requests

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How long does UX and UI design take?

An MVP's UX and UI typically takes 3–6 weeks: about one week on flows and wireframes and two to four on visual design and prototype, overlapping development so engineers aren't idle.

  • Larger products are designed in sprint-sized slices, one or two sprints ahead of development.
  • Each round ends with a clickable prototype review rather than static images.
What do developers receive from the design team?

Developers get Figma files with components, auto layout and variables mapped to design tokens, Dev Mode specs, a clickable prototype, and every screen state: loading, empty, error and success.

  • Tokens for colour, spacing and type export to code, keeping Tailwind or Material 3 themes in sync.
  • Component names match the code library, such as shadcn/ui or Jetpack Compose, to cut translation errors.
  • Storybook documents built components so design and code stay aligned.
How do you design for accessibility and Indian languages?

We design to WCAG 2.2 AA, test colour contrast and touch targets, and plan layouts for Hindi and regional scripts, which need more vertical space and fonts that render conjuncts correctly.

  • Government websites must follow GIGW 3.0, and the Rights of Persons with Disabilities Act 2016 sets accessibility duties too; screen-reader labels and focus order go in the design files.
  • Noto Sans Devanagari and other Noto families cover Indian scripts. We check line height and truncation in each, because buttons sized for English labels break first.
How do you prove a design change improved results?

We baseline the funnel in analytics before the redesign, run usability tests on the prototype, then compare conversion or task completion after launch, using an A/B test when traffic allows.

  • Google Optimize shut down in September 2023; we use GrowthBook, VWO or Optimizely for experiments.
  • Microsoft Clarity heatmaps and recordings show where users hesitate, at no licence cost.
  • Low-traffic products use before-and-after comparisons plus task success rates from usability tests.
Do we own the Figma files and design system?

Yes, files are created in or transferred to your Figma organisation, and fonts, icons and images are open-licensed or licensed to your company, so nothing depends on our accounts.

  • Commercial fonts and stock images are licensed in your name; terms are listed in the handover document.
  • The design system includes usage rules so your in-house designers can extend it consistently.
Back to the practice

Product Engineering →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.