Building a Mobile Video Surveillance App with RTSP and ONVIF Integration

When developing a mobile app for IP camera video surveillance, the core challenge is selecting the video stream protocol: RTSP for local cameras, HLS/DASH for cloud, WebRTC for minimal latency. The wrong choice leads to audio desync, high data consumption, or broken push notifications. We'll break down each protocol and show how to implement them on iOS and Android, including motion detection and video recording.

A mobile video surveillance app is a complex integration of network protocols, cameras, and mobile capabilities. Correct RTSP stream configuration determines whether the user sees real-time video. Our team has extensive experience in this domain, with over 50 delivered projects. Our tech stack includes ExoPlayer, VLCKit, FFmpegKit, along with ONVIF integration and custom camera discovery solutions. Pinpoint your case for a tailored solution.

Choosing a Streaming Protocol

For local cameras, RTSP is the typical choice — low latency and wide compatibility. However, implementing it on mobile requires additional libraries.

RTSP: Video Decoding on Mobile

RTSP streams from cameras contain H.264/H.265 video wrapped in RTP packets. Neither iOS nor Android has a native RTSP player. Options:

Android: ExoPlayer with extension-rtsp (Media3 1.0+) is about 2x faster in decoding than VLC for Android SDK (libvlc-android). ExoPlayer handles most H.264 cameras, but with H.265 some RTSP servers may throw SOURCE_ERROR due to non-standard SDP attributes.

iOS: AVPlayer does not support RTSP. Workarounds: VLCKit (functional but binary ~20 MB), FFmpegKit with native FFmpeg compilation (heavier but flexible), or a custom RTSP client on RTP/UDP via Network.framework. The last is labor-intensive but gives full control over buffering and latency.

Why ONVIF is the Standard for IP Cameras?

ONVIF is an international standard for IP cameras (Hikvision, Dahua, Axis, Reolink). Profile S defines GetStreamUri, GetSnapshotUri, PTZ control. WS-Discovery for device discovery on the local network. According to ONVIF Profile S, GetStreamUri returns the RTSP URL for each camera.

// Android: WS-Discovery multicast
class ONVIFDiscovery {
    private val MULTICAST_ADDRESS = "239.255.255.250"
    private val MULTICAST_PORT = 3702

    suspend fun discoverDevices(timeout: Long = 3000): List<ONVIFDevice> {
        val socket = MulticastSocket(MULTICAST_PORT)
        socket.joinGroup(InetAddress.getByName(MULTICAST_ADDRESS))
        socket.soTimeout = timeout.toInt()

        val probeMessage = buildWSDiscoveryProbe()
        val packet = DatagramPacket(
            probeMessage.toByteArray(),
            probeMessage.length,
            InetAddress.getByName(MULTICAST_ADDRESS),
            MULTICAST_PORT
        )
        socket.send(packet)

        val devices = mutableListOf<ONVIFDevice>()
        val buffer = ByteArray(4096)
        try {
            while (true) {
                val response = DatagramPacket(buffer, buffer.size)
                socket.receive(response)
                parseWSDiscoveryResponse(String(response.data, 0, response.length))
                    ?.let { devices.add(it) }
            }
        } catch (e: SocketTimeoutException) { /* normal */ }
        socket.close()
        return devices
    }
}

To obtain the RTSP URL: SOAP request GetStreamUri with WS-Security (Digest auth). The onvif4java library simplifies, but often lags behind current camera firmware — we prefer writing a custom SOAP client on Retrofit with a custom converter.

Multi-Camera Viewing

A grid of 4 or 9 simultaneous cameras is a heavy task. Each RTSP stream requires a separate decoder. On Android with 9 Full HD cameras, we risk exhausting hardware decoders (typically 4–8 per chip); the rest fall back to software decoding, dropping FPS to 5–10.

Solution: For the grid, use MJPEG snapshots via ONVIF GetSnapshotUri, updating every 2–3 seconds instead of full video streams. Full RTSP is activated only when tapping a camera to enter full-screen mode. This balances load and informativeness.

Recording and History: Local and Cloud Storage

Recording clips from the camera to the phone: download via ONVIF GetRecordings or ISAPI (Hikvision). Store locally in MediaStore (Android 10+) or Photos Library (iOS). For cloud cameras, direct MP4 links from the manufacturer's cloud.

Motion detection: either hardware-based (in the camera, events via ONVIF Event Service) or software-based on the mobile by comparing YUV differences between frames. Hardware detection is more reliable — fewer false alarms.

What's Included in Development

• Analysis of camera models and ONVIF compatibility
• Protocol selection and RTSP stream configuration
• Multi-camera grid with MJPEG snapshots
• Integration of recording and motion detection
• Publication to App Store and Google Play
• Technical documentation and team training
• Post-release support (optional)

Step-by-Step RTSP Viewing Implementation

1. Check which protocols your cameras support (RTSP, ONVIF, HLS).
2. Choose a player: for Android — ExoPlayer with RTSP extension, for iOS — VLCKit or FFmpegKit.
3. Configure buffering for minimal latency (target under 500 ms).
4. Test on different cameras and network conditions.
5. For multi-camera modes, implement MJPEG snapshots to conserve resources.

Timelines and Costs

Development of a mobile app with RTSP viewing of a single camera and basic ONVIF control: 4–5 weeks (starting at $5,000). Multi-camera system with WS-Discovery, PTZ control, recording history, and push alerts for motion: 8–12 weeks ($15,000-$25,000). Costs are calculated individually after analyzing your camera models and storage requirements. Using off-the-shelf libraries saves up to 40% of development time compared to building a custom RTSP client. Get a consultation for your project — we'll estimate timelines and costs.

Our experience in video surveillance app development spans over 50 successful projects for Hikvision, Dahua, Axis, Reolink cameras. We guarantee compliance with App Store Review Guidelines (Sections 4.2/5.1) and data security.

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.