Client/Sector: Simam Digital / spatial-authoring product
A browser-based 3D authoring workspace for scenes, transforms, annotations and spatial content.
Project Snapshot
01 Challenge
Creating interactive 3D scenes usually requires heavyweight desktop software and specialised workflows. The product explores how core authoring tasks can move into an accessible browser workspace without reducing the interface to a toy demo.
02 Approach
I organised the tool around familiar creator concepts: scene hierarchy, transforms, primitives, annotations, rendering controls and a timeline. The interface favours compact professional controls because the intended user is actively building, not browsing marketing content.
03 Execution
The working editor supports position, rotation and scale controls alongside image, text, geometry, water and splat-oriented workflows. Versioned UI and dense inspector panels communicate that this is an evolving product surface rather than a static mock-up.
04 Outcome
Simam 3D Studio is one of the strongest demonstrations of frontend depth in the collection. It shows complex application-state design, spatial interaction and the ability to translate desktop-authoring conventions into a web product.
Technical delivery
Simam 3D Studio is an authoring product, which means the difficult work sits in state, selection and persistence—not only rendering a model in the browser.
Objects, parents, transforms, visibility and metadata were represented separately from the viewport so hierarchy and selection could remain consistent. That makes common editor operations—duplicate, rename, reparent, hide or inspect—predictable and creates a route to undo, permissions and collaborative persistence.
Transform gizmos support fast spatial editing, while numeric controls give users a precise and accessible alternative. Selection, hover and camera input needed clear ownership so dragging an object did not accidentally orbit the scene. The UI exposes technical state without requiring the user to think like a game-engine developer.
Annotations, scene settings and object metadata were designed as serialisable project state rather than temporary DOM or render values. That distinction turns a viewer into a foundation for real authoring workflows, including saved revisions, branded outputs and domain-specific tools layered on the same editor core.
Project summary
No. It is presented as a self-hosted Simam Digital product or NDA-safe proof of concept without identifying confidential clients.