Crispwave is a small remote-first studio designing WebGL landing pages, 3D product configurators, scroll-driven brand stories and motion-first interfaces. We treat the browser like a canvas — and the user's attention like a finite, expensive thing.
Five overlapping practices — every project we ship usually borrows from at least three of them. We do not chase trends; we keep deepening a small set of techniques until they feel inevitable.
Real-time 3D viewers where users rotate, customise, recolour and step inside the product. We build them for fragrance bottles, furniture, hardware and apparel. Every configurator ships with mobile-first geometry budgets, baked lighting, lazy-loaded variants and a graceful 2D fallback when GPU memory is tight.
Long-form narrative pages where scroll is the timeline — copy, imagery and 3D scenes choreograph together as the user moves down the page. We design these like films: storyboard first, transitions earned, no scroll-jacking. Smooth scroll is opt-out and reduced-motion is respected end to end.
A single page that has to do the work of a campaign — a shader-backed hero, an interactive logo moment, a generative texture that ties the brand together. We build these in tight 4–6 week sprints with measurable performance budgets and a documented art-direction reference so the brand team can extend later.
Interface motion systems: how navigation reveals, how cards stagger in, how state changes feel. The boring 95% of a site that has to feel as crafted as the hero. We document timing curves, build a motion token system, and pair the visual choices with measurable interaction latency budgets.
End-to-end brand websites where interaction is the lead voice. CMS, content model, copy direction, motion system and shipping pipeline — all built together. These run 10–14 weeks and produce both a live site and a documented motion system the brand can extend internally without us in the room.
Four pieces from the last twelve months, each picked because it solved a different kind of problem. NDAs prevent some logos here — the work is real and references are available on a call.
Their lookbook turned into a navigable garment hall — each piece a draped cloth simulation the user could orbit, with copy panels drifting in on scroll. We collapsed twelve pages of brand content into a single sustained scroll, lifting time-on-page from 38 seconds to four and a half minutes. The whole site weighs less than a single hi-res campaign image used to.
Users compose a bottle — cap, glass tint, engraving, label — and watch the result rebuild in real time with refracted glass and accurate liquid. Built around a single 3.2MB GLB with material variants, instanced caps and a custom envelope shader for the perfume itself. Mobile holds 55fps on a 2021 iPhone with the bottle, the room and the reflections all active.
A 92-page PDF turned into a 14-minute scroll narrative — emissions graphs grow, satellite imagery dissolves, a globe rotates through the year as the user moves. We treated every section like a film beat: storyboarded in Figma, timed in Theatre.js, then re-cut after a live read-through with the fund's communications team. The report still pre-renders cleanly for press indexing and email previews.
Each project page is generated from the building's own floor-plan — points, lines and shadows reshuffle into a unique abstract piece for every visitor. The architect wanted "a portfolio that designs itself" — we built a small generative system seeded by URL so every share link produces a different but reproducible composition. The whole site is 84KB of JavaScript and reads beautifully on a five-year-old Android.
Four phases, deliberately small. We prefer one shared live prototype over fifteen Figma frames — most decisions are easier to make once you can scroll through the actual thing on your phone.
We start with a 90-minute call: brand, audience, the specific feeling you want the user to leave with. We map references, look at the existing site and pull out the one or two moments that have to land harder than the rest. By the end of the week you have a short written direction with three possible creative tracks and an honest read on what is actually buildable inside your timeline.
We translate the chosen direction into a scene-by-scene storyboard — Figma frames annotated with motion notes, scroll beats and interaction states. Copy goes in at this stage so we are choreographing real content, not Lorem Ipsum. You get a Loom walkthrough of the storyboard with our voice on it, so internal stakeholders can see the intent without needing us in the room.
Within ten days you have a working URL — a real, scrollable, interactive prototype hosted in CodeSandbox or StackBlitz. It runs in your browser, on your phone, in front of your team. We iterate live on it, sometimes pairing on a call while we adjust easing curves and shader parameters together. This is where most of the surprises happen, and where we are happiest having them happen — early, in code, not on launch day.
We harden the prototype into a production build, wire it into your CMS, run it through real-user performance testing on mid-range devices, and document the motion system so your in-house team can extend it. Launch day is uneventful by design. We stay on for two weeks post-launch to tune anything that surfaces in real traffic.
A small, public lab where we try ideas that may or may not turn into client work. Some of these end up shipping inside a project six months later. Some quietly die. Both are useful.
A compute-shader experiment pushing 200k vertices through a noise field on a 2020 mid-range phone. Currently holding 90fps and looking for an excuse to ship.
Read more →Driving variable font axes — weight, width, optical size — directly from scroll position to turn typography into the lead animated element of a page.
Read more →A field of small canvas tiles that reorganise themselves around the cursor, producing a different composition every second. Lightweight, no WebGL, surprisingly hypnotic.
Read more →We use roughly the same dozen libraries across every project. Mastery beats novelty — when something here is genuinely beaten by a new tool, we will swap it. Until then we keep getting faster with these.
Short, repeated out loud often enough that they show up in our pull requests. We will defend any of these on a call.
Three notes from creative directors and founders we have shipped with recently.
If your question is not here, the short version is: yes, probably, and we will tell you honestly if not.
Yes — when it is budgeted for mobile from day one. We treat mobile as the design baseline, not an afterthought: tight texture sizes, instanced geometry, suspended scenes off-screen, and conservative pixel ratios. If a scene cannot hit 45+ fps on a mid-range Android, we redesign it before we polish it.
All of our shipped sites pre-render or server-render the actual content — copy, metadata, structured data — so search engines index real text, not a hydrated shell. WebGL stays decorative on top of crawlable HTML. We have shipped immersive sites that rank in the top three for their target terms.
Almost every project we run is shared with a brand designer or in-house creative team. We take the visual system you already have and translate it into motion, depth and interactivity — we are not a replacement for brand identity work, and we are happiest when the brand thinking is already sharp before we arrive.
We ask two questions on the first call: does the story benefit from a physical metaphor, and will the audience linger long enough to reward the load? If neither answer is yes, we recommend motion and shader work instead of full 3D. We have talked clients out of 3D more times than into it — that is part of what you are hiring us for.
Default targets are sub-2.5s LCP on a throttled 4G connection, under 250KB of JavaScript before interaction, and 60fps interaction on a 2020 mid-range phone. We instrument every build with real-user metrics from day one and reject features that cannot fit the budget — including our own.
Yes — most clients keep a small monthly retainer with us for seasonal motion refreshes, new scroll chapters, campaign micro-sites, and gentle re-tuning of the interaction system as the brand evolves. It is a quieter, calmer relationship than the build sprint, and usually the most productive part.
Even if it is just a Pinterest board, a rough launch date and a vague feeling — that is enough to start. We reply within one business day with an honest read on scope, fit and timing. Fixed price, no surprises — figured out on the intro call.