Will the design system actually reach production, or is it just Figma files?

This is the right question to ask. The zeroheight Design Systems Report 2026 found that 86% of design systems include design tokens, but only 40% of teams have any token pipeline and 11% have working code-to-design sync. We author tokens in the stable DTCG 2025.10 format, generate platform output through Style Dictionary, Tokens Studio or Terrazzo, and map components with Code Connect so the Figma MCP server can serve real structure to coding agents. Who maintains the sync after handover is agreed in writing before we start.

Do you handle the AI disclosure requirements for a product sold in the EU?

We design the disclosure surface. EU AI Act Article 50 obligations have applied since 2 August 2026 and require that a user can perceive they are interacting with an AI within the interaction itself, so a clause in the terms or a metadata-only watermark is not enough, and exposure reaches €15 million or 3% of worldwide annual turnover. Whether your specific system falls in scope is a legal determination for your counsel. We build the interface that makes the answer visible.

Is 3D worth it for our products, or is it a vanity spend?

It depends entirely on the category, and we will say so before quoting. Real-time 3D earns its place in configurable, spatial and high-consideration products, where a buyer needs to see a specific configuration before committing. The widely quoted 40% conversion uplift figure is several years old and we have not been able to trace it to a primary source, so we do not quote it at you. For most categories the sensible first step is a pilot measured against your own baseline, with a frame budget for a mid-tier Android device on 4G and a documented fallback.

If AI makes design faster, why does the price stay the same?

Because generation was never the expensive part. Figma's 2026 AI Report puts it directly, that AI can build almost anything but cannot determine what is worth building. What you are paying for is research, judgement, a system that survives contact with production, conformance to a named accessibility standard, and accountability for defects. It also buys a register that is specific to you rather than the homogenised output people now recognise on sight. Where AI removes real hours, that shows up as shorter timelines and wider scope, and we will tell you which parts an agent produced and who verified them.

UX/UI and 3D Design Services for Web, Mobile and Product Teams

UX/UI design is the work of deciding what a product should do, checking that decision against real users, and then producing the interfaces, design systems and assets that engineering can ship without guessing. Mixcore Studio has been doing that work for more than eight years, across 320+ delivered projects, with a team of around twenty. This section covers three connected practices: UX design, UI design, and 3D modelling for the web and for product visuals.

Design in 2026 is not the same job it was two years ago, and it would be dishonest to describe it as if it were. Tools became agentic rather than merely AI-assisted, handoff became a live protocol instead of an export, accessibility became enforceable law across the European Union, and disclosing AI inside an interface became a legal requirement rather than a design preference. The sections below set out where that leaves a design engagement, including the parts we advise clients not to buy.

What changed in design tooling in 2026

At Config 2026, held in San Francisco from 23 to 25 June, Figma shipped several things at once: Code Layers, Figma Motion (a native timeline and keyframes living on the canvas, in the same file as your components and variables), AI shader fills and effects, generative plugins written from a prompt, Weave node-based generative workflows, and nested folders. Where those AI features move from a free beta to metered billing at general availability, tool spend becomes a design-ops line item rather than a flat seat cost, so it is worth confirming the pricing before you plan a budget around them.

The more consequential change is quieter. The Figma MCP server lets a coding agent query a file's component hierarchy, variables, layer tree and Code Connect mappings continuously, instead of being handed a flat screenshot or a one-way redline spec. That is the largest structural change to handoff since Figma displaced Sketch, and it inverts an old assumption. Token and component hygiene is now a hard prerequisite for AI code quality, not documentation tidiness. Feeding an agent screenshots instead of tokens is a self-inflicted quality ceiling.

Figma's 2026 AI Report, based on 8,403 survey responses and 639 qualitative interviews across ten markets, found that 41% of product builders say AI meaningfully changes how their teams work together, against 7% two years earlier, and that 60% of developers now take part in design work, up from 44%. Its own summary of where the value sits is the most quotable line of the year: "AI can build almost anything. What it can't do is determine what's worth building."

Design tokens are the handoff, not a document

