Spatial scenes built in code, not shipped as files

A kit that generates a Vision Pro scene at load time, so the app does not carry a folder of models.

Category
Developer tools
Who it is for
Developers shipping a visionOS scene who do not want to manage model files.
Possible model
Open source
Difficulty
Hard
Inspired by
RealityHD · RealityHD
Original launch
Watch the launch · Oct 4, 2026

Difficulty is an editorial estimate of technical and operational complexity, not a score.

Startup idea analysis by Startup Ideas. Last reviewed Oct 6, 2026. How we read a launch.

The startup idea

RealityHD’s post is an open-source renderer for RealityKit on Vision Pro. It says trees, rocks, terrain, and props are generated when the app loads, on the CPU and GPU, so the app does not ship mesh and texture files. The film is the evidence of a scene that is code.

The opportunity is not a new headset and not a general 3D suite. It is the scene layer for people already building a spatial app who are tired of asset packs. A founder can keep it open and sell the parts a studio will not write: a specific environment, a way to art-direct the generator, or a check that the scene still runs on device.

Copying a renderer for its own sake puts you next to a free project. The opening is one kind of scene a vertical actually needs.

The problem

Spatial apps get heavy because every tree, rock, and prop is a file someone has to store and update.

Who would pay for this?

Primary
Developers shipping a visionOS scene who do not want to manage model files.
Secondary
A small studio that needs one environment, such as a site walkthrough, and does not have a 3D department.
Early adopter
Someone who already tried to drop asset packs into a RealityKit app and watched the build get heavy.

How could it make money?

Possible models. Nothing here is a claim about what RealityHD charges.

  • The launch says the renderer is free and open source. A company around it would charge for a directed environment, support, or a private generator, not for the free core.
  • No price is in the post. Do not invent one.

What would the MVP look like?

  1. One environment, generated at load.
  2. A few controls a developer can set without opening a 3D tool.
  3. A note of what is not shipped as a file.
  4. Runs on device.

How to validate the idea

  • Build one scene the way the post describes, then the old way with files. Compare the hassle, not a benchmark you have not measured.
  • Show it to three visionOS developers. Ask which asset they would stop shipping.
  • If nobody is shipping spatial apps yet in your circle, this is a tool for you, not a company. Wait until a second person asks.

How to differentiate

  • One vertical scene, such as a building or a landscape, not every prop.
  • Art direction for people who cannot write the shader.
  • Stay on device. A cloud render is a different product.
  • Open source the generator and charge for the preset a studio reuses.

Why this could be interesting now

Spatial apps are still young enough that the asset pipeline is a choice, not a habit. Generating the scene in code is a way to skip a department a small team does not have.

Original product launch

This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. RealityHD did not write it.

Product
RealityHD
Company
RealityHD
Film
RealityHD for RealityKit
Posted
Oct 4, 2026 · 0:38
Open original post

Product that inspired this idea

An open-source renderer for RealityKit on Vision Pro. The post says scenes, trees, and terrain are generated in code, so the app does not ship mesh files.

Posted by @hunter_spatial. Watch the original launch. No separate product site is listed unless the post itself is the source.

  • visionos
  • open-source

Related startup ideas

More developer tools ideas

Looking for more ideas?

The full list is startup ideas for 2026, each one tied to a launch you can watch.

Browse startup ideas for 2026

More developer tool startup ideas