Skip to content
On this page Definition

Atlas · DS235 · Future / AI: Dynamic Composition

Self-Evolving UI

The system proposes or creates features and reorganizes surfaces during use.

  • Status in 2026: Experimental. Tried in experiments or prototypes.
  • Trend 2027 to 2030: Uncertain (an editorial projection, not a forecast).
  • The term: Known technical term or standard.

Definition

The system proposes or creates features and reorganizes surfaces during use.

Traits

  • mutable composition
  • new workflows

Typical settings: AI workspace, Devtools.

When to use it, and when not

Consider it when the task and motivation match: users of exploratory systems. Typical settings: ai workspace, devtools.

Be careful when the risk below would hurt the main task: loss of predictability and security.

UX risk and how to reduce it

Risk: Loss of predictability and security.

Mitigation and accessibility: Permissions, versioning and rollback.

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.

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
4 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
4 / 5 (1 is restrained, neutral, 5 is highly expressive)
Information density heuristic
4 / 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 "Self-Evolving UI" direction (future / ai, dynamic composition): The system proposes or creates features and reorganizes surfaces during use.
Visual and interaction traits to use: mutable composition, new workflows.
Main UX risk: Loss of predictability and security. Mitigate it: Permissions, versioning and rollback.
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

  1. Google Research (2026). Self-Evolving Systems: Moving Beyond Deterministic Interfaces to Adaptive Generative Interfaces. Google Research publication.Preliminary

    Supports: Introduces the concept of adaptive generative interfaces that expand their own feature sets at runtime through directed synthesis, inferred synthesis and real-time adaptation.

    Does not support: That such interfaces are usable or safe. The page presents a concept, not user outcomes.

    Checked 2026-10-25.

  2. Aljabri, Hijazi, Al-Salamin, Khemaja (2026). AI-MDD Approaches for Generating Adaptive and Intelligent UIs: A Systematic Literature Review. Journal of Advanced Computational Intelligence and Intelligent Informatics, 30.Supported

    Supports: A bibliometric analysis and systematic review that narrowed 3,335 Scopus records to 51 studies and reports rapid growth of research on AI and model-driven generation of adaptive UIs.

    Does not support: That adaptive generated UIs perform better for users. It maps the literature; the abstract read here does not report user outcomes.

    Checked 2026-10-25.