Selling a new product in a new paradigm
Web3 authentication was a genuinely new concept — even for developers who were familiar with Stytch. Vessel needed to do two things at once: communicate what a web3 wallet actually was and why it mattered, and make Stytch's specific approach feel like the right choice in a noisy space.
The visual language of web3 at the time was maximalist and complex — layered, interconnected systems that felt intentionally overwhelming. The challenge was to reflect that energy without losing legibility.
The brief
Create an entirely web3-native landing page to sell Vessel — Stytch's approach to web3 authentication. The page needed to feel at home in the web3 ecosystem while clearly communicating the product's value to developers evaluating it for the first time.
I owned the entire project: concept, visual design, illustration, and implementation.
Custom illustration to mirror web3 complexity
Rather than using stock imagery or generic crypto visuals, I created original illustrations that mirrored the visual density of web3 systems — interconnected nodes, layered networks, and fluid structures that felt alive and technical at the same time.
The illustrations weren't decorative; they were the core communication mechanism for what a wallet does — connecting identities, credentials, and chains in a way that a paragraph of copy couldn't.
Parallax scroll animation
I implemented parallax scroll animation across the illustrations to make the system feel dynamic — as if the infrastructure was running while you scrolled through it. This was a deliberate choice: web3 is always-on and always-moving, and the page needed to feel that way too.
Designed and built end to end
Due to engineering constraints, I implemented the entire page myself — building it in Webflow with significant custom work by hand. The animation, layout, and interaction all required going beyond what the tool provided out of the box.
The project extended well beyond typical design scope: concept, branding, illustration, motion, and front-end implementation were all owned by me from start to launch.