The DTCG Design Tokens Specification reached its first stable version, 2025.10, on 28 October 2025. It covers modern colour (Display P3, Oklch and the full CSS Color Module 4 set), aliases and groups, theming and multi-brand, and cross-platform generation for web, iOS, Android and Flutter. The reference implementations are Style Dictionary, Tokens Studio and Terrazzo, with support in Figma, Penpot, Sketch, Framer, Supernova, Knapsack and zeroheight. One procurement caveat worth stating plainly: DTCG is a W3C Community Group publication, explicitly not a W3C Standard and not on the W3C Standards Track, so contract language should name the version rather than call it a W3C standard.

Adoption has run well ahead of plumbing. The zeroheight Design Systems Report 2026, a survey of 147 design-system practitioners, found that 86% of design systems now include design tokens, but that only 40% of teams have any token pipeline at all and only 11% have working code-to-design sync. In the same survey just 8% described their design system as very stable, while 34% called it unstable and a further 10% very unstable. A design system that drifts away from production is the normal outcome, not an edge case, which is why we treat the pipeline as part of the deliverable rather than a follow-up project.

A homegrown token JSON schema now costs you the entire tooling ecosystem. If you already have one, converting it to DTCG is usually a short piece of work that pays for itself the first time an agent generates a component from it.

Accessibility is a legal deliverable in the EU

The European Accessibility Act has applied since 28 June 2025 in all 27 member states. Directive (EU) 2019/882 leaves penalties to national law, so exposure depends on which member states you sell into. Confirm the figure with local counsel per market rather than assuming a single EU-wide number.

The technical bar is EN 301 549, produced jointly by ETSI, CEN and CENELEC. The published version is still V3.2.1, which incorporates WCAG 2.1 Level AA, and a revision aligning its web, document and software clauses with WCAG 2.2 AA is in progress. WCAG 2.2 has itself been a W3C Recommendation since 5 October 2023 and contains 86 success criteria. Writing "WCAG 2.1 AA" into a 2026 contract books a re-audit the moment that revision lands, so we target 2.2 AA by default and name the target in the statement of work.

We do not sell accessibility overlays and we will not install one. The US Federal Trade Commission settled with accessiBe in January 2025 over the representation that its automated product could make any website compliant with the Web Content Accessibility Guidelines; the consent order requires accessiBe to pay the Commission $1,000,000 in monetary relief and bars that claim. In litigation, an overlay's separate and inferior interface is now used as evidence of a barrier rather than a defence. Remediation belongs in the markup.

Outside the EU, the US Department of Justice moved its ADA Title II web deadlines by a year in an interim final rule published on 20 April 2026. Public entities serving 50,000 or more people now have until 26 April 2027, and smaller entities and special district governments until 26 April 2028. The standard remains WCAG 2.1 Level AA, and the extension does not suspend existing nondiscrimination or effective-communication duties. WCAG 3.0 is a Working Draft (3 March 2026) whose own text says requirements will be added, combined and removed. It is not a compliance target, nothing in law references it, and we do not price work against it.

Designing AI features without defaulting to a chat box

Bolting a chat panel onto a product is now read as a failure to design the interaction. The 2026 consensus is that conversational interfaces underperform graphical ones for structured tasks: linear reading, context recall, and correcting an error over several turns. The patterns that work are agentic and ambient. Show the plan before acting, disclose which tools are being used, let the user set an autonomy level, stream partial results, track multi-step progress, and make recovery and escalation cheap.

A standards layer is forming underneath this. A2UI, the OpenAI Apps SDK that renders React components inline in ChatGPT over MCP, the MCP Apps standard and mcp-ui for host-rendered interfaces, and AG-UI for streaming agent UI into your own frontend are all declarative specifications. Increasingly an AI feature's interface is something you specify once rather than hand-build per surface.

