Shipping Shipping checklist
Shipping

Shipping checklist

A final checklist before releasing a Loom UI in a player build.

Environment

  • Unity version matches Supported platforms.
  • Target OS and graphics API are supported.
  • Tools > Loom > Doctor is green on the development machine.
  • CI has Node.js 22 or 24 LTS and npm 10 or 11 available to Unity.

UI project

  • UI dependencies are installed with npm ci or npm install.
  • Tools > Loom > Sync UI Dependencies was run after the last Loom package upgrade.
  • The UI app builds successfully with npm run build.

Bridge

  • State values are initialized before Loom starts.
  • Large collections are not pushed every frame.
  • UI-triggered operations are actions.
  • One-shot visual reactions are events.
  • Mock data still matches the generated bridge types.

Player build

  • Assets/StreamingAssets/Loom/index.html exists after the build.
  • The player starts without a blank UI.
  • Main menu, HUD, pause, loading, and error states were tested in a player.
  • No workflow depends on the Vite dev server in a shipped build.

Debuggability

  • Known failure states have user-facing UI.
  • The Unity log is captured for QA and CI builds.
  • Common problems are documented for the team in Common problems.
Loom documentation

Search docs

Esc

Type a word or phrase to search the documentation.

Type a word or phrase to search the documentation.