Aplance UI
React design system and UI library
A React component library built so our interfaces stay scalable, flexible and independent from UI-library lock-in.
UI systems and frontend craft
We build design systems and frontend architecture — tokens, components and documentation — so interfaces stay consistent, accessible and easy to change. Our own Aplance UI library and postcss-token-utilities exist because we practice this on ourselves first.
What you get
- A component system your team can extend without breaking the look
- Design tokens as one source of truth for color, type and spacing
- Accessibility treated as a default, not an audit finding
- Frontends free from vendor lock-in and framework churn
Approach
How we run it
-
Start from tokens
Color, type, spacing and radius live as tokens, so consistency is structural instead of remembered.
-
Build components once
Repeated UI becomes documented components with clear states, not copy-pasted variations.
-
Document in Storybook
The system stays visible and reviewable as products and teams grow around it.
-
Keep CSS modern and owned
Native CSS capabilities over heavy frameworks, so styles age well and stay yours.
Where AI fits
AI-era interfaces bring new patterns — streaming responses, review states, sources and confidence. We design these into the component system so AI features feel native to the product instead of bolted on.
FAQ
Common questions
We already have designs in Figma. Where do you fit?
We turn them into a living system: tokens, components and documentation that keep the implementation faithful to the design as it evolves. Figma stays the design home; the code becomes its reliable mirror.
What is Aplance UI?
Our own React component and design library, documented in Storybook and built on modern CSS and headless primitives with zero vendor lock-in. It is the foundation we reuse and adapt across client work.
Can you improve an existing messy frontend without a rewrite?
Usually, yes. We introduce tokens and shared components gradually, clean the highest-traffic screens first and let consistency spread release by release.