StudioX
A scene is the beginning. A workflow makes it useful.
Rendering workflows & platform engineering
Product platform · team contribution
React · Three.js · WebGL · Node.js · MongoDB
From a visual tool to a useful workflow.
A product viewer needs more than a good-looking frame. Camera choices, output settings, feature access, and saved results have to behave as one coherent workflow.
Where I worked.
Worked across the product viewer, configuration controls, and supporting backend.
Implemented feature configuration and access controls, including company-specific rules and real-time plan updates.
Contributed product-type configuration, render settings, and analytics for product and administrative workflows.
The details that matter.
Make captures repeatable
Camera presets are ordered before capture. Each output carries its angle identity, display name, and order, so the result is a useful set rather than a folder of unrelated images.
Keep policy authoritative
The interface responds to plan changes, while backend checks evaluate usage and allowed output formats before an upload reaches storage. A hidden control alone is not an access policy.
Treat rendering as a lifecycle
Capture temporarily changes scene and camera state. The workflow also has to release image blobs, refresh saved outputs, and restore the working view.
A frame is only one step.
Choose the scene, output settings, and ordered camera presets. A repeatable capture starts with a well-defined setup.
Same object. Different decisions.
Change the light and material to see how each affects the form. This is an original real-time study of rendering choices.
Procedural geometry, local lighting, no client models. The study loads only when you choose it.
The interesting engineering sits between the frame and the workflow: making visual tools predictable enough to use repeatedly.
Visit StudioX