You have an interaction idea, a feature concept or a Figma flow that needs to be felt, not just looked at. I turn it into a working prototype in React and Motion that you can click through, share with your team and put in front of real people.

Static mockups can't show timing, gestures or what happens when someone changes their mind halfway through an animation. A prototype can. It settles arguments in a design review and gives engineers something concrete to build against.

Product teams testing a new navigation pattern, onboarding flow or gesture-heavy screen

Founders who need a feature pitch that leadership or investors can actually use

Designers whose Figma prototype can't show the interaction they have in mind

Day 1: we agree on the one flow that matters most and the questions the prototype needs to answer.

Days 2 to 4: I build it with real states, real timing and springs that can be interrupted. You get a live link to check progress every day.

Day 5: polish, keyboard and screen reader support, then handover.

What makes it different I'm a design engineer, so the motion decisions are made in code, not handed off. Everything runs in the browser on desktop and phone, and the code is clean enough for your engineers to read.

You can see the kind of work I do in my concept prototypes for Spotify, GitHub, Figma, Google Calendar, WhatsApp and LinkedIn, linked below.