PRODUCT DESIGNER
WHO SHIPS CODE
Product UI/UX · 3D & Motion · Code
I like the part where you figure it out
I’m a product designer, over twenty years in. I’ve built consumer apps people use every day, the web products businesses actually run on, and the connected devices some of them talk to. Different surfaces, same job: make a complicated thing feel obvious.
I run the research, own the experience end to end, and get to a working prototype in hours. I dig in with React and React Native, do motion and 3D design, and anything else creative I can get my hands on.
Lately I’ve been building the AI tooling my team designs with, including custom skills, rapid prototyping, and using it to generate frontend components and sync with Figma.
Products should be easy to understand at the worst moment, not just their best.

Scott Veltkamp
Lead DesignerFeatured work
Image 1 of 4


Image 1 of 3


Image 1 of 4

Image 1 of 3


Image 1 of 3


What I do
Product design
I own the experience end to end: architecture, flows, interaction and motion. And the states most specs skip: empty, loading, error, offline, first run. Shipped on iOS, Android and the web, often with a piece of hardware on the other end.
User research
Generative and evaluative, and I run it myself. I recruit, write the guide and lead the interviews. Then I code the transcripts against a codebook, with checks on my own bias built in. When I look at competitors I want countable findings, not impressions.
Design systems
I start the component library while the design is still moving, so the two never drift apart. I have built one from Figma into React Native, and built one backwards, rebuilding the components to match screens that already existed. Either way the file and the codebase stay in sync.
Front-end code
I have been writing front-end since HTML and CSS were the whole job. Now it is React and React Native: design system components, screens, animated components and the styling underneath them, alongside the engineers who own the rest. I stay through the build, because the gap between a mock and a shipped screen is where a design gets lost. This site is one of mine: typed components rendered to static HTML, with no framework shipped to the browser.
Motion design
Motion is part of the interface, not a coat of paint on it. I design the transitions and micro-interactions, then either hand them off as Lottie or build them in the app myself. When a product needs a film I make that too, in After Effects.
Industrial design
The app is only half of a connected product. I design the enclosures alongside the software that runs on them: form development and rendered concepts the hardware gets built from. I work in Plasticity and Blender, with plugins I wrote for the repetitive passes.
AI tooling
When the tool doesn’t exist, I build it. A design pipeline that audits its own output and won’t ship a page below the bar. MCP servers that put Canva and FigJam inside the agent. The Claude Code skill my team structures its client work with, one dated decision at a time.

Experience
20+Years
Thirteen of them at Very, designing connected products and the mobile and web apps that run them. Before that, an agency doing web, print, motion and brand, a startup, and four years of freelance web design and development. In all of them I stayed with the work from the first sketch to the shipped build.
















