Shipping checklist

Use this checklist before sending a Loom build to QA, a publisher, or players.

Environment

• Unity version matches Supported platforms.
• Target OS and graphics API are supported.
• Loom -> Doctor is green on the development machine.
• CI has Node.js 20+ and npm available to Unity.

UI project

• UI dependencies are installed with npm ci or npm install.
• 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.