Can I vibecode Feather 3D?
NOT REALLY · don't bother3D authoring tools are the category where one-shot builds go to die. An agent will happily hand you a Three.js scene with a transform gizmo and an orbit camera in an afternoon, and it will feel great for about ten minutes. Then you want snapping, a real undo stack, material editing, HDRI lighting that does not blow out, UVs, glTF import that survives weird exporters, and a viewport that stays at 60fps with more than a dozen objects, and you are now writing a DCC app instead of using one. None of that is conceptually hard, all of it is thousands of small interaction decisions plus GPU tuning, and that is exactly what you are paying for here. Build the toy if you want a scene composer for one specific job, not if you want a 3D tool you enjoy opening.
Build a local-only 3D scene composer as a web app. This is a personal tool, not a product. Stack, no substitutions: Vite + TypeScript + vanilla Three.js (latest). No React, no framework. No backend, no accounts, no telemetry, no network calls at all. What it does: 1. Full-window WebGL canvas with an orbit/pan/zoom camera (OrbitControls) and a grid helper. 2. Drag and drop .glb or .gltf files onto the canvas to add them to the scene. Use GLTFLoader and fit the camera to the new object's bounding box on first load. 3. Click an object to select it. Show TransformControls with keyboard shortcuts: W translate, E rotate, R scale, X toggle world/local space, Delete removes the selection. 4. Left sidebar: scene outliner listing objects by name, click to select, double click to rename, visibility toggle per object. 5. Right sidebar: numeric inputs for position, rotation (degrees) and scale of the selection, kept in sync with the gizmo in both directions. 6. Lighting panel: one directional light with intensity, color and a draggable azimuth/elevation, plus ambient intensity. Drag and drop an .hdr file to set the environment via RGBELoader and PMREMGenerator, with an exposure slider. 7. Shadows: soft shadow map from the directional light, plus a toggleable ground plane that receives shadows only. 8. Undo/redo (Ctrl+Z / Ctrl+Shift+Z) for add, delete, transform and rename. Implement it as a plain command stack, do not try to diff the whole scene graph. 9. Save/load the scene as a JSON file: asset filenames plus transforms plus light settings. On load, re-prompt for any asset files it cannot find instead of failing silently. 10. Render button: renders the current view at a chosen resolution (up to 4x canvas size) and downloads a PNG. Also an Export glTF button using GLTFExporter. Explicitly out of scope, do not build these: mesh editing or sculpting, UV tools, material/shader authoring beyond base color and roughness sliders, animation, physics, any AI generation, any multi-user or cloud sync. Deliver: working dev server on npm run dev, a README with the shortcut list, and no .env because there are no secrets. Keep it to a handful of files with a clear scene-state module; do not invent an architecture.
$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR
prompt copied. want to know what dies next week?
new verdicts + top votes, weekly. free. one-click out.
Because the alternative is Blender, and for a large group of people Blender is a cliff. A focused 3D tool that opens fast, gives you sensible defaults and gets a decent render out the other side is worth money precisely because someone else absorbed the tedium of making a viewport pleasant. A DIY composer is fine for a repeated, narrow task like laying out product shots from assets you already own. It is a bad trade if 3D is something you want to actually get better at.
xActual modeling: you can arrange assets, you cannot make them
xA trustworthy undo/redo history across every operation
xMaterial and shader editing beyond a handful of sliders
xViewport performance work: shadows, culling, LOD, big scenes
xWhatever asset library, templates or generation features ship with the paid product
Nothing worth pointing at. That's why the prompt exists.
Can I vibecode Feather 3D?
Not really. Feather 3D's value is not the code: The moat is execution polish: a real-time viewport that feels good is a long grind of small interaction and performance decisions, not a feature you can spec. See the honest breakdown above.
How much does Feather 3D cost?
Feather 3D's pricing is usage-based or varies by plan · One-time $14.99 purchase on the iPad App Store; no subscription. Canonical monthly amount is null..
What do I lose by replacing Feather 3D?
Honestly: Actual modeling: you can arrange assets, you cannot make them; A trustworthy undo/redo history across every operation; Material and shader editing beyond a handful of sliders; Viewport performance work: shadows, culling, LOD, big scenes; Whatever asset library, templates or generation features ship with the paid product. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Feather 3D?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.