Sharing apps

Share the project folder containing project.toml, its entry file, frontend assets, and other required files. The recipient opens it in SpatialStudio.

Prepare the project

Declare Python dependencies in the manifest. Use relative paths for files included in the project. Include any frontend build output your Python app serves.

Run the app from the saved folder before sharing it. Test it on the destination platform if your code depends on platform-specific libraries or paths.

Published apps

Studio can mark an app as published. A published app runs with prepared frontend assets. The recipient does not need the frontend toolchain to rebuild them.

Editing a published app returns it to the development workflow. Its declared build can then run again.

Publishing in Studio does not deploy a website or create a separately signed desktop installer. Distribute the project with Studio, or build your own application packaging around the engine.

Runtime requirements

The recipient needs a compatible Studio release and access to additional Python dependencies. External files, services, and SpatialDrive projects retain their own access requirements.

A Python app with a native engine cannot be hosted as static browser files. Use the npm engine for a browser-only deployment.