IoT Device Event Logging in Mobile Apps

The device lost connection, a sensor threw an error, and the log contains 10 million records. We'll show you how to find the needle in seconds. We create IoT event logs not as a simple table, but as a full-fledged tool for incident analysis. Without proper structure and filtering, 99% of data remains unused. Our solution reduces error search time by 40%. In one project with 5 million device events per day, we implemented ClickHouse and cut query time from 3 seconds to 40 ms. Offline caching allowed technicians to view logs even in no-coverage zones — critical for field conditions.

Filtering Events Without Delays

The key to performance is correct event structure and storage choice. Minimum field set: ID, timestamp, severity level (DEBUG, INFO, WARNING, ERROR, CRITICAL), category (connection, sensor, command, firmware), and metadata. For storage we use TimescaleDB or ClickHouse — they are optimized for time series and provide queries in 80 ms even with 10 million records. Compare: regular PostgreSQL at 1 million records takes 2-3 seconds, while TimescaleDB takes 50 ms.

data class DeviceEvent(
    val id: Long,
    val deviceId: String,
    val timestamp: Instant,
    val severity: Severity,
    val category: String,
    val message: String,
    val metadata: Map<String, Any?>
)

Client-side event filtering uses pagination and color coding. The server returns only the required range (default 50 records). The mobile app displays events with intuitive markings: gray (DEBUG), white (INFO), yellow (WARNING), red (ERROR/CRITICAL). Critical entries are always on top. For faster navigation, we use cursor-based pagination instead of offset — it's more stable under frequent new writes.

Future<List<DeviceEvent>> fetchEvents({
  required String deviceId,
  DateTime? from,
  DateTime? to,
  List<Severity>? severities,
  String? searchQuery,
  int page = 0,
  int pageSize = 50,
}) async {
  return _api.getEvents(
    deviceId: deviceId,
    from: from?.toIso8601String(),
    to: to?.toIso8601String(),
    severities: severities?.map((s) => s.name).toList(),
    q: searchQuery,
    offset: page * pageSize,
    limit: pageSize,
  );
}

Importance of Offline Cache for IoT

When connection drops, users must see the latest records. We cache up to 500 latest events in SQLite using drift. Upon reconnection, the client loads new events via the since parameter. This reduces server load and ensures instant response. Offline access is critical for field technicians. Step-by-step implementation:

1. Choose a local DB (SQLite).
2. Create a table with event fields.
3. Define eviction policy (e.g., FIFO up to 500 records).
4. Implement synchronization: client sends since — latest timestamp, server returns new events.

For finer tuning, you can use SQLite WAL mode, which speeds up writes under concurrent access. Also set indexes on timestamp and deviceId for fast lookups.

Comparison of Local vs Cloud Storage

Which Server Storage to Choose?

For mobile solutions with millions of records, TimescaleDB or ClickHouse are 5-10x faster than MongoDB and PostgreSQL. Using TimescaleDB instead of SQLite on the server speeds up queries by 100x at 10 million records. When choosing, consider data model: ClickHouse is better for aggregate analytical queries, TimescaleDB for point lookups.

According to TimescaleDB documentation, time series are stored efficiently via automatic time-based partitioning.

What's Included in the Work

We deliver IoT device event logging turnkey:

• Event structure and API design
• Server-side implementation (TimescaleDB/ClickHouse)
• Client-side logic in Swift, Kotlin, or Flutter
• Push notifications and deep linking integration (Universal Links / App Links)
• Caching and offline mode setup
• APK size optimization via ProGuard/R8
• Documentation and operation manual

The process includes stages: analytics → design → implementation → testing → deployment. During analytics, we clarify logging requirements, choose the stack, and after implementation we perform load testing.

Timeline: 1–2 weeks depending on complexity. Typical project cost ranges from $5,000 to $15,000. Get a consultation to evaluate your project — we'll help you with logging and propose an optimal solution.

Why Choose Us?

With many years of experience in mobile development and over 50 IoT projects delivered, we guarantee stable event logging. Our engineers are Apple and Google certified, using modern approaches: SwiftUI, Jetpack Compose, Flutter 3.x. We've been on the market for many years — a testament to our reliability.

Get a consultation: contact us to evaluate your project.

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.