Read · INTERFACE / CRAFT
The Glass Looks Real. Does the Interface Make Sense?
Flat, frosted, opaque or translucent: a digital surface earns its place when it tells people what belongs where, what they can do and what deserves their attention.
Give every surface a job before giving it a finish.
In this article
- A material is a rule about relationships
- Apple's opacity slider is a choice, not a verdict
- The same screen, three very different decisions
- A beautiful screenshot is not a legibility test
- Flat design didn't remove material. It changed the vocabulary.
- Give the surface a job description
- The screen owes the user an explanation
- Sources
In one breath
Transparency, blur, and solid surfaces only earn their place when they make hierarchy, action, and changing content easier to understand.
Imagine a music app that places its playback controls over the current album artwork. On one cover, the controls look wonderful: a pale, transparent strip floating over dark photography. Change the album and the cover becomes almost white. The same controls now compete with the image. The design has not changed, but the experience has.
This is a constructed example, not an audit of an existing music app. It points to a problem that screenshots are particularly bad at revealing. A surface can look finished in one frame and lose its purpose when the content behind it moves.
The argument over flat design, skeuomorphism and glass-like interfaces often becomes a contest of appearances. A better question is what the surface is supposed to explain. If transparency communicates that navigation floats above content, it is doing a job. If it makes a control harder to distinguish from whatever happens to be underneath, its visual character is competing with that job.
A material is a rule about relationships
A digital screen is not made of wood, paper or glass. Yet its interface still asks us to understand a kind of material: whether a panel feels fixed or temporary, whether something sits above something else, whether a control is available and whether content continues behind it.
Those relationships can be drawn using a shadow, an outline, a solid fill, a blur, motion or simply enough empty space. The material is the visual behavior of the surface, not the noun we use to describe its appearance.
This distinction matters because flat design and skeuomorphic design are often described as opposites. One reduces decoration; the other borrows cues from the physical world. Neither guarantees clarity. A completely flat text label can be unmistakably actionable when its placement, wording and surrounding pattern are right. A beautifully raised glass button can still leave people wondering whether it is decorative.
In Apple's Human Interface Guidelines for materials, a material is defined through depth, layering and hierarchy. Apple positions Liquid Glass chiefly as a functional layer for navigation and controls, distinct from the content underneath. That guidance gives the current aesthetic debate a useful constraint: the effect should make a relationship easier to understand.
A decorative blur tells you what a designer likes. A functional surface tells you which part of the interface you are using.
Apple's opacity slider is a choice, not a verdict
Apple announced Liquid Glass for its software platforms in June 2025. iOS 26 later offered people Clear and Tinted appearances. With iOS 27, released on September 14, 2026, Apple introduced a slider spanning an ultra-clear to a fully tinted look. Those steps are documented in Apple's iPhone display settings and its September 2026 software announcement.
It is tempting to treat the slider as proof that the original glass treatment failed, or proof that customizable transparency has solved the problem. Neither conclusion follows from the release notes. Apple confirms the controls and their availability; the documentation does not establish how many people found the earlier style difficult, or whether the slider improved task performance.
The more interesting design lesson is that one visual strength does not fit every person and every background. A designer choosing a translucent treatment also takes on the responsibility of deciding what happens when the person wants stronger separation, when the background changes, or when an accessibility setting alters the effect.
Apple's own guidance is unusually specific here: use glass-like effects selectively, keep navigation visually distinct from content, favor more legible treatments where text or busy backgrounds are involved, and test reduced transparency and increased contrast settings. None of that requires copying Apple's styling in a product built for another platform. The principle travels better than the aesthetic.
The same screen, three very different decisions
Return to the imaginary music app. A user opens a playlist and needs to pause playback, skip a track or return to the library. The album artwork may change from a dark portrait to a white illustration. The controls must remain discoverable throughout.
There are several defensible ways to construct the control area:
| Treatment | What it communicates | What needs checking |
|---|---|---|
| Clear overlay | Artwork continues underneath; controls feel lightweight and close to the media. | Whether labels, icons and boundaries remain recognizable over every relevant cover. |
| Frosted or tinted overlay | Controls are elevated but separated from visual detail behind them. | Whether blur and tint maintain contrast across content changes and accessibility settings. |
| Solid control surface | Controls are a stable, distinct operating layer. | Whether the heavier separation crowds out useful artwork or feels unnecessarily dominant. |
These are design alternatives, not a ranked result from usability research. A rich media player may benefit from a carefully adapted overlay. A dense billing or medical-information view may benefit from a more stable background. The right choice depends on the task, content and risk.

