Application Management

Once application code is ready — developed locally with the CLI and pushed to a Git repository — the next step is registering it in Studio so the platform can build, version, and deploy it to devices. This section covers everything that happens in Studio: connecting repositories, managing builds, deploying through playlists, and removing applications.

Registering an Application

Registration connects the application code to the TelemetryOS platform. In Studio, navigate to Content > Applications > CREATE APPLICATION and choose a connection method.

GitHub Repository is the recommended approach. Authorize the TelemetryOS GitHub App, select a repository and branch, and the platform auto-detects build settings from telemetry.config.json. Every push to the connected branch triggers a new build automatically. See Defining Applications for the full walkthrough and GitHub Integration for detailed setup.

Git Repository works with any Git provider — GitLab, Bitbucket, or self-hosted. Provide the HTTPS URL and authentication credentials for private repositories. The same CI/CD capabilities apply.

ZIP Upload is available for quick testing or environments without source control. Build the application locally and upload the output directory as an archive. See Upload a ZIP File for details.

Build and Deploy

After registration, TelemetryOS clones the repository, installs dependencies, runs the build command, and packages the output. The first version is immediately available for deployment. Build progress displays in real time, and builds typically complete in one to three minutes.

Applications reach devices through playlists. In the Studio page editor, add the application to a playlist page and configure its instance settings in the sidebar. Assign the playlist to devices or device groups, and the content appears on screen.

Each subsequent push to the connected branch triggers a new build. New versions can be deployed to the fleet or rolled back to a previous version instantly.

Version Management

Studio maintains a complete version history for each application. Every successful build produces a new version. You can deploy specific versions to different device groups (production devices on a stable release, test devices on the latest build), compare what changed between versions, and roll back to any previous version with a single click — the change propagates to devices within seconds.

Environment Branching

The Git-based workflow supports environment separation naturally. Connect a develop branch to test devices, a staging branch to QA displays, and main to production. Each environment is a separate application definition in Studio pointed at a different branch of the same repository.

Deleting Applications

Applications can be permanently removed from Studio when they are no longer needed. See Deleting an Application for the process and implications.