Project Lifecycle

Project lifecycle defines the execution stages of a runtime experience: initialization, setup, entry placement, continuous updates, and session scoping.

Startup Flow

Startup includes project metadata, runtime initialization, and loading of any authored world content. Runtime logic should assume these stages are distinct.

Setup Timing

Project logic should begin only after runtime initialization has completed and required scene content is available. Setup is the correct stage for creating runtime objects, registering callbacks, and connecting subsystems.

Authored Entry Behavior

Authored entry data defines the initial user position and orientation for the experience. Runtime setup should account for this state instead of assuming a default origin.

Frame-Driven Logic

Continuous behavior runs through the update loop after setup. Typical responsibilities include state progression, timers, movement, synchronization, and reactive scene logic.

Runtime Identity

Each running experience has a session identifier used by other runtime systems to scope scene operations, synchronization, and shared state.

Learn More

If developers want the concrete reference details behind this concept page, they can continue with the API docs for Project, ProjectBundle, ProjectMetadata, and API_VERSION.