When Web Experiences Become the Product: Lessons from the Front

The most interesting conversion optimisation work happening right now isn’t happening in A/B testing dashboards. It’s happening at the component level — in the gap between what browser defaults offer and what users actually need to feel oriented, delighted, and confident enough to act.

Three pieces of web craft published this week make that case sharper than any funnel analysis I’ve seen in a while.

The Humble Search Input Is a UX Liability Waiting to Happen

Bramus Van Damme’s <rich-input> custom element landed quietly this week, and it’s the kind of release that deserves more signal than it’ll probably get. The component replicates GitHub’s structured filter syntax — think artist:"Aphex Twin" or label:"Warp Records" — inside a standard text input, giving users a way to combine free-form queries with precise field-level filters without needing a separate advanced search UI.

This matters more than it looks. On Shopee and Lazada, search abandonment is a genuine revenue leak — users who can’t find what they want in two attempts frequently bail to a competitor. Native search inputs offer no structured filtering affordance whatsoever. Most teams paper over this with dropdowns and sidebar facets, which add layout complexity and perform poorly on mobile. A composable web component that handles tokenised filter input, keyboard navigation, and accessible markup in one drop-in element is architecturally elegant and, frankly, long overdue.

Implementation consideration: <rich-input> is a custom element, so teams need to verify CE support across their target browser matrix — still relevant in parts of SEA where older Android WebView versions linger. Progressive enhancement fallback to a standard text input is non-negotiable if you’re serving tier-2 and tier-3 cities in Indonesia or the Philippines.

Nostalgia as a Design System — Decathlon’s Yestalgia Shows How

Decathlon’s Yestalgia microsite, covered in depth by Quentin Hocdé on Codrops, is a case study in how creative direction and engineering can move in lockstep without either sacrificing intent. The project revives a ’90s aesthetic — not as a retro gimmick, but as a deliberate brand positioning tool — through art direction, scroll-driven animation, and interaction design that earns its complexity.

The strategic insight here isn’t the nostalgia itself. It’s that Decathlon used a standalone digital experience to make an emotional claim about brand heritage that product pages structurally cannot make. This is the web experience as brand investment, not as conversion funnel — and that’s a legitimate choice when the goal is repositioning perception rather than driving immediate purchase.

For digital teams in Southeast Asia, this is worth thinking about carefully. Thai and Vietnamese consumers in particular have strong affinity for brand storytelling tied to heritage and authenticity. A Shopee store page cannot carry that weight. A purpose-built experience — even a lightweight PWA — can. The question is whether your performance budget allows for the animation payload Yestalgia deploys. Scroll-driven animations built on the native CSS Scroll Timeline API are significantly lighter than JavaScript-driven equivalents; that’s the technical path worth taking if you’re going down this road.

---

Resn’s Anti-Boring Manifesto Is Actually a Performance Argument

New Zealand studio Resn published a candid piece this week about their philosophy — combining brand, content, and technology with what they describe as “a healthy disregard for boring websites.” It reads like a creative manifesto, but buried inside it is a sharp technical argument: the web is capable of experiences that are genuinely surprising, and the reason most of them aren’t is a failure of ambition, not a failure of tooling.

From a performance engineering standpoint, I’d frame it differently. Boring websites are often slow websites in disguise — teams that default to template-heavy CMS builds and off-the-shelf component libraries aren’t just making aesthetic compromises, they’re shipping unnecessary JavaScript, unoptimised render paths, and layout architectures that punish mobile users. The sites Resn builds tend to be bespoke, which means every animation, every interaction, every asset load is considered. That intentionality has a performance dividend.

The practical lesson for growth teams isn’t “hire a creative studio.” It’s: audit whether your current web stack is making you boring by default. If your CMS is forcing you into a render architecture that scores 45 on mobile Lighthouse, you’re not just losing aesthetics points — you’re losing conversions. Google’s own data consistently shows that moving from a 3-second to a 1-second mobile load time can lift conversion rates by up to 27%. Resn’s work is a prompt to ask whether your tooling constraints are actually tooling constraints, or just untested assumptions.

What These Three Signals Add Up To

Taken together, this week’s web craft output points somewhere consistent: the distance between a functional website and an effective one is increasingly measured in component-level decisions, not page-level strategy. A structured search input that reduces friction. A scroll experience that earns emotional investment. A performance architecture that doesn’t punish ambition.

None of these are silver bullets. <rich-input> requires thoughtful integration and fallback planning. Scroll-driven animation campaigns need performance budgets and stakeholder alignment before a single frame is keyframed. And “don’t be boring” is useless advice without a technical plan behind it.

But the direction is clear. The teams pulling ahead in digital experience quality right now are the ones treating web engineering as a strategic lever — not a delivery mechanism.

Key Takeaways

• Drop <rich-input> into your evaluation backlog for any search-heavy product interface, but validate browser support against your actual Southeast Asian user base before committing.
• If you’re planning a brand storytelling microsite, build on native CSS Scroll Timeline for animation — it’s lighter, more composable, and won’t torch your Core Web Vitals.
• Run a Lighthouse audit on your mobile experience before your next creative brief — if you’re scoring below 60, the performance problem is the conversion problem.

---

The deeper question worth sitting with: as web components mature and CSS gains more native animation capability, the tooling excuse for boring, slow experiences is quietly disappearing. What’s your team’s honest reason for not closing that gap?

---

At grzzly, we work with digital and marketing teams across Southeast Asia on exactly this intersection — where engineering decisions become growth decisions. Whether it’s performance audits, component architecture, or building the case internally for a bespoke web experience, we’re in that conversation regularly. Let’s talk