Smart Home App Development: Unify Multi-Brand Appliances

A client came to us with a problem: a Samsung washing machine, a Roborock robot vacuum, and an LG refrigerator — each with its own app. Managing three different interfaces is inconvenient, and automating scenarios ("start cleaning after washing") is impossible. We built a unified smart home mobile app that merges devices from different brands and adds scenarios unavailable in official apps. Our solution reduces integration time by half compared to building from scratch, and development cost is individual — you pay only for the brands and features you need. A typical project involves 5–10 devices, and event reaction time can be up to 30 seconds. We use proven APIs and middleware to ensure stable operation even when no official interface exists. This cuts maintenance costs by up to 40% compared to using multiple native apps. Development is on Flutter, providing a single codebase for iOS and Android and speeding up updates. Contact us for a preliminary project estimate.

Smart Home Mobile App Development: How to Unify Multi-Brand Appliances?

Ecosystems and APIs

• Samsung SmartThings — REST API at https://api.smartthings.com/v1. OAuth2 personal access tokens or full OAuth2 flow. Supports washing machines (washerWashingCourse), refrigerators (refrigerationSetpoint), air conditioners. On Flutter: http + dio with Bearer token. WebHook event subscription via subscriptions endpoint.
• LG ThinQ — no official public API. We work through unofficial reverse-engineered libraries (pythinq, thinq2-be) or the Home Assistant LG ThinQ integration as middleware. This is typical for large appliances: manufacturers close the API to prevent third-party access.
• Miele — developer.miele.com, OAuth2, REST API. Manage wash programs, monitor status, push notifications via Miele webhook.
• Bosch/Siemens Home Connect — REST API at https://api.home-connect.com. OAuth2. Supports refrigerators, ovens, washing machines. Sandbox for testing without real devices.
• Xiaomi (Mi Home) — Xiaomi MiIO protocol, UDP, local. The python-miio library is well documented. Roborock/Dreame vacuums use separate local protocols or cloud via MiCloud API.

Smart Home API Comparison

How to Obtain the Room Map from a Robot Vacuum?

Roborock is one of the most common. The official Roborock API appeared recently; before that we used reverse engineering via MiIO. The key feature for vacuums is the room map. The robot builds the map via SLAM and stores it on the device. To get the map: either a proprietary protocol (Roborock S7+: binary format with RLE compression) or via Home Assistant vacuum.send_command with get_map_data. Rendering the map on Flutter: decode binary blob into Uint8List, build a Picture via Canvas. Rooms are colored polygons. Robot position is an icon on top. Obstacles are dark pixels. We use CustomPainter with repaint: ValueNotifier<RobotState>. Starting a room-specific cleaning: POST /api/commands/vacuum/start_room with room ID from the map. The Roborock API passes room_ids as a list of int identifiers.

Step-by-Step Roborock API Integration

1. Register in Roborock Developer and obtain client_id / client_secret.
2. Install the roborock library for Dart or Python.
3. Check device availability via vacuum.discover().
4. Get the map via vacuum.get_map_data().
5. Decode binary data according to documentation.
6. Render the map using CustomPainter.

Monitoring Appliance Status

Washing machine: current program, remaining time, errors. Real-time is not needed — updating every 30–60 seconds is sufficient. Cycle completion notification — via WebHook or polling with status == "finished" check. On Flutter: Timer.periodic(Duration(seconds: 60), (t) => _fetchStatus()) until status != 'idle'. Once cycle ends — FCM push to user and stop timer. Refrigerator: compartment temperature, compressor, door opening (sensor in Samsung SmartThings capability: contactSensor). Push if door open longer than 2 minutes — on backend via Rule-based trigger.

Push Notification Method Comparison

Energy Monitoring

Smart plugs with power measurement (Shelly Plug S, Tapo P110) are an important component for appliances. Power in watts, total consumption in kWh. MQTT publish every 5–30 seconds. Display consumption: line chart via fl_chart (Flutter) or victory-native (React Native). Aggregation by hour/day/month on backend (PostgreSQL date_trunc). We don't pull raw data for the last 30 days into the app — only aggregates, saving up to 80% of traffic.

Experience and Guarantees

Our team has 5+ years of experience in IoT app development, delivering over 30 smart home projects. We guarantee stable integration via official APIs, and where none exist, we use proven open-source solutions with our own enhancements. Our engineers are Flutter-certified and familiar with App Store Review Guidelines (Sections 4.2/5.1) and Google Play rules. Get a project estimate — contact us for a consultation.

What's Included in the Work

• Analysis and architecture design of the app.
• Integration with selected brand APIs (up to 5 brands).
• Flutter app development with custom UI for Android and iOS.
• Backend setup (Node.js/Python) with microservices and MQTT broker.
• Push notification (FCM) and background updates.
• Testing on real devices and debugging.
• Deployment to App Store and Google Play (code signing, provisioning profile).
• Integration documentation and team training.
• Post-launch support (3 months bug warranty).

Typical Pitfalls

Appliance feedback can be unstable. Samsung SmartThings webhook may miss an event on unstable internet. Polling as fallback if no webhook event within >5 minutes is standard insurance. Home Connect API has a rate limit: 100 requests per day per device in trial mode. For production — request commercial access. REST APIs are easier to use than MQTT, but are 10x slower when polling 10 devices.

Timelines

One brand (e.g., Samsung SmartThings), basic monitoring and control — 4–6 weeks. Multi-brand, vacuum map, energy monitoring, automation — 3–5 months. Cost is calculated individually based on brand set and integration complexity. Request a preliminary estimate — we'll calculate within 1 day. Get a consultation for your project — contact us.

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.