3D web development that runs on the phones people actually own

Soham Dang builds interactive 3D web experiences with Three.js and React Three Fiber, including the WebGL product visualisation engine for Gaon Se Ghar Tak, optimised for mid-range mobile devices.

Most 3D on the web is built and reviewed on a workstation with a discrete GPU, then shipped to an audience holding a three-year-old Android phone. It looks extraordinary in the case study and unusable in the analytics.

The interesting constraint in 3D web work is not what you can render. It is what you can render on the worst device that matters.

How the budget is kept

  • Device tiering, decided at boot

    Particle counts, geometry detail and pixel ratio chosen from hardware concurrency, memory and pointer type — not from a user-agent string.

  • Draw calls treated as a budget

    Instanced geometry and merged meshes, because on mobile the count of draw calls matters more than the polygons inside them.

  • Animation on the GPU

    Movement driven by shader uniforms rather than per-frame JavaScript, so the main thread stays free for the actual application.

  • No allocation per frame

    Reused vectors, colours and matrices. Garbage collection pauses are what turns a smooth scene into a stuttering one.

  • A real fallback

    Reduced-motion users and WebGL failures get a designed static state, not an empty black rectangle.

Where 3D earns its place

Product visualisation, where rotating the thing answers a question a photograph cannot — the case for the Gaon Se Ghar Tak viewer and the Rohtak Shoe Co. storefront.

And scroll-driven narrative, where depth and motion carry the structure of a long page. This portfolio is itself a scroll-driven React Three Fiber application, with all scroll state handled outside React so scrolling never re-renders the component tree.

When to say no to 3D

If the 3D does not answer a question the user actually has, it is a cost — in bundle size, battery and the accessibility work it demands — paid for a first impression.

A dashboard does not need a WebGL background. Saying so is part of the job.

Common questions

What does Soham Dang use for 3D web development?

Three.js and React Three Fiber, with custom GLSL shaders where the effect needs to run on the GPU, and GSAP or Framer Motion for the surrounding interface motion.

Will 3D slow down my website?

It can, and that is a decision rather than an accident. Keeping it fast means device-tiered quality, budgeted draw calls, GPU-side animation, no per-frame allocation, and lazy-loading the 3D engine so it never blocks first paint.

Does 3D work on mobile?

Yes, with a budget. The Gaon Se Ghar Tak product viewer was built specifically for mid-range Android, using instanced geometry, compressed textures and quality tiers chosen from the device's own capabilities.

What about users who can't use 3D?

Anyone with reduced-motion enabled, or whose browser fails to create a WebGL context, gets a designed static fallback rather than a broken or empty region.