# Liquid Glass

DS063. Aesthetic: Transparency. Page: https://ui.codeatlas.com.br/atlas/liquid-glass/. Index: https://ui.codeatlas.com.br/llms/atlas.txt

Apple's language of responsive translucent material for floating controls.

- Status in 2026: Established. Documented and in wide use.
- Trend 2027 to 2030: Rising in some contexts (an editorial projection, not a forecast).
- The term: Community or market label, or a descriptive term.

## Traits

- refraction
- glass
- layers

Typical settings: Native apps, Navigation.

## When to use it, and when not

Consider it when the task and motivation match: users of ecosystems that recognize this UI. Typical settings: native apps, navigation.

Be careful when the risk below would hurt the main task: indiscriminate use harms hierarchy.

Audience (a hypothesis about motivation and task, never measured, not a statement about any group): Users of ecosystems that recognize this UI.

## UX risk and how to reduce it

- Risk: Indiscriminate use harms hierarchy.
- Mitigation and accessibility: Restrict to control layers.
- How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.

## Evidence

Indirect: the sources support underlying principles, not a preference for this style.

The sources support the principles that apply to this term. None shows that this style works better or is preferred.

- [E12] Apple (2025). Materials, Human Interface Guidelines. https://developer.apple.com/design/human-interface-guidelines/materials (Standard or guideline). Does not support: Evidence of better outcomes for users. It is the platform owner's design guidance, not a study.
- [E07] W3C Web Accessibility Initiative (2023). WCAG 2.2: How to Meet WCAG (Quick Reference). https://www.w3.org/WAI/WCAG22/quickref/ (Standard or guideline). Does not support: What users prefer or what performs better. A standard says what is required, not what is popular.

## Limits

- The atlas is a broad, living catalogue, not every style that exists. No authority enumerates them, and the classes (movement, aesthetic, design system, layout, pattern, principle) overlap.
- The 1 to 5 scores are relative editorial judgements. They are not results of a study and not a measure of quality.
- An audience is a hypothesis about motivation, task and context. It was never measured and says nothing about any age, gender or other group.
- The sources support underlying principles (visual complexity, legibility, grouping, accessibility, platform conventions). None shows that a particular style works better or is preferred.
- The 2027 to 2030 trend is an editorial projection, not a forecast.
- Terms in the Future / AI category rest on exploratory work, some of it preprints, with no causal validation.

Last reviewed 2026-10-25.

## Heuristic scales

Relative editorial judgements from 1 to 5, not results of a study.

- Visual complexity: 4 / 5 (heuristic)
- Expressiveness: 4 / 5 (heuristic)
- Information density: 3 / 5 (heuristic)

## In our library

- designStyle("default"): CodeAtlas. Solid surfaces, plain paper, neutral shadows, 8px corners. The package default.
- designStyle("liquid"): CodeAtlas Liquid. Liquid glass surfaces, brand mesh, glow and hue-tinted shadows. The former default.
- designStyle("apple"): Apple HIG. System type with tight headings, rounded continuous corners, glass on controls.

## Prompt for your AI

```text
Design this interface in the "Liquid Glass" direction (aesthetic, transparency): Apple's language of responsive translucent material for floating controls.
Visual and interaction traits to use: refraction, glass, layers.
Main UX risk: Indiscriminate use harms hierarchy. Mitigate it: Restrict to control layers.
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.
In @codeatlasdev/ui start from the design-style recipes `designStyle("default")`, `designStyle("liquid")`, `designStyle("apple")` and override only tokens (`--ca-*`).
```