Repository navigation
App Integration
idadwind edited this page Sep 21, 2026
·
1 revision
- Give the host container a nonzero width and height.
- Create the browser player after the DOM exists; avoid creating it during server-side rendering.
- Keep playback controls and application state in the host application.
- Subscribe to events as needed and unsubscribe when those listeners are no longer used.
- Dispose the player on unmount, including if an asynchronous creation finishes after the host has already unmounted.
Store the scene document separately if users need to save or edit it. getFrame() is evaluated render state, not a replacement for the authored document. Track runtime overrides explicitly if they should become persisted application data.
The optional React Stage consumes the older builder API's frames. To render a JSON SceneDocument in React, create the browser player in an effect using a container ref and dispose it during cleanup.
- Installation and development
- Browser quick start
- Scene documents
- Objects and expressions
- Document field reference
- Complete object reference
- Animation
- All animations and events
- Interaction and multiple views
- Browser player API
- Headless evaluation and validation
- Integration and lifecycle
- Features and limitations
- Publishing Webnim
- Troubleshooting
- Reference files