Development workflow

Loom is designed around a fast frontend loop while Unity stays the source of truth for gameplay state.

Normal Editor loop

1. Press Play in Unity.
2. Loom starts or reuses the UI dev server.
3. The UI loads in the Loom overlay.
4. Edit .tsx or .css files in the UI app.
5. Vite hot reloads the UI.

For most UI edits, you do not need to stop Play mode.

When to restart the dev server

Use:

Loom -> Restart Dev Server

when you change Vite config, environment variables or dependency versions. This gives the UI a clean connection to the current Unity session.

When to restart Unity

Restart Unity after upgrading the Loom package or replacing native platform binaries. Unity keeps native plugins loaded for the life of the Editor process.

Browser-only UI work

Use Mock mode when you want to work on layout, animation, or visual states without entering Play mode. Mock mode lets designers and frontend developers iterate from the browser with scripted bridge data.

Player builds

In player builds, Loom loads a production bundle instead of the Vite dev server. Read Player builds before shipping.