Hire a React developer for interfaces that survive their second year
Soham Dang builds React and Next.js interfaces with TypeScript for production applications, including the frontend of a 25+ module platform where every screen has to look and behave like part of one product.
Any React developer can build a screen. The difference shows up a year later, when forty screens exist and each new feature either extends the component layer or forks it.
Most React codebases rot in a predictable way: a component grows three boolean props, then a fourth, then someone copies it rather than adding a fifth. The work worth paying for is the architecture that stops that happening.
Component architecture
Composition over configuration
Components that accept children and slots rather than accumulating boolean flags, so variation does not multiply the prop surface.
Typed boundaries
TypeScript at the seams — props, API responses, shared state — so a rename in one place fails the build instead of failing in production.
A real design token layer
Spacing, colour and type defined once. Twenty-five modules staying visually consistent is a systems problem, not a discipline problem.
Accessible by construction
Semantic elements, keyboard paths and focus management built in rather than retrofitted after an audit.
State, and being sparing with it
Redux for state that is genuinely global — the signed-in user, tenant context, cross-cutting permissions. Local state for everything else, which is most things.
The common failure is putting server data into a client store and then maintaining two sources of truth. Server state is cached, invalidated and refetched; it is not the same category of thing as UI state, and treating it as such causes most of the stale-data bugs in a React app.
Performance
Rendering strategy chosen per route in Next.js: server-rendered where data is fresh and personalised, statically generated where it is not, client-rendered where interactivity dominates.
Beyond that: code splitting so a dashboard route does not ship the editor bundle, image pipelines with responsive transforms and lazy loading, and animation driven on the compositor rather than through React re-renders. At MS Infracon, moving asset delivery to Cloudinary with responsive transforms cut page load time by 40%.
Where React meets 3D
Interactive 3D with Three.js and React Three Fiber, budgeted for the devices that will actually load it. The WebGL product viewer for Gaon Se Ghar Tak targets mid-range Android, which means capped draw calls, instanced geometry and device-tiered quality rather than a demo that only runs on a workstation.
This portfolio is itself a scroll-driven React Three Fiber site, with all scroll state handled outside React so scrolling never re-renders the tree.
Common questions
What React experience does Soham Dang have?
React.js has been his primary frontend framework across all three professional roles since July 2023, including the interface for Avani Business OS, a 25+ module multi-tenant platform, plus Next.js work with Redux and TypeScript at MS Infracon.
Does Soham Dang work with Next.js?
Yes. Next.js is part of his daily stack, used for server-side rendering, static generation and routing where those are the right fit for how a route's data changes.
Can Soham Dang build 3D or WebGL interfaces in React?
Yes, using Three.js and React Three Fiber. He built the 3D product visualisation engine for Gaon Se Ghar Tak, optimised for mid-range mobile devices, and this portfolio is a scroll-driven React Three Fiber application.
Can Soham Dang work with an existing React codebase?
Yes. Extending and restructuring live React applications is most of what the work has been, including performance work on production frontends.