Refined Live: Aesha.Design Joins the Mosaic Showcase

aeshapatel.in was recently featured in the official Mosaic showcase — a look at how the site was built, and why it earned its place there.

Earlier this month, Mosaic featured my portfolio, aeshapatel.in, in their official showcase. Their framing stuck with me: a portfolio positioned as the human answer to AI complexity — warm, illustrative, and built on a clear process.

That description is generous, but it’s also accurate in a way I didn’t fully plan. This site was never meant to look automated, templated, or optimised into anonymity. It was meant to feel like one person made it, cared about it, and kept working on it after launch. Here’s the story behind the build.

An end-to-end project, in-house

Aesha.Design is my own studio — which made this the rare project where I owned every layer: brand strategy, visual identity, the design system, content architecture, and front-end execution. No handoffs, no compromises negotiated across a table. Every decision, and every consequence of every decision, was mine.

That sounds like freedom. In practice, it’s the hardest brief a designer ever takes on. When the client is you, “good enough” is always available and never acceptable.

Built through iteration, not from a spec

There’s a version of this story I could tell where a fully defined design system existed before development began, and the build was just delivery. That version would be tidy. It would also be false.

The truth is more interesting: this site was refined live, in production, one deliberate change at a time.

The hero alone went through several full reworks. The Three.js water-ripple interaction was rebuilt after an earlier version was scrapped entirely. Mouse tracking was rewritten from viewport-relative to element-relative coordinates — a small correction that mattered for accuracy at any scroll position. The header cycled between fixed and sticky until sticky earned its place. Nothing shipped without being tested, and nothing survived if it didn’t hold up. Reverting became as much a part of the process as building.

That’s not indecision. That’s the discipline: small, isolated changes, honest evaluation, and no attachment to work that isn’t working.

Performance as a design decision

Polish that costs the user is not polish. A real-time water simulation in the hero is exactly the kind of feature that quietly wrecks performance if you let it — so it wasn’t allowed to.

Non-critical scripts were deferred. The hero simulation lazy-initialises through IntersectionObserver, so it only spins up when it’s actually on screen — and tears down when it isn’t. That single piece of restraint cut Total Blocking Time significantly. Behind it sits a full technical SEO pass: Schema markup, Open Graph data, structured metadata — the invisible architecture that makes a visual site legible to everything that isn’t a human.

The lesson I keep relearning: the most expressive interactions on a site should also be the most carefully engineered ones.

Why Mosaic

Mosaic’s role in this build wasn’t templating a static design. It was giving a live system room to evolve without breaking, page over page.

That’s the real test of any component-based workflow. It’s easy to look structured when nothing changes. What matters is whether the system holds when you’re stress-testing it constantly — reworking a hero for the third time, swapping interaction models, reverting a header pattern at 11pm. Mosaic was fast enough to iterate in real time and structured enough to keep typography, spacing, and interaction states coherent while everything around them moved.

A builder that only supports finished designs is a rendering tool. One that supports a design system while it’s still becoming itself is a workflow. That’s what made this project worth building in it — and, I suspect, what made it worth featuring.

What the feature actually validates

Being showcased is nice. But what I take from it isn’t the badge — it’s the confirmation that a specific way of working reads from the outside: disciplined iteration over big reveals, systems thinking over one-off screens, and craft that extends past the pixels into performance and structure.

The site that got featured isn’t finished. It never will be — it’s a working system, and working systems keep moving. That’s rather the point.

View the feature: Aesha Patel on the Mosaic Showcase Explore the site: aeshapatel.in