Design Architect
in the United Kingdom
I'm Brandon Allen, an independent design architect based in Plymouth, working with organisations across the United Kingdom. I design the architecture behind the interface: component systems, design tokens and the developer experience that lets a product stay coherent as it grows.
Design treated as an engineering discipline
A design architect works one level above the individual screen. The questions are structural: which components exist and why, how tokens encode the visual language so it survives a rebrand, how the system documents itself, and how engineers consume it without friction. Get that architecture right and every subsequent screen is faster, more consistent and cheaper to build.
My practice is unusual in pairing this with deep systems engineering. I build AI infrastructure and production web applications, so the design systems I architect are grounded in how they will actually be implemented (real component APIs, real rendering constraints, real accessibility requirements) rather than delivered as static artwork for someone else to interpret.
The result is a visual and interaction system that is engineered, not decorated: versioned tokens, documented components, measurable accessibility and a developer experience that makes the correct implementation the easy one.
Design architecture services across the UK
Stack
Design tokens · component architecture · React / Next.js · TypeScript · accessibility (WCAG) · typography systems · Figma-to-code workflows · documentation tooling
Frequently Asked Questions
What is a design architect?
A designer who works at the level of the system rather than the screen: defining the components, tokens, patterns and conventions from which every interface is then assembled. The role sits between design and engineering, and the value is coherence: products that remain consistent and fast to build as they grow.
How does this differ from hiring a UI designer or an agency?
A UI designer produces screens; an agency typically produces a brand book and leaves implementation to others. I deliver the working system itself (coded components, versioned tokens and documentation) because I am also the engineer who builds production applications with them. Nothing is lost in translation between design and code.
Why does design architecture matter for AI products?
AI interfaces carry unusual obligations: streaming output, displaying uncertainty honestly, making model behaviour inspectable and keeping a human meaningfully in control. These are architectural decisions, not styling decisions, and they are far cheaper to design in from the start than to retrofit.
Do you work with teams across the UK?
Yes. I am based in Plymouth and work on-site across Devon and Cornwall, and remotely with organisations throughout the United Kingdom. Engagements range from a design-system audit to architecting and building the full system alongside your team.
