| ID | product.user_facing.mobile_app |
|---|---|
| Description | Owner-facing iOS / Android app. |
| Key | mobile_app |
| Type | microservice:app |
| Team | Apps |
| Owner | apps@iotgateway.example |
| Status | active |
| Technologies | TypeScript, React Native |
| Attributes | framework: React Native, offline: true, platform: iOS + Android |
| Tags |
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.
Could not build diagram for model "example-iot".
Recently viewed devices and alerts are cached so the app is useful on a flaky connection; writes queue and replay when back online.
Push alerts originate from the alert pipeline:
Owners can act on a device from a screen, which issues a command:
1 outgoing link
| Target object | Label | Link type | Relation | Raw id | Required | Description | |
|---|---|---|---|---|---|---|---|
| receives push from | — | links | external_systems.notification_provider | — | — |