Mobile App Development for Smart Home (Electronic Locks/Doorphones)

Mobile App Development for Smart Home (Electronic Locks/Doorphones)

The lock hangs, the API returns 503, the BLE connection fails — the user stands at the door with a dead phone. This is not a UX problem; this is an incident. We design apps for electronic locks and doorphones where every communication channel has a backup. Our experience: 10+ years and 15 projects in the smart home domain. Recently, we solved an issue with Nuki locks on iOS: the app did not receive BLE notifications about the lock state due to incorrect CoreBluetooth background mode configuration. After adding bluetooth-central to Info.plist and using CBCentralManagerOptionShowPowerAlertKey, everything worked. Such details determine reliability. We are ready to evaluate your project in 2 days: contact us, and we will offer a turnkey solution.

How Do We Ensure Reliability When All Channels Fail?

The architecture is built on redundancy. At least two independent ways to open the lock. If the primary channel fails, the user should not call support standing in the cold. Typical channel hierarchy:

1. BLE (local, no internet) — first priority when close
2. Wi-Fi/cloud — if BLE is not available
3. PIN code on the lock — if the system completely fails
4. Mechanical key — physical fallback

The app automatically detects available channels and switches. BLE: check Bluetooth state via FlutterBluePlus.adapterState. No BLE or device is far — try Wi-Fi/cloud. In the UI, show the active channel to the user. Reduce support costs — fewer calls, higher satisfaction.

Why Is BLE the Primary Channel for Fast Opening?

BLE provides latency under 200 ms — 10 times faster than cloud control. Range 5–15 meters, no internet required. Native implementation via CoreBluetooth (iOS) / Android BLE API, on Flutter — flutter_blue_plus. Each lock is a GATT service with its own characteristics. For example, August locks use service UUID 00001523-1212-EFDE-1523-785FEABCD123 with proprietary protocol — no official SDK, we work via reverse engineering or August API.

Protocols and Lock Types

For Wi-Fi Tuya locks, use Tuya Open API: POST /v1.0/devices/{deviceId}/commands with {"commands": [{"code": "switch_1", "value": true}]}. For Zigbee — MQTT command to topic zigbee2mqtt/{device}/set with {"state": "UNLOCK"}. Z-Wave works via Z-Wave JS or Home Assistant.

Comparison of Temporary Access Approaches

Temporary Access and Guests

A key for a guest for 24 hours, for an Airbnb tenant for a week, for a cleaner on Tuesdays from 10 to 14 — this is core functionality. Implementation depends on the lock. Nuki Web API: POST /smartlock/{smartlockId}/auth creates an authorization with allowedWeekDays, allowedFromDate, allowedUntilDate, allowedFromTime, allowedUntilTime. August API: POST /access_codes with access_code type.

For BLE locks without a cloud, a temporary key is a cryptographically signed token with temporal constraints, transmitted via BLE. On the backend, we store all issued keys with metadata (to whom, by whom, expiry, usage list). Push notification to the owner on each use of the guest key.

How to Implement a Video Call from a Doorphone?

Video call from doorphone to mobile = WebRTC + VoIP push. When someone presses the doorphone button:

1. Doorphone publishes an event to MQTT
2. Backend sends a VoIP push to iOS (via PushKit) or FCM with priority: high to Android
3. The app wakes up in the background, establishes a WebRTC connection with the doorphone
4. Shows incoming call UI via CallKit (iOS) or android.telecom.ConnectionService

VoIP push on iOS via PushKit is the only way to reliably wake the app for a video call. Normal push arrives with a delay of 2–30 seconds. PushKit is instant. Requires VoIP certificate in Apple Developer Portal, entitlement com.apple.developer.pushkit.unrestricted-dispatch. On Android, a background service with startForeground keeps the WebRTC connection ready. Starting from Android 14, restrictions on background services have tightened; need ForegroundServiceType.CAMERA + ForegroundServiceType.MICROPHONE in the manifest.

Event Log

Every opening is recorded in the log: who, by which method, at what time. For rental properties, this is legally important. Storage: PostgreSQL with table access_log (id, lock_id, user_id, method, timestamp, result). Index on (lock_id, timestamp DESC). The mobile app requests paginated: GET /api/locks/{id}/access-log?page=1&per_page=50.

What Is Included in Development?

You get the full cycle: requirements analysis and protocol agreement, architecture design with fallback channels, mobile app development (iOS/Android), integration with locks and doorphones via API, push notification setup (PushKit, FCM), testing on real devices, preparation of documentation and user guides. Includes 3 months of warranty support after release.

Timeline and Cost

One lock type (BLE or Wi-Fi/cloud), basic control, temporary access — 6–8 weeks. Multi-protocol, doorphone with video, CallKit/VoIP, log, notifications — 4–6 months. Cost is calculated after determining lock models and guest access requirements. Contact us — get architecture consulting and a preliminary estimate. Order turnkey development — we will offer a solution in 2 days.

Apple PushKit documentation: https://developer.apple.com/documentation/pushkit

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.