Skip to main content
Mohamed Noor

Services

Two ways to work with me

What each track delivers, and how a project runs from the first call to handover.

  • Figma to production Next.js

    Founders, designers, and small agencies with a finished design file and no front-end capacity.
    Typical timeline
    One to three weeks for a typical marketing site

    A finished design file becomes a responsive, accessible Next.js site that matches the design, loads fast on a mid-range phone, and is straightforward to edit afterwards.

    What you get

    • Pixel-accurate build of every screen and state in the file
    • Responsive behaviour at mobile, tablet, and desktop
    • Accessible markup: landmarks, heading order, keyboard operation, AA contrast
    • Core Web Vitals within target on mobile
    • A typed content layer so copy changes need no code changes
    • Deployment plus a short handover walkthrough

    How it runs

    1. Read the file

      Walk the design and list every screen, state, and breakpoint, including the ones the file implies but does not draw.

    2. Build the system first

      Tokens, typography, and shared components before pages, so the site stays consistent as it grows.

    3. Screen by screen

      Each screen goes to a staging URL as it lands, so you review the real thing rather than a screenshot.

    4. Fidelity and performance pass

      Side-by-side check against the design, then Lighthouse and a keyboard pass before handover.

  • Healthcare and fintech platforms

    Technical founders and product leads building a regulated product on React, Node, and Postgres.
    Typical timeline
    Four to twelve weeks, depending on scope

    Front end and API work for products handling sensitive data, where access control, auditability, and a real testing story are requirements rather than nice-to-haves.

    What you get

    • React and Next.js front end against your design system
    • Node API endpoints with input validation at every boundary
    • Postgres data modelling and migrations
    • Role-based access control and audit logging
    • Handling rules for personal and health data, documented
    • Test coverage on the logic that matters, wired into CI

    How it runs

    1. Model the domain

      Agree the entities, the roles, and who is allowed to see what, before any screen is built.

    2. Thin slice first

      One real flow end to end, from database to interface, so the architecture is proven early rather than assumed.

    3. Build in reviewable pieces

      Small pull requests against a running staging environment, each one demonstrable.

    4. Hand over

      Written architecture notes, environment setup, and a walkthrough with whoever maintains it next.