Book a call

Work / CARS24

CARS24CARS24 · 2025 · Patterns, CMS, Adoption

Pages built from tested blocks, not from scratch

CARS24 was turning into a super app and launching new services almost every month. Every homepage and landing page was designed and built from zero. We built a pattern library that lets teams assemble pages from tested blocks, so they ship faster and every page feels like one product.

Role
Lead System Designer
Team
2 designers, 2 developers, a PM, a CMS lead
Platforms
App and mobile web
Markets
India, UAE, Australia
A phone showing a CARS24 homepage built from pattern library blocks

The 30-second version

The problem

Every new page started from a blank canvas. The same cards and carousels were built again and again, and no two services felt alike.

What we did

Six families of page blocks with grid, text, image and behaviour rules, wired to the CMS and the tokens, with one name from Figma to code.

What changed

Pages took about 43% less time. Within three months every major redesign in three countries was built on the library.

~43%
less time to design and build a page
3 months
to reach every major redesign
~$212k
saved in design and development
3
countries building from one library
01

A car company turning into a super app

Loans, car checks, fines, FASTag, servicing, car wash: new services launched almost every month, each needing its own homepage, landing and offer pages.

  • Buy a used car
  • Sell your car
  • Get a loan
  • Car check
  • New cars
  • Insurance
  • Pay challan
  • Recharge FASTag
  • Car servicing
  • Car wash
  • Scrap and earn
  • Hire a driver
  • Credit cards
  • Showrooms

The back end kept up. The screens didn't: several redesigns ran at once, and the app started to feel like many apps stitched together.

02

Every page started from a blank canvas

Nothing was shared, so the same work was repeated, it cost more, took longer, and moving between services felt like changing apps.

India screens rebuilt on the pattern library
Audit of the India homepages before the library
BeforeAfter
Drag to compare the India audit with the screens rebuilt on the library.
Time per new page
100%
~57%

BeforeAfter

Total time to design and build a page, before and after. The drop is what was measured: about 43%.
03

Borrowing what people already know

Our users also lived in Swiggy, Zepto and Blinkit. Service grids became quick-action rows, offer banners became the banner family, scrolling rails became sliders.

Offer banners from other consumer appsService grids from other consumer apps
Patterns customers already understood meant less to learn.
Read the detail

We audited homepages, landing pages and exit flows in every market and sat with product managers, engineers and visual designers. Layouts were all over the place, one component existed in many builds, there were no rules for content, and nobody knew how a section should adapt across screens.

04

Every pattern comes with its own rules

Grid, text limits, image shapes and behaviour, set in the CMS, so an editor can fill a pattern and still get a page that looks right. Try it: type a longer title, or change the image shape.

Homepage / Widgets / contextual_card_slider

Image

Locked by the pattern: size, spacing, type, colours, behaviour. Editable: image, text, button, link, schedule.

Live preview

Like this car? Take it for a spin!

Book test drive
One pattern fully specified: the two-column grid in three image shapes, every size marked for design and engineering.
One pattern fully specified: the two-column grid in three image shapes, every size marked for design and engineering.
05

Six families of page blocks

Built on the base design system, with layout templates, ready-made combinations, tokens, specs and usage guidance.

Banners

Banners

One template, three types: full bleed, padded and carousel, in fixed sizes. Used for campaigns, offers and the top of every homepage.

06

One name from Figma to code to CMS

The library only works if four groups can use it without waiting on each other. Every pattern has one name everywhere.

Designercontextual_card_slider

Picks patterns and sets the page order.

Developer<ContextualCardSlider />

Builds each pattern once, mapped to base tokens.

CMS teamcontextual_card_slider

Fills images, copy and links, and schedules what goes live.

Product managerPattern request · High

Asks for new patterns with the request template, not one-off screens.

Pattern implementation spreadsheetPattern request form
The implementation sheet engineering builds from, and the request template for anything the library doesn't cover.
07

From empty patterns to a live page

A page is now a stack of patterns. Drag the divider: on the left, the empty blocks with their rules; on the right, the same page filled in through the CMS. Scroll inside the frame.

The same homepage, live
The homepage as empty patterns
PatternsLive
08

One library, every market and service

India's new homepage, the UAE app revamp, Australia's homepage in five themes, and new service apps for loans, servicing, car wash and car care.

The UAE revamp, built from library patterns.
The UAE revamp, built from library patterns.
Faster pages (target 30–40%)
target 40%
43%
Redesigns on the library (target 50%)
target 50%
all major redesigns

BeforeAfter

Both targets were beaten.
09

What we'd do again

Small, token-driven blocks scale, and documentation decides adoption.

Small, token-driven blocks scale

They made fast experiments possible without new design debt.

Follow what users already know

Familiar patterns leave room to innovate where it matters.

Docs decide adoption

Clear guidelines kept people using it after launch.

Bring engineering in early

It caught performance limits before they became rework.

+

From the files

Select any image to see it full size.

Led by Aniket Pandey as Lead System Designer at CARS24, with two designers, two developers, a product manager and the CMS lead. Images belong to CARS24 and are shown for portfolio purposes.

Need this for your product?

We do this work for product teams now. Start with a two-week audit.

Next case studies