Disclosure is no longer a matter of taste. EU AI Act Article 50 transparency obligations have applied since 2 August 2026, with Commission guidelines adopted on 20 July 2026 and a Code of Practice on Transparency of AI-Generated Content signed by about 190 organisations. Users must be told they are dealing with an AI in a way that is perceivable in the interaction itself. A line buried in terms and conditions, a metadata-only watermark, or a euphemistic "assistant" label does not satisfy it. Deepfakes must be labelled, and generated or altered content must carry machine-readable marks. Exposure runs to €15 million or 3% of worldwide annual turnover. We design that disclosure as part of the interface. Whether your particular system falls in scope is a question for your counsel, not for us.

Platform design languages and 3D on the web

Both mobile platforms re-based, and Apple's is effectively compulsory. Liquid Glass, announced at WWDC on 9 June 2025, spans iOS 26, iPadOS 26, macOS Tahoe 26, watchOS 26, tvOS 26 and visionOS 26. Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later against a 26-series SDK, and building against that SDK applies Liquid Glass to native controls by default unless you opt out. That governs the build SDK, not the deployment target, so you can still support older OS versions. Shipping the default is not automatically the safe choice either. Nielsen Norman Group has published a critical usability read on Liquid Glass in iOS 26, so the sensible position is to adopt the material deliberately and re-check contrast and legibility rather than inherit it. On Android, Material 3 Expressive and its spring-based motion physics is now the default on Pixel devices.

On the web, WebGPU is now a genuine cross-browser baseline. Chrome and Edge have shipped it since version 113, Safari 26.0 added it in September 2025 across macOS Tahoe 26, iOS 26, iPadOS 26 and visionOS 26, and Firefox shipped it in 141 on Windows and extended it to macOS 26 on Apple silicon in 145, with the remaining platforms still to follow. Compute shaders are the capability WebGL never had. Three.js (r185) ships WebGPURenderer with automatic WebGL 2 fallback, and shader authoring has moved to TSL, a node system that compiles to both WGSL and GLSL. New material features are TSL-first, which makes hand-written GLSL strings a migration liability rather than a preference. Babylon.js 9.0, released in March 2026, added clustered lighting, volumetric lighting, a frame graph and textured area lights.

Gaussian splatting crossed from research demo to shippable format. Khronos announced the KHR_gaussian_splatting release candidate for glTF 2.0 on 3 February 2026, contributed to by Autodesk, Cesium, Esri, Huawei, Niantic Spatial and NVIDIA. On delivery, PlayCanvas open-sourced SOG (Spatially Ordered Gaussians), whose own worked example compresses a 1 GB PLY capture to a 42 MB SOG file, and added streaming and a WebGPU renderer to SuperSplat. Shipping raw PLY to a browser is a bandwidth defect. For asset interchange, AOUSD published the first OpenUSD Core Specification 1.0 on 17 December 2025, with Geometry, Materials and Physics specifications in progress.

Two tools still turn up in client stacks and should not. Adobe XD is in maintenance mode with no meaningful new features and no standalone download, and InVision shut its design and collaboration products down permanently at the end of 2024, with invisionapp.com now redirecting to Miro, so an InVision prototype in a handover pack is dead infrastructure. Penpot is the credible open-source alternative when a client cannot use Figma.

When we tell you not to buy this

Three cases come up often enough to state up front.

3D that nobody asked for — real-time 3D earns its place in configurable, spatial and high-consideration products. The most recycled figure in this market, a roughly 40% conversion uplift for products with 3D visualisation, is several years old and we have not been able to trace it to a primary source we would put our name to, so we treat it as folklore rather than evidence. The vendor studies in furniture and other configurable categories point the same way, that seeing a specific configuration raises buyer confidence, but they are published by the companies selling the technology. The honest answer is a small pilot measured against your own baseline, not somebody else's case study.
A full design system before there is a product to systematise — for a team of three shipping a first release, a token set plus a small component library beats a documented system nobody has time to maintain. The zeroheight 2026 numbers on stability exist for a reason.
A redesign when the problem is upstream — if activation is failing because of pricing, missing onboarding data or a broken integration, new screens will not fix it. We would rather run a short discovery and tell you that than sell a visual refresh.

