Design system development
NDDev builds design systems for products and brands that keep growing: tokens, components in every state, a Figma library and the rules designers and developers follow to assemble new screens. We built nddev.ai on our own system: six practices on shared components, with light and dark themes.
Who it is for
Product teams whose screens have drifted apart in style, and companies running several websites or apps under one brand.
- Tokens and themes
- Components with variants and states
- Figma library
- A direct link to code
The layers of a design system
A system is built from the bottom up. At the base are tokens: colours, type, spacing, radii and shadows with clear names. Tokens make components, components make templates for common screens, and the documentation explains when to use what.
- an inventory of current screens and components
- tokens for colour, typography, spacing, radii and shadows
- themes, such as light and dark
- components with variants and states
- templates for common screens
- documentation with usage examples
- a Figma library for the whole team
- tokens and components handed over to developers
We have taken this path on our own website. The six NDDev practices share components and tokens, each with its own accent colour, composition and illustrations, and all of it works in light and dark themes.
Our team writes front ends in React with Tailwind CSS, shadcn/ui and Radix, so tokens and components move from Figma into code under the same names. If you have your own stack, we deliver tokens in a format it understands.
How a system takes shape and grows
We start with whatever repeats most often.
Inventory
We collect every screen in the product and count how many versions of buttons, fields and colours it contains.
Tokens
We reduce colours, type and spacing to a short set of tokens and check contrast.
Core components
We build a UI kit of core components, usually in about a week plus revisions.
Composite components and templates
Tables, forms, cards and screen templates are assembled from the core parts.
Documentation and adoption
We write the rules, hand over the library and help move the first screens onto the system.
Answers for product teams
How is a design system different from a UI kit?
A UI kit is a set of ready components. A design system adds tokens, usage rules, documentation and a link to code, so new screens can be built from it even after the team changes.
How quickly can the system be ready?
A core UI kit usually takes about a week plus revisions. A full system depends on the number of components, themes and products; we give the timeline after the inventory and fix it in the specification.
Can the system be built on our brand identity?
Yes, that is the usual case. We turn the identity’s colours, type and graphics into tokens and check text contrast against WCAG 2.2.
Who maintains the system after handover?
Your team, using the documentation, or us: we take on new components and changes as separate tasks so the library and the code stay in line.
Does a small product need a design system?
A small product does well with a UI kit and tokens, which can grow into a system later. A full system is worth it once there are many screens or several teams work on the product.
How much does a design system cost?
The starting figure is in the price block. The total grows with the number of components, themes and products, and with the depth of documentation. We fix the price after the inventory.
from $4,500
- Free warranty
- 40 days
Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.
Interfaces
Related
Send us screens that have drifted apart
Five to ten screenshots of your product are enough for a first estimate. We will show which components repeat and outline the scope.
We reply within 24 hours