I Will build your React or Next.js front end from a Figma design and connect it to your API

The design is done and the API is ready or nearly ready, but the screens users will see don't exist yet. I build the front end only: your backend, auth provider and hosting stay as they are, and the code goes into your repository. For 14 days after delivery, I fix anything that does not work as we agreed, free of charge.

With Starter you get one screen or page from your Figma file, responsive and typed, with its data coming from your API, or from a mock until the endpoint exists. Standard covers up to five screens wired to your API, with loading, empty and error states and forms with validation. Advanced allows up to twelve screens and adds login screens that work with your auth provider, shared components used across the app, and tests for the main flows.

I follow the design closely: spacing, type scale and colours come from the Figma file. Where a screen has no mobile version, I propose one before building it rather than guessing. Next.js with the App Router is my default; plain React with Vite is fine when you don't need server rendering. For styling I use Tailwind CSS or CSS Modules, whichever your project already has.

I check the result in Chrome, Firefox and Edge on desktop, and in Chrome on a real Android phone.

Two public examples of my front-end work are in the portfolio: a Next.js storefront with filters, a cart and a checkout, and my own bilingual site.

I work in writing only, without meetings. The screens and the endpoints behind them are listed before I start, a preview link shows the work as it grows, and a short progress note comes in the chat every working day.

Steps for completing your project
1. Screen list - I go through the Figma file and your API docs and write down each screen, its states and the endpoints it calls. You confirm the list before any code.
2. Base and shared parts - Project setup or your existing repository, colours and type from Figma, and the layout and components that every screen reuses.
3. Screens and data - Each screen is built to the design and connected to your API, with loading, empty and error states. A missing endpoint gets a mock that is easy to swap.
4. Review round on the preview link - You click through and send corrections in one list. I fix them and show the same link again.
5. Handover - The code in your repository, a short note on the structure and how to run it, and on Advanced, tests you can run before each release.