Web Development#
Developing a client application that embeds a streaming Omniverse Kit App follows a two-phase workflow: first develop and iterate locally, then deploy to Omniverse Kit App Streaming. Keeping the same codebase between phases avoids rework: you only change stream configuration when you move from your machine to the cluster.
Phase 1 - Develop Locally
Start by running your Omniverse Kit App on your local machine and connecting your web client directly to it. Using a local dev server (such as Vite) means every code change is reflected in the browser immediately with no deployment, no cloud credentials, and no waiting for a stream to provision.
This is the fastest way to build and test your UI, messaging, and streaming behavior.
Phase 2 - Deploy to Kit App Streaming
After your client works as expected locally, deploying to an Omniverse Kit App Streaming instance requires only a stream configuration update. Your application code carries over unchanged.
Summary#
You start on your workstation for fast iteration, then reuse the same project against Omniverse Kit App Streaming with an updated stream configuration. Open Local development to begin, or Deploy to Kit App Streaming when you already have a working client.