A few weeks ago, on a Sunday evening when I clearly should not have been coding but was anyway, I had "Let It Happen" playing with the music video running on my second monitor, more out of habit than actual attention. At some point, for no reason I could immediately explain, I stopped typing and just watched. Purple halos bleeding into a scorched orange background, grain trembling like worn-out magnetic tape, geometric shapes repeating in kaleidoscopic loops. None of it tells a story in the usual sense. There's no character, no arc. And yet I felt something before I could even recall the lyrics. It stuck with me until, a few days later, I landed on the homepage of an electronic music festival built entirely in WebGL, using almost the same visual vocabulary: saturated gradients, pulsing halos, analog noise layered over perfectly smooth digital motion. That wasn't a coincidence of personal taste. It was a visual language I'd already encountered somewhere that, on paper, has nothing to do with an Australian psych-rock project.
An emotion before the reading
That's the question that's been sitting with me since: can an interface create an emotional reaction before the user reads a single word? In "classic" web development, we're taught to think in layers - content first, then structure, then presentation. CSS comes after HTML, both in build order and in how we're taught to think. But perceptually, that's not how it actually works. When I land on a site, I register a chromatic mood before I read the first word. My brain encodes a temperature (warm, cold), an intensity (saturated, muted), a texture (smooth, grainy) within tens of milliseconds, well before any linguistic meaning kicks in. That's exactly what happens with an album cover or a music video: the purple and orange of "Currents" or "Let It Happen" set a mood of drifting, slightly unreal warmth before you've parsed a single note. Color arrives before content. Good web design plays with that same lag between perception and comprehension.
Purple doesn't mean anything, and yet
What fascinates me about this aesthetic - saturated, warm, in constant motion - is that it has no literal meaning. Purple doesn't "mean" anything fixed. There's no universal dictionary of color that says "orange equals nostalgia, purple equals mystery." These are cultural, shifting, context-dependent associations. But inside a coherent world - an album, a website, a brand identity - repeating a palette eventually builds its own language. Across the visuals tied to "Currents," that mix of deep purple, warm orange, and soft-edged halos is never used randomly: it recurs, it stabilizes, and through repetition it becomes recognizable. That's exactly the mechanism behind a web design system: a palette of color tokens that, in isolation, carries no inherent meaning, but that, applied consistently across dozens of screens, eventually becomes a product's visual signature. Stripe has its mesh gradient, Linear has its deep purple on near-black, Notion has its desaturated pastels. None of those colors carry universal semantic weight. Their meaning comes from repetition and context, not from the hue itself.
The web has its own psychedelia
What struck me digging into this parallel is how much of the experimental web - the sites you find showcased on Awwwards, audio visualizers, WebGL shader backgrounds - draws from a visual vocabulary very close to 1960s-70s psychedelic art: fluid shapes, hypnotic repetition, organic distortion, colors that spill past their own edges. That doesn't mean web designers are "copying" Tame Impala, nor that the band draws from the web (most of its visual identity comes from a graphic artist, Robert Beatty, who works on the artwork well before a track is even finished). Both draw from the same larger cultural well: the legacy of psychedelic art, VJ culture, early-2000s audio visualizers, retro-futurist aesthetics. A designer building a shader background animated with looping Perlin noise probably isn't thinking of a specific music video. But the result triggers the same perceptual reflexes: slow organic motion, colors that blend without ever forming a hard edge, the sense of a space that breathes rather than one that's static. It's a shared vocabulary, not a direct lineage.
Grain and imperfection as a choice, not an accident
One detail that keeps showing up in this aesthetic, both musically and visually, is grain. Tame Impala's sound, even produced with thoroughly modern tools, keeps a saturation, a compression, a hiss that evoke analog vintage. Visually, the same logic applies: film grain added digitally, lens flare halos that only exist because someone simulated them in post-production. It's an entirely manufactured imperfection, a constructed nostalgia built with tools that have nothing nostalgic about them. On the web, you see the exact same move over the past few years: noise overlays added in CSS or canvas on otherwise ultra-crisp interfaces, gradients that mimic the grain of an old monitor, animations that are deliberately a bit imperfect rather than running on mathematically perfect easing functions. It's an aesthetic choice pushing back against the hyper-smooth flat design trend of the 2010s. Texture gets added on purpose so the screen doesn't feel too sterile, too digital. The tension between the smooth (a flawless WebGL render, pixel-precise gradients) and the grainy (hand-added noise) creates a warmth that a purely clean render could never achieve on its own.
Color has rules, even when it looks free
Here's a real tension in the craft worth being honest about: this aesthetic relies on saturated colors, on strong chromatic contrast between warm and cool hues, on gradients that play with hue proximity rather than luminance. Web accessibility asks for the opposite: sufficient luminance contrast between text and background, regardless of hue. The W3C's minimum contrast criteria don't care whether purple and orange are "harmonious" in an artistic sense - they measure a luminance ratio. A site trying to recreate a psychedelic mood with mid-tone purple text on a warm orange background has a very good chance of failing a WCAG contrast check, even if the visual effect is striking. That's a genuine trade-off, not a minor detail: either you keep that expressive palette for decorative elements (backgrounds, halos, background shapes) and preserve a neutral, high-contrast reading hierarchy for text, or you accept sacrificing some legibility for atmosphere - which can be a defensible choice on an event landing page, much less so on an interface people use daily. Emotion and legibility aren't enemies, but they rarely pull in the same direction.
Motion finishes what color starts
Color alone doesn't get you all the way there - motion is what makes the whole thing breathe. What sells the mood in a Tame Impala video isn't a single still frame, it's the fact that nothing ever fully stops: the camera drifts, the colors bleed into each other, shapes rotate just slowly enough that you stop noticing them as separate objects and start reading the whole frame as one continuous surface. On the web, this shows up as the difference between a page that simply displays a gradient and a page where that gradient shifts almost imperceptibly over time, or reacts a beat behind your scroll position. Scroll-driven animations, subtle parallax, a hero background that takes ten full seconds to complete one loop - none of it reads as "animation" in the way a bouncing icon does. It reads as atmosphere. The trick, and it's a hard one to pull off, is keeping the motion slow and continuous enough that it never competes for attention with the actual content, while still being present enough that the page feels alive rather than static. Too fast and it becomes a distraction; too slow and you might as well not animate it at all. That narrow band in between is, I think, where most of this aesthetic's effect actually lives.
The limits of the analogy
I want to be clear about one thing: I'm not saying Kevin Parker, who writes, plays, and produces most of Tame Impala alone in the studio, thinks in design tokens or accessibility checklists. That would be absurd. Nor am I claiming that designers of experimental websites have "Currents" on loop while writing their shaders - though it's plausible for some of them. What I'm describing is a retrospective reading, a way of naming a visual vocabulary that crosses several media without any causal link between them. That's the whole premise of this series: looking for correspondences of feeling, not proof of influence. The analogy has a clear limit, and pushing it further than a cultural parallel would be dishonest.
What it changes in how I design
What stays with me from this, concretely, is a question I now ask myself before opening my editor: what's the first sensation, before a single word gets read? Not to justify gratuitous effects, but because I've realized how much color, motion, and background texture communicate intent before a user has read a line of copy. A portfolio, a landing page, even an internal dashboard, has an emotional temperature before it has content. For a long time I treated that as a cosmetic detail, almost a distraction from the "real" work - logic, architecture, performance. I think differently now. Not to the point of sacrificing accessibility or clarity for a gradient that pops, but enough to accept that color is never neutral, even when it looks purely decorative.