EzGIG
Contact
EzGIG
Design and marketing

One kit. Every screen consistent.

Start a project

One kit for every screen

A design system is the shared set of design tokens, components and rules that every screen in your product is built from. EzGIG designs and documents one in design files and in code, for product teams in Malaysia whose screens have drifted apart or who have several teams building one product.

Design tokensComponent libraryCode componentsTeam training
340+ EzKids features on one kit

What a design system includes

A style guide is one part; a design system adds components, code and rules.

PartWhat it isWhere it lives
Design tokensNamed values for colour, type, spacing, radius and motionDesign files and code
Component libraryButtons, forms, cards and tables with every stateDesign files and code
Usage guidelinesWhen and how to use each part, with do and don't examplesDocumentation
Code componentsThe same components built for your front endYour code repository
Style guide (on its own)Colours, fonts and logo rules onlyA PDF or a single page

Six deliverables, one source of truth

Design and engineering work from the same parts.

Design tokens

Colour, type, spacing and radius as named values.

Component library

Every reusable part with its states and variants.

Usage guidelines

Clear rules so new screens match old ones.

Code components

The same parts built for your front end.

Documentation

One place your team can look things up.

Team training

Your designers and engineers learn to use and extend it.

Kits we built and use daily

Our own products run on design systems we made.

In use across the group

EzGIG's own design system

Tokens, components and this website, built from one kit.

About EzGIG
EzKids parent app screen built from one shared component kit
340+ features

EzKids

One kit across five role logins: owner, principal, teacher, parent and child.

See EzKids
340+EzKids features built on one kit
5role logins sharing the same components
1kit behind EzGIG's own tokens, components and this website

When a design system pays back

It earns its keep once several people design or build the same product.

A good fit if

  • Every screen looks different
  • Design and code drift apart
  • Several teams build one product
  • You're rebranding

Probably not the right start if

Printed app screens pinned in a grid, with buttons, colours and spacing that do not match
We start from what you have

Audit, define, build, train

We start from what you already have, not a blank page.

Designers comparing colour swatches while agreeing design tokens
Tokens agreed before components
  1. Audit

    An inventory of every screen and component in use.

  2. Define

    Tokens for colour, type, spacing and radius agreed.

  3. Build

    Components designed and coded, with every state.

  4. Train

    Documentation published and your team trained.

Three ways to work with us

Pick the model that fits how your team ships.

Project

A defined scope, timeline and team, with a fixed quote after discovery.

Retainer

Ongoing capacity for new components, improvements and support.

Dedicated team

Designers and engineers embedded alongside yours.

You own the tokens, components and code, as set out in your contract.

Questions about design systems

A design system is a shared set of design tokens, components and usage rules that every screen of a product is built from. It keeps design and code consistent as teams and features grow.

  1. Liftoff

    Book a slot or send a quick brief. A real person on our team replies within one working day.

  2. Mission briefing

    A focused call on your goals, systems and site. We tell you straight what will work, and what won't.

  3. Flight plan

    A clear written plan shaped around your needs, with a fixed price and timeline. No surprises.

Ask EzGIG