UI/UX Design

Style Guide or Design System? What Your Project Needs

Style guide or design system? Where I draw the line for clients, and how I start, organise, name and document a design system so developers can build from it.

Dhiraj Ingle, author of this article.

Dhiraj Ingle

UI/UX Designer · Framer Expert

A small flat style guide card with three colour swatches, joined by one rod to an orange molecule whose white spheres carry interface icons.

Style Guide or Design System? What Your Project Needs

1 min read
IN THIS POST:
No headings found
In this post:
No headings found

Quick answer: A landing page, or a site of two to three pages with a similar look, only needs a style guide. A mobile app or a product UI needs a full design system, documented with every state, variant and token. That’s the line I draw for every client.

What’s the difference between a style guide and a design system?

A lot of people call the simple style guide they made for a landing page a design system. They’re not the same thing.

A style guide is your colours, your text styles and a few basic rules. It keeps a small site consistent.

A design system includes a style guide, but it goes much further. It has reusable components with all their variants, tokens for every value, naming rules and documentation for each part.

Nielsen Norman Group describes it the same way. The style guide is one part of a design system, not a replacement for it.

A style guide with colours, text styles and two buttons, for a landing page or 2 to 3 similar pages, next to a design system that holds that style guide plus components and variants, tokens, naming rules and documentation, for a mobile app or product UI.

When is a style guide enough?

If it’s a landing page, or two to three pages with a very similar design style, I tell the client they need a style guide. They don’t need a design system.

A full system for a small site is extra time and extra cost that nobody will use. Colours, text styles and a few button styles cover it.

When do you need a design system?

For a mobile app or a product UI, a design system isn’t optional. Other designers, developers and editors will keep building after me. They need one place to take everything from.

And it can’t be just a pile of components. It has to be properly documented, with every state and variant, clear naming, colour tokens and all the other tokens.

The Travel App is a good example. It has 150+ screens and a light and dark design system documented for handoff. The Social Media App needed one too, across 150+ screens.

How do I start a design system now that AI is here?

I don’t start with the system. I start with the design.

Once I’ve designed one page, or two to three high-fidelity screens of an app, the basics are already there. Buttons, text styles, colours. Then I use AI to turn those into a basic design system, and I scale it from there.

AI makes the first version fast. The decisions are still mine: what to merge, what to name and what the developer needs to see.

How do I keep components from turning into a mess?

Too many components is a mess. So as soon as I see components or variants repeating, I organise them into one component with proper variants.

One component can easily have 10 to 12 variants. In Figma, I also use properties that show or hide a layer, so a small change doesn’t need its own component.

One button component with four properties, type, state, size and mode, and a grid of all 24 variants in light and dark mode.

For handoff, I put every variant in its own section. The developer sees what each variant does, why it exists and where to use it. That clears up most handoff questions before anyone has to ask.

How do I name tokens and text styles?

I don’t invent my own token names. I use primitive and semantic tokens, because that’s the language designers and developers already understand everywhere.

A primitive token holds a raw value, like one shade of blue. A semantic token says what a value is for, like the colour of primary text, and points to a primitive. Change the primitive once and everything that uses it updates.

Example primitive tokens orange-500, grey-900 and grey-50 feeding the semantic tokens action-primary, text-primary and surface, used in a small card, and a new shade of orange-500 updating every primary button.

For text styles, I follow the naming in Apple’s Human Interface Guidelines, like Title, Headline, Body and Caption. I’ve read Material’s naming too, and Apple’s makes more sense to me.

Naming styles by role: a product screen with its text labelled Title, Headline, Body and Caption, the names Apple and Material use, and the Body role at 18px on a desktop web app and 16px on mobile web.

I go deeper on this in my post on building a typography system.

Do I use atomic design?

Yes, and here I follow standard practice: atoms, molecules, organisms, templates and pages. I don’t reinvent it.

If you want to learn it properly, go to the source. Brad Frost’s book Atomic Design explains it better than any summary.

How do I document a design system?

For big design systems, I document the way Apple does. Related components sit together on one page. Different components get their own pages, each with an explanation.

I also built a notes component that sits next to each component. It carries a status tag, like In progress or Ready for dev. Once every variant of a component is documented, I switch its tag to Ready for dev.

Each tag has its own colour. So a developer doesn’t have to read the tags to know what’s ready. They can see it at a glance.

A documentation page: a sidebar of component pages with status dots, a Button page with Primary, Quiet and Pressed each in its own section, and a notes card with colour-coded status tags In progress and Ready for dev.

Which one does your project need?

Tell me what you’re building. On a free intro call, I’ll tell you straight whether a style guide is enough or you need a full design system, and what it takes to build.

Designing your own portfolio? That’s a style guide job. MonoCraft is my $79 Framer template, with a blog and case study pages built in, ready for your work.

FAQ: style guides and design systems

Is a style guide the same as a design system?

No. A style guide is one part of a design system. A design system adds components, variants, tokens and documentation.

Does a landing page need a design system?

No. A landing page, or a site of two to three pages with a similar look, only needs a style guide.

Does every mobile app need a design system?

Yes. Other designers and developers will keep building on it, so it needs one documented place to work from.

Can AI build a design system for me?

AI can build a basic first version from your designs, and it’s fast. Deciding what to merge, how to name things and what developers need is still design work.

Key Takeaways

A landing page needs a style guide. An app or a product UI needs a design system that’s documented with every state, variant and token.

  • A style guide is one part of a design system, not the same thing.

  • Two to three similar pages? A style guide is enough.

  • Mobile apps and product UIs always need a documented design system.

  • I design the first screens, then use AI for a basic system and scale it.

  • One component with many variants beats a pile of similar components.

  • Primitive and semantic tokens, and Apple’s names for text styles.

  • Colour-coded status tags tell developers what’s ready to build.

Date:

·

UI/UX Design

Written by

Dhiraj Ingle, author of this article.

Dhiraj Ingle

UI/UX Designer · Framer Expert