The starter is a local integration example. Use these checks before making a Team-backed application available to other users.
Authorize Work on your server
Use Team API Quickstart for the token → Team directory → selected Work flow. SK and gateway tokens remain on your server. A frontend resource code or saved camera snapshot is not ownership proof.
Add your own user authentication and server-owned resource authorization before hosting the app. The starter binds to localhost and is not a multi-user authorization service.
Handle the assets separately
A valid Work response can still reference unavailable panorama or model assets. Check asset network access, allowed domains, applicable signed-URL lifetimes and the browser's actual rendering result. Do not proxy arbitrary user-supplied URLs to work around an asset failure.
Keep errors attached to their stage
| Stage | Evidence to inspect |
|---|---|
| Authentication | HTTP and business outcome of the server token request. |
| Directory | Authorized list result; empty is valid. |
| Work | Selected resource, parse result and current selection lifetime. |
| Panorama or model | SDK load outcome and the referenced assets. |
| Optional control | Whether this Work supports the requested mode or intersection. |
Never log secrets, gateway tokens, complete private Work, signed resource handles or signed asset URLs in support messages.
Manage browser resources
Keep the renderer client-only, give it a stable sized host, and dispose instances that leave the page. Pause or remove unnecessary offscreen viewers. Test mobile memory use and WebGL availability on your own supported devices; a minimum browser version does not guarantee usable device performance.
Image capture and multiple active scenes allocate additional GPU and CPU memory. Avoid unbounded capture sizes or continuously exporting frames.
Upgrade a tested set
Preserve the lockfile. Check SDK declarations, runtime behavior, peer dependencies, package advisories and the representative browser workflows before changing versions.
Dnalogel, Vreo and Live have their own version constraints. Install the versions listed in the extension guides and preserve their peer dependencies.
Check before launch
Run the public scene and a scene from your Team in the deployed environment. Check loading, navigation, view modes, and access control in the browsers and devices you support.