Read full figure transcript
Notice what this comparison changes: instead of asking whether glass looks premium, it asks what the person can reliably see and operate. That is the beginning of a design decision rather than the end of a mood board.
A beautiful screenshot is not a legibility test
A product interface is not a single static composition. Content scrolls. Photographs change. A page can switch between light and dark appearances. Text grows. Keyboard focus moves. A person may turn on higher contrast or reduced transparency. A visual material needs to survive these changes without hiding important information.

Read full figure transcript
For web interfaces, the Web Content Accessibility Guidelines 2.2 provide measurable contrast requirements: at Level AA, ordinary text generally needs at least 4.5:1 contrast against its immediate background, larger text 3:1, and visual information needed to identify UI components or their states generally 3:1 against adjacent colors. These are scoped requirements with exceptions, not a claim that every decorative edge must satisfy the same ratio.
The tricky word is immediate. If white text sits on a glass pane above an image, measure its appearance where the letters actually appear—not only against the color value used in the design file. The W3C's image-background failure guidance specifically identifies cases where a variable image destroys the contrast of overlaid text.
Do not conclude that increasing blur automatically makes a surface accessible. Blur may reduce visual noise, while opacity, tint, text styling and the content behind the surface still determine legibility. Test the rendered result in meaningful states.
Motion presents a similar issue. A fluid control that responds to touch can communicate an interaction. Repeating a dramatic transformation after every tap can distract or slow the person down. Apple's motion guidance advises purposeful animation, alternatives for people who reduce motion, and restraint around frequent interactions. The principle is not that motion must imitate physics. It is that motion should help explain cause and effect.
Flat design didn't remove material. It changed the vocabulary.
A plain white sheet, a hard black divider and a sharply outlined input field all communicate something about an interface. They establish regions, boundaries and possible actions without pretending to be objects you can hold.
That remains a strength of restrained visual systems. They can direct attention toward content and avoid making decoration compete with a task. But removing texture is not the same as removing the need for signposting. If every item is equally flat, equally pale and equally quiet, users still have to infer what can be tapped, what is selected, and what sits above the rest.
The failure mode does not belong to flat design or glassmorphism alone. It belongs to unexplained hierarchy. A material gets in the way when it makes the interface's structure less obvious than it could be.
That suggests a useful rule for product teams: give each surface a responsibility before giving it a finish. Content needs to remain readable. Navigation needs to remain discoverable. Temporary feedback needs to stand apart and then disappear. A border, tint or translucent sheet is justified if it helps accomplish one of those jobs.
Give the surface a job description
Before approving an elaborate surface treatment, write one sentence for each visual layer: This surface exists to help people understand ______. Then challenge the result with four questions.
- Hierarchy: What does this layer sit above or below, and can people tell without studying it?
- Action: Which elements are interactive, and does the surface make their boundaries and states clear?
- Variation: What changes when the background, theme, content length, scale or system appearance changes?
- Fallback: What does the experience become when transparency or motion is reduced, or the effect is unavailable?
A good answer may be that the interface should remain fully opaque. That is not a design defeat. It is a defensible outcome when stability is more valuable than visual permeability.
For a quick team review, take one existing component and place it over three backgrounds: the quietest it is likely to encounter, the busiest, and the one with the least favorable contrast. Check the component in its normal, focused, disabled and active states. If the material no longer communicates its role, modify the surface before polishing its appearance. On the web, verify WCAG contrast rather than treating a visual inspection as certification; on native platforms, apply the relevant platform accessibility requirements as well.
This exercise is a proposed GoodScool practice, not a published usability method or a substitute for testing with people.
The screen owes the user an explanation
The imagined music app can keep its elegant floating controls. It may even be better with them. What it cannot rely on is a single flattering album cover to prove the design works.
That is what makes the current fascination with Liquid Glass interesting. It gives designers another expressive vocabulary for depth, motion and hierarchy. But every visual vocabulary can become mannerism when its effects are applied without asking what they mean.
A product does not need to choose between flatness and physical imitation as competing ideologies. It needs to establish where things belong, which actions matter, and what will remain understandable as the screen changes.
The best material is the one the user understands without needing to notice it.
Takeaway and next steps
Give every surface a job before giving it a finish.
Give a surface a job description
Check hierarchy, action boundaries, content variation and accessible fallback over three different backgrounds.
Review the argument ↗Sources and further reading
- Apple — Materials, Human Interface Guidelines. Describes materials as tools for hierarchy and the intended separation between controls and content.
- Apple — Major software updates now available, September 14, 2026. Primary announcement confirming iOS 27 availability and the Liquid Glass appearance slider.
- Apple — Adjust iPhone display and text settings (iOS 26). Official Clear/Tinted display-option documentation.
- W3C — WCAG 2.2 and Failure F83. Contrast rules and risks from image-backed text.
- Apple — Motion, Human Interface Guidelines. Purposeful feedback, motion sensitivity and accessible alternatives.