Skip to content
On this page Definition

Atlas · DS248 · Future / AI: Personalization

Adaptive Density UI

Density adjusted to expertise, screen size and task.

  • Status in 2026: Emerging. Appearing in practice, not yet settled.
  • Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
  • The term: Known technical term or standard.

Definition

Density adjusted to expertise, screen size and task.

Traits

  • comfortable/compact
  • detail

Typical settings: ERP, SaaS, IDE.

When to use it, and when not

Consider it when the task and motivation match: novices and experts in the same software. Typical settings: erp, saas, ide.

Be careful when the risk below would hurt the main task: unexpected change harms memory.

UX risk and how to reduce it

Risk: Unexpected change harms memory.

Mitigation and accessibility: Manual control and persistent modes.

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
2 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
2 / 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 "Adaptive Density UI" direction (future / ai, personalization): Density adjusted to expertise, screen size and task.
Visual and interaction traits to use: comfortable/compact, detail.
Main UX risk: Unexpected change harms memory. Mitigate it: Manual control and persistent modes.
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. Reinecke, Gajos (2014). Quantifying visual preferences around the world. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '14), pp. 11-20.Supported

    Supports: About 2.4 million ratings of the visual appeal of websites from nearly 40 thousand participants: the level of colorfulness and visual complexity at which appeal is highest varies between groups.

    Does not support: Predicting one person's taste from a group label. Group differences in ratings of website screenshots do not justify stereotypes or per-style audience claims.

    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.

  3. 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.