Application Components

The modular pieces that make up a TelemetryOS application

What are Application Components?

Application components are the modular pieces that make up a TelemetryOS application. Each component handles a specific responsibility, making applications composable, maintainable, and deployable.

TelemetryOS Application Structure

TelemetryOS applications use a mount point architecture with up to four component types:

Core Components

  1. Render - The main UI that displays on physical devices (TVs, kiosks, digital signage). This is what end users see. Learn more in Rendering.

  2. Settings - Configuration interface that appears in the TelemetryOS admin portal for administrators to configure your application. Learn more in Settings.

  3. Workers - Background scripts that run continuously on devices, even when your app isn't visible. Ideal for data sync, monitoring, and scheduled tasks. Learn more in Workers.

  4. Containers - Docker containers for backend services, databases, or complex processing on devices. Learn more in Mount Points.

Additional Platform Components

Beyond the application structure, TelemetryOS provides platform-level components:

  • Content Assets - Media library for images, videos, and other assets
  • Playlists & Schedules - Content sequencing and timing rules
  • Device Management - Device configuration, monitoring, and control
  • APIs & Integrations - External system connections (CMS, data feeds, auth)
  • Permissions - Role-based access control for users
  • Analytics & Logging - Application metrics, health checks, and error reporting

Component Communication

Components communicate through the TelemetryOS SDK:

  • Settings ↔ Render - Via Storage API with instance scope
  • Workers ↔ Render - Via Storage API with application scope
  • Containers ↔ Render - Via HTTP requests to container hostnames

Each component has clear inputs and outputs, enabling independent development, testing, and replacement.

Learn More

For detailed information on application architecture and component configuration, see:


What’s Next