Atlas · DS247 · Future / AI: Simulation
Digital Twin UI
Digital representation of equipment or a process linked to real states.
- Status in 2026: Emerging. Appearing in practice, not yet settled.
- Trend 2027 to 2030: Rising in some contexts (an editorial projection, not a forecast).
- The term: Known technical term or standard.
Definition
Digital representation of equipment or a process linked to real states.
Traits
- 3D model
- data
- sensors
Typical settings: Industry, IoT.
When to use it, and when not
Consider it when the task and motivation match: factory engineers and operators. Typical settings: industry, iot.
Be careful when the risk below would hurt the main task: outdated model and false precision.
The audience is a hypothesis
"Factory engineers and operators" describes a motivation, task or context for which this direction tends to be chosen. It was not measured, and it says nothing about any age, gender or other group.
UX risk and how to reduce it
Risk: Outdated model and false precision.
Mitigation and accessibility: Timestamp, telemetry and data quality.
How to check: Test with realistic scenarios: task success, accuracy, reversal, auditability, understanding of what the system does on its own, and a human's ability to step in.
Evidence
Emerging: exploratory work, with no causal validation for this style.
The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.
- Apple 2025 (Standard or guideline): Layout for spatial computing.
- W3C Web Accessibility Initiative 2021 (Standard or guideline): Cognitive accessibility guidance.
Heuristic scales
Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.
- Visual complexity heuristic
- 5 / 5 (1 is few visual elements, 5 is many layered elements)
- Expressiveness heuristic
- 3 / 5 (1 is restrained, neutral, 5 is highly expressive)
- Information density heuristic
- 5 / 5 (1 is sparse, 5 is dense)
In our library
No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.
Prompt for your AI
Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.
Design this interface in the "Digital Twin UI" direction (future / ai, simulation): Digital representation of equipment or a process linked to real states. Visual and interaction traits to use: 3D model, data, sensors. Main UX risk: Outdated model and false precision. Mitigate it: Timestamp, telemetry and data quality. Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion. Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.
References
Apple (2025). Spatial layout, Human Interface Guidelines. Apple Developer Documentation.Standard or guideline
Supports: Platform guidance for Apple Vision Pro: field of view is the space a person can see without moving their head, and depth is conveyed with cues such as distance, occlusion and shadow.
Does not support: Layout for flat screens, or evidence of outcomes. It is device-specific platform guidance.
Checked 2026-10-25.
W3C Web Accessibility Initiative (2021). WCAG 2 supplemental guidance. W3C WAI.Standard or guideline
Supports: W3C WAI lists supplemental guidance for improving accessibility beyond what WCAG 2 requires, including a cognitive accessibility guidance set.
Does not support: Normative requirements: supplemental guidance is advisory, not required for conformance. This page is an index; a specific recommendation needs the linked document.
Checked 2026-10-25.