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.
- Required
Tools > Loom > Doctorchecks pass 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 ciornpm install. Tools > Loom > Sync UI Dependencieswas 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.
- Mock data still matches the generated bridge types.
Player build
Assets/StreamingAssets/Loom/index.htmlexists 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
- Failed actions and loading errors show a message or recovery option.
- The Unity log is captured for QA and CI builds.
- QA knows where to find the logs and troubleshooting steps.