Translucency had a fashionable phase and is now settling into something more useful: a way of encoding layer relationships in interfaces too dense for drop shadows to carry the load.
What it communicates
A translucent surface says two things at once: this is above the content, and the content is still there. In a dense dashboard, that is materially better than an opaque overlay that erases the context a user was mid-way through reading.
The constraints nobody mentions
- Contrast is not guaranteed. Text over a blurred surface must be validated against the worst-case background, not the marketing screenshot.
- Backdrop blur is expensive. On a long scrolling page with several blurred surfaces, it is visible in a frame-time profile.
- It needs a fallback. Not every rendering context supports it, and the opaque fallback should be designed rather than defaulted.
Use it structurally
Reserve translucency for the persistent chrome, meaning navigation, sheets and floating panels, where the layer relationship is the actual message. Applied to every card on the page, it stops encoding anything and becomes texture.
- Visual design
- Depth
- Enterprise
