Service
You have a design and no frontend. I turn a Figma file into a working React or Next.js interface — reusable components, accurate spacing, and responsive behaviour that holds on real devices.
A working interface built from your design, as reusable components rather than a pile of one-off screens. Accurate spacing, real responsive behaviour on desktop, tablet and mobile, and a component structure your team can extend without reverse-engineering it first.
My largest contract to date was exactly this work: 203 hours of React development turning a design system into a working social platform interface.
The most common failure is building screens instead of components. Each screen gets implemented as its own block of markup, the same button appears in eleven slightly different forms, and six months later a brand change means editing every one of them. Reading the design for its repeated elements before writing any markup is what separates a frontend you can maintain from one you replace.
The second is treating responsive as an afterthought. A design usually arrives at two or three fixed widths, and every width in between is an unstated decision that someone has to make. I would rather ask what should happen to that table on a narrow screen than guess and have it rejected in review.
The third is silent divergence from the design system. A spacing value that is 14px because it looked right, in a system built on a 4px scale, is how design systems decay. I build against tokens so the implementation and the Figma file stay describable in the same language.
EL-Arca is an accessibility-first discovery platform built to WCAG 2.1 AA — semantic markup, ARIA, keyboard navigation, and a multi-axis filtering interface. TranquiLove is an interactive web app of guided exercises where the interaction design is the product.
NuVisa turns a confusing immigration process into guided multi-step forms, which is the kind of interface where layout decisions and validation states matter more than visual polish.
Conversion work scopes well because the unknowns are smaller than in a product build. Send me the Figma file and I will come back with a realistic component breakdown and an estimate, usually within a day and at no charge.
What changes the number is not screen count but component reuse, how many interaction states the design specifies, and whether the responsive behaviour is defined or needs deciding together.
Send me the Figma file and I will come back with a component breakdown and an estimate, at no charge. The price is driven by component reuse and interaction states rather than screen count — twenty screens built from a tight component set cost less than eight screens that each reinvent their layout.
A small marketing site is days; a full application interface is weeks. For scale: my largest engagement of this kind was 203 hours turning a design system into a working social platform interface. A realistic estimate needs the actual file, because the visible screen count says very little about the work.
Close, and deliberately not obsessively so. I match spacing, type scale and color exactly by building against tokens rather than eyeballing values. Where a design specifies something that breaks at a real viewport width or fails contrast requirements, I will flag it and propose a fix instead of shipping a faithful copy of a problem.
Then we decide it together rather than me guessing. Most designs arrive at two or three fixed widths, and every width in between is an unstated decision. I will come back with specific questions — what this table does at 375px, whether this nav collapses — because getting that wrong is the most common cause of rework.
Either. Tailwind by default because it keeps spacing and color on a token scale, which is what keeps an implementation honest to its design system. If your team already has a styling approach, I match it — an interface nobody on your team wants to edit is not a finished deliverable.
An accessibility-first app-discovery platform for users with special needs — WCAG 2.1 AA-compliant UI with an advanced filtering system.
Read the case study →Psychology-backed digital tools for dating anxiety — interactive guided exercises that help users calm nerves and make steadier decisions.
Read the case study →A UK visa & immigration services platform — guided application flows and multi-step forms that turn a confusing process into a clear path.
Read the case study →A 15-minute call is usually enough to scope it. If I am not the right fit, I will tell you on the call.