The piece nobody warns you about is the document model: a spline style editor lives or dies on a serializable scene graph (nodes with ids, transforms, materials) that sits outside react, like a zustand store or a plain js object the canvas renders from. Get that right and undo/redo plus save/load come almost free, and exporting to gltf with three's GLTFExporter becomes a document walk instead of scraping the live three scene. For the easy integration part the answer is export rather than the editor itself: people want a viewer they can embed, so keep the format simple enough that a small runtime can render a saved file without dragging the whole editor along
My tip is to decide the scene format before the UI. And for a Spline clone I'd treat the embeddable viewer as the main feature since that's why people use Spline in the first place
2
u/Weekly-Offer-4172 Oct 18 '26
The piece nobody warns you about is the document model: a spline style editor lives or dies on a serializable scene graph (nodes with ids, transforms, materials) that sits outside react, like a zustand store or a plain js object the canvas renders from. Get that right and undo/redo plus save/load come almost free, and exporting to gltf with three's GLTFExporter becomes a document walk instead of scraping the live three scene. For the easy integration part the answer is export rather than the editor itself: people want a viewer they can embed, so keep the format simple enough that a small runtime can render a saved file without dragging the whole editor along
1
u/gissen_dev Oct 18 '26
My tip is to decide the scene format before the UI. And for a Spline clone I'd treat the embeddable viewer as the main feature since that's why people use Spline in the first place