Atlas · DS264 · Future / AI: Ubiquitous Agents

Predictive UI

Predicts the next action or needed data and reduces steps.

• Status in 2026: Active. In current use.
• Trend 2027 to 2030: Rising (an editorial projection, not a forecast).
• The term: Known technical term or standard.

Definition

Predicts the next action or needed data and reduces steps.

Traits

• next action
• autocomplete

Typical settings: ERP, Productivity.

When to use it, and when not

Consider it when the task and motivation match: professionals in repetitive processes. Typical settings: erp, productivity.

Be careful when the risk below would hurt the main task: prediction error and bias.

UX risk and how to reduce it

Risk: Prediction error and bias.

Mitigation and accessibility: Always allow editing and refusal.

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.

• Aljabri 2026 (Supported): Adaptive UI generated with AI and model-driven development.
• 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

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

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 "Predictive UI" direction (future / ai, ubiquitous agents): Predicts the next action or needed data and reduces steps.
Visual and interaction traits to use: next action, autocomplete.
Main UX risk: Prediction error and bias. Mitigate it: Always allow editing and refusal.
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.