Mobile App for Access Control Systems: Integration & Remote Management

Implementing Access Control System (ACS) Management via Mobile App

Integrating a mobile app with an ACS hits the wall of protocol incompatibility. Controllers like Suprema BioStar, HID OSDP, Ironlogic Z-5R, RusGuard each have their own API and data format. We solve this by creating a unified interface over REST or OSDP v2 that works equally well for iOS and Android. Thanks to this approach, customers save up to 40% on implementation time, avoiding rewriting logic for each controller.

The mobile app handles three critical functions: real-time access event monitoring, remote door control, and flexible access rights management. Without this, security guards are stuck at a console and HR fills out paper forms. With our app, all operations take a few taps, and security incident costs drop by up to 50% due to instant reaction.

Problems We Solve

Event delays. Standard REST API polling every 2-5 seconds misses events during a turnstile rush. We use WebSocket (BioStar 2 supports /ws/events) for a real-time feed. Our delay between passage and event appearance in the app is under 500 ms — 4x faster than polling.

Remote unlock security. Opening a door with a button in the app is convenient but dangerous without protection. An intercepted request can be replayed. We implement HMAC-SHA256 signing with a timestamp, making replay impossible after 30 seconds. Every unlock is logged on the server.

Card and rights management. Manually entering a 10-digit Mifare card number invites errors. We add NFC reading: the guard taps the card to the phone, and the number is picked up automatically. Then selecting doors and time schedules via an intuitive form. Card addition time drops from 30 to 5 seconds, and entry errors fall to zero.

How We Do It: Stack and Integration

For controller integration we use REST API (Suprema BioStar 2, HID Mercury) or OSDP v2 over TCP. In a Kotlin Multiplatform project, the access event structure looks like this:

data class AccessEvent(
    val id: Long,
    val timestamp: Instant,
    val deviceId: Long,
    val doorId: Long,
    val userId: Long?,
    val cardNumber: String?,
    val eventCode: Int,
    val temperature: Double?,
    val imageData: String?
)

The live WebSocket feed is a standard component. Kotlin code using OkHttp:

class AcsEventStream(private val url: String, private val token: String) {
    fun observe(): Flow<AccessEvent> = callbackFlow {
        val client = OkHttpClient.Builder()
            .readTimeout(0, TimeUnit.MILLISECONDS)
            .build()
        val ws = client.newWebSocket(
            Request.Builder().url(url)
                .header("Authorization", "Bearer $token").build(),
            object : WebSocketListener() {
                override fun onMessage(webSocket: WebSocket, text: String) {
                    val event = Json.decodeFromString<AccessEvent>(text)
                    trySend(event)
                }
                override fun onFailure(webSocket: WebSocket, t: Throwable, response: Response?) {
                    close(t)
                }
            }
        )
        awaitClose { ws.close(1000, null) }
    }
}

Why Remote Unlock Security Is Critical

Any door unlock request must be signed and verified server-side. Our implementation on Android/iOS:

suspend fun unlockDoor(doorId: Long) {
    val timestamp = System.currentTimeMillis()
    val payload = "$timestamp:$doorId:${authService.userId}"
    val signature = hmacSha256(payload, authService.apiSecret)
    api.unlockDoor(DoorUnlockRequest(
        doorId = doorId,
        timestamp = timestamp,
        signature = signature,
        reason = "manual_unlock_mobile"
    ))
}

The server checks: timestamp ≤ 30 seconds, signature matches, user has door:unlock permission. Without these checks, an attacker intercepting traffic could replay the request.

How to Integrate NFC for Card Reading

On Android we use NfcAdapter, on iOS — CoreNFC. Tap the card to the phone, the app reads the UID and sends it to the server to bind to the user. This cuts card addition time from 30 to 5 seconds and eliminates input errors.

What's Included in the Work

We deliver not just an app, but a complete package: source code, API integration documentation, server-side access (if needed), admin training, and 3 months of post-launch support. All fixed in the contract, allowing you to evolve the system independently.

Process

Estimated Timelines

An MVP with basic features: event feed, remote unlock, NFC card management — from 4 to 7 weeks. Cost is calculated individually after reviewing the specific system's API and security requirements.

Typical Mistakes in ACS App Development

• No replay protection for door unlock requests.
• Server-side permission checks ignored (client decides what's allowed).
• Long REST polling intervals instead of WebSocket.
• Manual card number entry without NFC.

We have 5+ years of experience developing mobile apps for ACS and over 20 implemented projects for clients in Russia and the CIS. We guarantee correct integration with any API and security compliant with App Store Review Guidelines.

Interested? Get a consultation for your project — we'll assess integration complexity and propose a solution. Contact us to discuss details.

Note: Our team holds iOS and Android development certifications and has hands-on experience with Suprema BioStar, HID, and RusGuard.

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.