Interfaces, APIs, shops, motion, and keeping pages fast. Each capability points at a build already written up on the work page.
Same person on the interface and the data when the product needs it — maintainable, documented, and handed over as a real build, not a demo.
A React or Next.js front end, a Node.js API, and a database — SQL Server, MongoDB, or Supabase. Same person on both sides, so the interface and the data model don't drift apart.
React, Next.js, TypeScript, and Tailwind. Component systems, responsive layout, accessibility, and motion — the kind of interface work that has to hold up on a phone in a shop as well as on a desktop.
Auth, server logic, and database work in Node.js and Express. SQL Server, MongoDB, or Supabase depending on the product. Used on live dashboards and order flows, not only on demos.
Catalogues, carts, checkout, and the screens needed to run them. Stripe when payments are involved; Sanity or SQL Server for the catalogue, depending on whether the shop needs a CMS or a real database.
Scroll-driven pages, GSAP timelines, and WebGL scenes in Three.js / React Three Fiber. The Zentry study and this site's 3D studio are the current examples.
Rendering strategy, image and font delivery, bundle size, and the work the browser has to do before first paint. I treat this as part of the build, not a pass at the end.
Tell me what the product has to do. I'll tell you whether I can take it — reply from the person who would write the code.
Talk to me →