01
A dashboard rendering 40k live data points without dropping a frame. Moved the chart layer to WebGL, kept the chrome in DOM for accessibility. Time-to-interactive fell from 4.2s to 1.1s.
2026
Freelance web developer — Melbourne, remote worldwide
Interfaces that move with intent.
I build fast, motion-led front ends for product teams who care how a thing feels, not just whether it renders. Ten years of shipping, and a hard rule: nothing moves unless it earns its frame budget.
- TypeScript
- React
- Svelte
- Next.js
- WebGL
- GSAP
- Canvas 2D
- Motion One
- Tailwind
- Node
- Core Web Vitals
- WCAG 2.2 AA
Selected work
Four builds worth showing.
Each of these shipped to production and stayed there. Case studies cover the constraint, the call I made, and the number that moved.
02
Outdoor gear storefront where product transitions carry across routes. Shared-element motion on a 90KB JS budget. Checkout completion up 18% against the previous build.
2025
03
A type foundry specimen site where every axis is draggable and the preview re-renders at 120Hz. Built the layout engine on measured text rather than CSS guesses.
2025
04
Patient portal rebuilt to WCAG 2.2 AA with a 46-component system. Full keyboard path, screen-reader tested, and motion that respects every reduced-motion preference on the device.
2024
Capabilities
What you can hire me for.
Front-end engineering with a motion specialism. I take the build from design file to production, or drop into an existing team to fix the part that hurts.
01
Front-end builds
Design files to production code. TypeScript, React or Svelte, component systems that survive the second designer.
02
Motion & interaction
Scroll choreography, transitions, canvas and WebGL work. Every effect measured against a 16ms frame budget before it ships.
03
Performance work
Core Web Vitals audits and the follow-through. I find the real bottleneck, fix it, and leave you the trace that proves it.
04
Accessibility
WCAG 2.2 AA remediation with keyboard and screen-reader passes on real hardware, not just an automated score.
How I work
Small team of one, on purpose.
I have spent ten years on the front end, the last four almost entirely on motion. The pattern I keep seeing is the same: a beautiful design file, then a build that feels a half-second behind the user's hand. That gap is where trust leaks out.
So I work directly with whoever made the decisions. No account layer, no handoff telephone. You get the person writing the code in the room where the tradeoff gets made.
-
01
Scope in a week
A paid discovery week: audit, technical plan, and a fixed quote. If we are not a fit, you keep the plan.
-
02
Build in the open
Deployed preview from day one. You watch it come together and redirect early, not at the reveal.
-
03
Hand over clean
Documented components, a performance baseline, and thirty days of support after launch.
0+
Years shipping
0
Projects delivered
0%
Median Lighthouse
0h
Reply time
Contact
Let's build it.
Tell me what you are making and where it is stuck. I reply to everything within a day, including the ones I turn down.