There is also the cost question, which every buyer now asks. AI has made parts of this work faster, so why has the invoice not fallen. Generation is cheap now. Judgement, research, accessibility conformance and accountability for what ships are not, and those are what we price. Where AI genuinely removes hours it shows up in scope and speed, and we will tell you which parts of a deliverable an agent produced and who verified them against a measurable bar.

What this section covers

UX research and product definition
Interface design and design systems
DTCG design tokens and pipelines
WCAG 2.2 AA accessibility
Motion and interaction design
3D, WebGPU and Gaussian splats

How a design engagement runs

Three phases, each ending in something you can check rather than a slide. The accessibility target and the performance budget are agreed in the first phase, not discovered in the last.

01

Discovery and definition

Research with your actual users, an audit of the current product including an accessibility baseline against WCAG 2.2 AA, and a written decision on what is worth building. Where an existing InVision or Adobe XD file is the source of truth, we migrate it first, because both products are end of life.
02

System and interface

Tokens authored in DTCG 2025.10 format, a component set built on them, interface and motion design, and accessibility checked as the work is produced rather than audited afterwards. Platform work follows Liquid Glass on iOS 26 and Material 3 Expressive on Android, adopted deliberately with contrast re-checked.
03

Handoff that stays live

Code Connect mappings and the Figma MCP server so coding agents read structure instead of screenshots, a token pipeline through Style Dictionary, Tokens Studio or Terrazzo, and documented degraded paths for reduced motion, no WebGPU and low bandwidth. We name who maintains the sync after handover.

Frequently asked questions

What accessibility standard do you design to, and do you use an overlay?

We design to WCAG 2.2 AA and name that target in the statement of work. WCAG 2.2 has been a W3C Recommendation since 5 October 2023 and has 86 success criteria, and EN 301 549 is being revised to align with it. We do not use accessibility overlays. The US Federal Trade Commission settled with accessiBe in January 2025 over the representation that its automated product could make any site compliant with the Web Content Accessibility Guidelines, and the consent order requires a $1,000,000 payment to the Commission. An overlay's separate interface is now used in litigation as evidence of a barrier. Remediation goes in the markup.
Will the design system actually reach production, or is it just Figma files?

This is the right question to ask. The zeroheight Design Systems Report 2026 found that 86% of design systems include design tokens, but only 40% of teams have any token pipeline and 11% have working code-to-design sync. We author tokens in the stable DTCG 2025.10 format, generate platform output through Style Dictionary, Tokens Studio or Terrazzo, and map components with Code Connect so the Figma MCP server can serve real structure to coding agents. Who maintains the sync after handover is agreed in writing before we start.
Do you handle the AI disclosure requirements for a product sold in the EU?

We design the disclosure surface. EU AI Act Article 50 obligations have applied since 2 August 2026 and require that a user can perceive they are interacting with an AI within the interaction itself, so a clause in the terms or a metadata-only watermark is not enough, and exposure reaches €15 million or 3% of worldwide annual turnover. Whether your specific system falls in scope is a legal determination for your counsel. We build the interface that makes the answer visible.
Is 3D worth it for our products, or is it a vanity spend?

It depends entirely on the category, and we will say so before quoting. Real-time 3D earns its place in configurable, spatial and high-consideration products, where a buyer needs to see a specific configuration before committing. The widely quoted 40% conversion uplift figure is several years old and we have not been able to trace it to a primary source, so we do not quote it at you. For most categories the sensible first step is a pilot measured against your own baseline, with a frame budget for a mid-tier Android device on 4G and a documented fallback.
If AI makes design faster, why does the price stay the same?

Because generation was never the expensive part. Figma's 2026 AI Report puts it directly, that AI can build almost anything but cannot determine what is worth building. What you are paying for is research, judgement, a system that survives contact with production, conformance to a named accessibility standard, and accountability for defects. It also buys a register that is specific to you rather than the homogenised output people now recognise on sight. Where AI removes real hours, that shows up as shorter timelines and wider scope, and we will tell you which parts an agent produced and who verified them.