Hand a 3D scene to a React developer

The approach

A useful handoff explains what the scene should do and how it fits the application. Decide whether the developer needs a hosted viewer or editable application code. These are different integration choices, and neither removes the need to test the result in the destination project.

Choose the right boundary

Orbital’s publishing panel offers React (R3F) code as well as embed options. A viewer keeps scene playback behind an embed boundary. A React export brings code and assets into the developer’s application, where package versions, asset paths and application state must be reviewed.

Document the expected behavior

Include the opening camera, interactions, background, responsive framing and loading fallback. Name the assets and explain which properties are intended to change. If the developer must connect a scene interaction to business data, write that requirement explicitly instead of assuming exported visual behavior already knows about the app.

A workflow to start with

1. 01

   Choose embed or React export based on the destination requirements.

2. 02

   Export the scene and retain the required assets with clear filenames.

3. 03

   Document the camera, supported interactions and expected mobile layout.

4. 04

   Have the developer test dependency compatibility and application-state integration.

Before you publish

• Asset paths resolve in the target application.
• The application has compatible rendering dependencies.
• Business actions are connected and tested rather than merely described.

Common questions