IIoT Mobile App for Industrial Equipment Monitoring

Imagine a production line with 500 vibration, temperature, and pressure sensors. Every second — 250,000 samples. The operator can't monitor everything. They need a mobile app that shows only critical deviations. We build such solutions — from data collection from PLCs to smartphone notifications. Our experience: over 10 years in the Industrial Internet of Things (IIoT), over 50 projects for factories. Without proper architecture, the app drowns in data flow. That's why our first step is designing the data collection and normalization system on edge gateways, then building a reliable real-time transmission channel.

Mobile Monitoring of Industrial Equipment: Key Technical Solutions

Edge Component for Data Collection

The edge component — an industrial gateway (Moxa, Advantech, Siemens IPC) or a custom Linux server — normalizes data from various protocols and publishes aggregates via MQTT or exposes them via REST/WebSocket. For the mobile app, two streams matter: real-time — current values of key parameters, updated every 1-5 seconds via WebSocket; and history — trends over shift, day, week via REST API with pagination and aggregation.

How Real-Time Data Collection Works?

At the equipment level, data is collected by the edge component. It normalizes data from different protocols (OPC-UA, Modbus, MQTT) and publishes aggregates via MQTT or serves via REST/WebSocket.

Sensors → PLC / Edge Gateway → Time-Series DB (InfluxDB / TimescaleDB)
                                         ↓
                                 Backend API (REST + WebSocket)
                                         ↓
                                 Mobile App

Aggregation and Normalization on the Edge Gateway

According to OPC-UA Part 6 documentation, the gateway converts OPC-UA address space into flat tags. For Modbus — register-to-physical-value mapping (e.g., register 40001 = temperature with coefficient 0.1). Aggregation: average, min, max over a 1-second window. This reduces traffic by 10-100 times.

Why Data Collection Architecture is the Main Challenge?

We use Flutter with WebSocket. For reliability — automatic reconnection with exponential backoff.

class EquipmentMonitorRepository {
  WebSocketChannel? _channel;
  final StreamController<EquipmentState> _stateController =
      StreamController.broadcast();

  Stream<EquipmentState> get stateStream => _stateController.stream;

  void connect(String equipmentId, String token) {
    _channel = WebSocketChannel.connect(
      Uri.parse('wss://iiot.factory.com/ws/equipment/$equipmentId'),
    );

    _channel!.stream
        .map((event) => json.decode(event as String))
        .map(EquipmentState.fromJson)
        .listen(
          _stateController.add,
          onError: _handleError,
          onDone: _scheduleReconnect,
        );

    _channel!.sink.add(json.encode({'auth': token}));
  }

  void _scheduleReconnect() {
    Future.delayed(const Duration(seconds: 5), () => connect(_lastId, _lastToken));
  }
}

class EquipmentMonitorBloc extends Bloc<EquipmentEvent, EquipmentMonitorState> {
  StreamSubscription<EquipmentState>? _subscription;

  EquipmentMonitorBloc(this._repository) : super(EquipmentMonitorInitial()) {
    on<StartMonitoring>((event, emit) async {
      _subscription = _repository.stateStream.listen(
        (state) => add(StateUpdated(state)),
      );
      _repository.connect(event.equipmentId, event.token);
    });

    on<StateUpdated>((event, emit) {
      final current = event.state;
      final isAlert = current.temperature > 85.0 || current.vibrationRms > 12.5;
      emit(EquipmentMonitorRunning(state: current, hasAlert: isAlert));
    });
  }
}

WebSocket is 20 times faster than HTTP polling for telemetry delivery. Compare:

Trend and Deviation Visualization

For historical data we use fl_chart (Flutter) or MPAndroidChart. Key optimization: aggregation on the API side. Request to InfluxDB-based API:

GET /api/v1/equipment/{id}/trend?
  parameter=temperature&
  from=2024-01-15T06:00:00Z&
  to=2024-01-15T18:00:00Z&
  resolution=300  # 5-minute aggregation

Response returns an array of 144 points instead of 43,200. The chart draws without lag.

Baseline and Deviations

A useful feature is displaying the baseline (normal range) on the chart. If motor current normally is 12-15A, highlight that zone so the operator immediately sees deviation:

LineChartData buildTrendChart(List<TrendPoint> data, Range baseline) {
  return LineChartData(
    extraLinesData: ExtraLinesData(
      horizontalLines: [
        HorizontalLine(y: baseline.min, color: Colors.green.withOpacity(0.3)),
        HorizontalLine(y: baseline.max, color: Colors.green.withOpacity(0.3)),
      ],
    ),
    betweenBarsData: [
      BetweenBarsData(
        fromIndex: 0,
        toIndex: 0,
        color: Colors.green.withOpacity(0.1),
      ),
    ],
    lineBarsData: [
      LineChartBarData(
        spots: data.map((p) => FlSpot(p.timestamp.toDouble(), p.value)).toList(),
        color: data.any((p) => p.value > baseline.max || p.value < baseline.min)
            ? Colors.red
            : Colors.blue,
      ),
    ],
  );
}

What to Consider During Development?

• Data aggregation — do not transmit raw samples, only aggregates.
• Offline mode — cache latest readings and alerts in local DB.
• Alert escalation — if operator doesn't acknowledge an alert within 5 minutes, notify the supervisor.
• Security — TLS, JWT, device-level encryption.
• Testing — simulate up to 10,000 devices.

To reduce traffic, the edge gateway uses a sliding window: from 25,600 vibration sensor samples, 1-10 aggregates are formed — average, peak, RMS, fundamental frequency.

Development Stages

1. Audit of data sources — protocol analysis and polling frequency.
2. Architecture design — selection of edge component and Time-Series DB.
3. Backend development — aggregation API, WebSocket, alerts.
4. Mobile app development — UI, trends, push notifications.
5. Integration and testing — on real equipment.
6. Deployment and support — App Store / Google Play, monitoring.

What's Included?

• Source code of the mobile app (iOS/Android/Flutter).
• Backend service with API and WebSocket.
• Integration and deployment documentation.
• Repository and CI/CD access.
• Operator training (up to 2 hours).
• 6-month warranty on bugs.

Cost and Timeline

Development of an app for one equipment type with WebSocket and trends takes 4-8 weeks. Full cycle including offline mode and escalation takes 2-4 months. Pricing is individual after analysis of your data sources. Typical savings from implementation amount to millions of rubles annually due to reduced downtime and unplanned shutdown costs. Contact us for a free consultation with an engineer on mobile development.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.