People search React development and TypeScript when they want a product UI that a team can keep, not a JavaScript soup. This landing is production React + TypeScript: typed components, data fetching, forms, auth, and a Node.js API when you want one owner. The parent web applications page is the whole cluster (dashboards, integrations, tests). Astro marketing sites are Astro websites—different rendering model, same TypeScript discipline.
I default to explicit types, small deployable increments, and tests on money/auth paths. I do not start greenfield on an abandoned Create React App template. Next.js appears when the brief truly needs that router and hosting model; many internal tools are happier as Vite + React or as an Astro island. Be honest in discovery.
Examples: nextevents, employment_cal, dashBoard, localization-dashboard. Adjacent: admin panels, REST API, personal accounts.
Out of scope: rewriting a healthy Vue app “because React is trendy,” or pixel-perfect design without a designer when you said you have none—then we ship a clean functional UI, not a Dribbble clone.
Timeline: a focused React app MVP is often 4–8 weeks. Joining an existing codebase starts with a read-only audit.
What you get
- Stack choice in writing (Vite/React, Next, or hybrid)
- UI + API slices you can click every 1–2 weeks
- Typing, lint, CI on the paths that pay for themselves
- Handoff notes and optional pairing
