SpecsModelExplore
Overview
Actors
External Systems
IoT Platform
Edge
Ingestion
Stream Processing
Device Management
User-Facing Apps
Dashboard Web App
Mobile App
Platform
User-Facing Apps
System at a glance
Surfaces
How the apps talk to the platform
Responsibilities
Related workflows
SpecsModelExplore
User-Facing Apps
OverviewGuideLinks and Communications

User-Facing Apps

User-Facing Apps is the experience layer of the platform. It turns the device twin, live telemetry and alerts into screens that fleet operators and device owners can actually act on — without ever talking to the backend services directly.

Responsibility in one sentence

Present authoritative fleet state and let people act on it — viewing devices, watching live telemetry, triaging alerts and dispatching commands — through a single, app-friendly API.

System at a glance

Could not build diagram for model "example-iot".

Surfaces

Dashboard Web App

Realtime operator dashboard with fleet table, live charts and an alert inbox.

Mobile App

Owner-facing iOS / Android app for viewing and controlling owned devices.

How the apps talk to the platform

Both surfaces share a single Backend-for-Frontend (BFF) owned by the Dashboard Web App. The BFF aggregates registry, telemetry and alert data into view-shaped responses so the clients stay thin.

Responsibilities

  • The operator and owner experience (layout, navigation, auth).
  • The BFF contract that shapes backend data for the UI.
  • Realtime presentation of telemetry and alerts.

Related workflows

Live charts and the alert inbox render the output of the alert pipeline:

Operators issue commands to devices straight from the UI: