SpecsModelExplore
Overview
Actors
External Systems
IoT Platform
Edge
Ingestion
Stream Processing
Device Management
User-Facing Apps
Dashboard Web App
Mobile App
NavigationDevice ScreensAlert Screens
Platform
SpecsModelExplore
Mobile App
OverviewGuideLinks and Communications
IDproduct.user_facing.mobile_app
DescriptionOwner-facing iOS / Android app.
Keymobile_app
Typemicroservice:app
TeamApps
Ownerapps@iotgateway.example
Statusactive
TechnologiesTypeScript, React Native
Attributesframework: React Native, offline: true, platform: iOS + Android
Tags
Table of contents
Guide
Mobile App
Internal structure
Components
Component tree
What makes mobile different
Related workflows

Guide

Mobile App

The Mobile App puts the fleet in an owner’s pocket. It is a React Native app for iOS and Android that lets owners check their own devices, watch live status and react to push alerts — reusing the very same Backend-for-Frontend as the web dashboard.

Same BFF, no second API

The mobile client talks to the Dashboard BFF API — it does not define its own backend contract. One BFF serves both surfaces.

Internal structure

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

Components

Navigation

Tab navigation and deep links into devices and alerts.

Device Screens

View and control the owner’s devices, with offline support.

Alert Screens

Push alerts and the alert history.

Component tree

What makes mobile different

Recently viewed devices and alerts are cached so the app is useful on a flaky connection; writes queue and replay when back online.

Related workflows

Push alerts originate from the alert pipeline:

Owners can act on a device from a screen, which issues a command:

Links and Communications

1 outgoing link

Outgoing Links(1)

Target objectLabelLink typeRelationRaw idRequiredDescription
Notification Provider

example-iot.external_systems.notification_provider

external
receives push from—linksexternal_systems.notification_provider——