Interactive front-ends
The interface-as-product build: motion, 3D and interaction that make a product feel considered rather than assembled.
- Architecture
- Interaction design
- Implementation
- Performance budget
Stack
What I reach for
The tools I know well enough to know their limits. Opinionated, but not religious. The right tool is the one the team can maintain after I leave.
Stack
What I reach for
The tools I know well enough to know their limits.
Languages
What I write daily- TypeScript
- Rust
- GLSL
- Python
Frameworks
For the app around the canvas- React
- Next.js
- Svelte
- Astro
Graphics & motion
The reason you hire me- Three.js
- React Three Fiber
- GSAP
- WebGL
- Framer Motion
Platform
To ship it and keep it up- Vercel
- Cloudflare
- Postgres
- Playwright
What I do
Four ways to work together
Mostly contract and fractional-lead. I take a handful of projects a year so each one gets the whole of me.
Creative technology
WebGL, generative and real-time work. The things a normal front-end team looks at and says “we can’t do that here”.
- Shaders
- Real-time data
- Generative systems
- R&D
Design systems
The version of the brand that lives in code, built so the people using it cannot easily make it ugly.
- Tokens
- Component library
- Docs
- Adoption
Prototyping
Fast, convincing prototypes for pitches and product bets, the ones that have to feel real before anyone commits budget.
- Concept
- Working demo
- Handover
- Next steps
Contact
Tell me the problem
What you’re building, when it needs to exist, and roughly the budget. All three, ideally. The third one saves us both a week of dancing around it.
Work
hey@vesper.dev
Based
Amsterdam · remote
Code
github.com/vesper
Writing
vesper.dev/journal