Precise Object Finding with UWB: From Tracker to Mobile App

An engineer on a construction site lost an expensive laser rangefinder among tons of rebar and equipment. A standard Bluetooth tracker showed a radius of 15 meters but not the precise direction. He had to dig through the entire warehouse. After implementing a UWB tracker with 10-centimeter accuracy, losing tools ceased to be a problem. We executed such a project for a client in industrial safety — fully turnkey: from tracker firmware to a mobile app for iOS and Android. Experience shows that UWB finding reduces the time to locate items by 90%.

UWB (Ultra-Wideband) uses short pulses to measure distance via Time of Flight (ToF) with nanosecond precision. A phone with a U1 chip and the tracker exchange signals, calculating not only distance but also angle of arrival. This yields an arrow pointing to the object. The foundation is the IEEE 802.15.4z standard, described in Ultra-wideband.

How does precise UWB object finding work?

A UWB session on a mobile device is initiated via Bluetooth Low Energy: the tracker transmits its identifier and keys. Then a UWB connection is established, and data exchange begins at up to 60 Hz. Distance is calculated from signal propagation time; direction is derived from phase differences across antennas.

Why implement UWB finding now?

Bluetooth trackers provide only approximate distance, while UWB delivers accuracy up to 10 cm and direction. For industrial sites, hospitals, warehouses, this means up to 40% budget savings on locating lost equipment. Our clients report that inventory time is cut by three.

Two scenarios: Find My network vs standalone UWB

Standalone UWB approach is 2-3 times faster to deploy than integration into Find My Network, due to the absence of MFi certification. For B2B segments (warehouses, construction, hospitals), this is the preferred solution.

iOS: Implementation via NearbyInteraction

On iOS, the key framework is NearbyInteraction. It provides NINearbyObject objects with distance and direction. Here is a typical session example:

import NearbyInteraction
import CoreBluetooth

class ItemFinderSession: NSObject {
    private var niSession: NISession?
    private var currentDistance: Float = 0
    private var currentDirection: SIMD3<Float>?

    func startFinding(accessoryToken: Data, bluetoothId: UUID) {
        niSession = NISession()
        niSession?.delegate = self
        niSession?.delegateQueue = .main

        let config = NINearbyAccessoryConfiguration(
            accessoryData: accessoryToken,
            bluetoothPeerIdentifier: bluetoothId
        )
        niSession?.run(config)
    }
}

extension ItemFinderSession: NISessionDelegate {
    func session(_ session: NISession, didUpdate nearbyObjects: [NINearbyObject]) {
        guard let obj = nearbyObjects.first else { return }
        
        if let distance = obj.distance {
            currentDistance = distance
            // Update UI: distance to object
            updateDistanceDisplay(meters: distance)
        }

        if let direction = obj.direction {
            currentDirection = direction
            // direction — unit vector in ARKit coordinate space
            // direction.x: left-right, direction.y: up-down, direction.z: forward-backward
            updateDirectionalArrow(direction: direction)
        }
    }

    func session(_ session: NISession, didUpdateAlgorithmConvergence convergence: NIAlgorithmConvergence, for object: NINearbyObject?) {
        // convergence.status: .converged / .notConverged([reasons])
        // When notConverged — ask user to move the phone
        handleConvergence(convergence.status)
    }
}

A critical aspect is convergence.status. If the user stands still, direction is not delivered. In our project, we added animation and a voice prompt "move the phone" — this reduced the initial detection time to 2 seconds.

What defines UX: algorithm convergence and feedback?

The UWB algorithm requires movement to determine angle. We implemented combined indication: distance displayed large, direction as an arrow. At distances below 0.3 m, UIImpactFeedbackGenerator(.heavy) vibration is triggered. Haptic feedback is a standard borrowed from AirTag.

Tracker based on DW3000 for standalone solution

For a standalone tracker without MFi, we use the Qorvo DWM3001C — a ready UWB transceiver with BLE. The firmware implements the UWB Initiator role, exchanges the token via BLE, and responds to TWR requests from the phone. On Android, a similar experience is provided by the androidx.core.uwb library:

val rangingParams = UwbRangingParameters(
    uwbConfigType = UwbRangingParameters.CONFIG_UNICAST_DS_TWR,
    complexChannel = controllerScope.uwbComplexChannel,
    peerDevices = listOf(UwbDevice.createForAddress(trackerUwbAddress)),
    updateRateType = UwbRangingParameters.RANGING_UPDATE_RATE_FREQUENT,
    sessionKeyInfo = sharedSessionKey
)

What is included in a turnkey UWB solution?

Our team, with 5+ years of experience and over 50 BLE/UWB projects, offers:

1. Requirements analysis and hardware platform selection (DW3000, NXP, or custom).
2. Design and development of UWB tracker firmware.
3. Creation of mobile app for iOS (Swift, NearbyInteraction) and Android (Kotlin, UWB API).
4. Integration with accounting systems (1C, SAP, custom API).
5. Security architecture design (session key encryption).
6. Accuracy and stability testing in real conditions.
7. Documentation and personnel training.

We guarantee accuracy up to 10 cm even in high-interference environments. Verify it yourself — order a pilot project.

Get a consultation — we will assess your task and propose optimal hardware.

Timelines

A mobile app with UWB functionality (with a ready tracker) — from 1 to 3 weeks. Full cycle: tracker firmware + app + integration — from 1 to 3 months. Cost is calculated individually based on the number of supported devices and API scope. Contact us to discuss details.

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.