Integrating UWB for Indoor Navigation in Mobile Apps

Precise Indoor Positioning: The Role of UWB and Its Capabilities

We integrate UWB (Ultra-Wideband) for precise positioning in mobile applications. GPS does not work indoors — that is well known. Bluetooth Low Energy offers 1-3 meter accuracy at best. Wi-Fi RSSI triangulation gives 2-5 meters with high instability. UWB — a technology with 10-30 centimeter accuracy based on measuring radio signal propagation time (Time of Flight / Two-Way Ranging). This is what Apple built into iPhone 11+ via the U1 chip, and what gives AirTag the precision of "your bag is here, turn right." Our team has 10+ years of experience in mobile solution development, and we guarantee a turnkey UWB integration. Get a consultation on selecting UWB equipment for your facility.

Why UWB Is Better Than BLE and Wi-Fi for Indoor Navigation

UWB provides accuracy 10 times better than BLE, as confirmed by our projects for shopping malls and warehouses.

How UWB Works and What It Means for Developers

UWB uses pulses ~500 MHz wide in the 6-8.5 GHz range. The signal propagation time between two devices is measured with nanosecond accuracy (TWR — Two-Way Ranging, or TDoA — Time Difference of Arrival). Distance is calculated from time: 1 ns ≈ 30 cm.

For an indoor positioning scenario, you need anchors — UWB beacons with known coordinates — and a mobile device (tag). Based on measured distances to at least three anchors, the position is calculated via trilateration.

Supported Devices

iOS: Apple NearbyInteraction framework. Devices with U1/U2 chip: iPhone 11–15, iPhone SE 3rd gen, AirTag, HomePod mini 2, Apple Watch Ultra. NISession is the main class. One session = one device pair. For positioning relative to multiple anchors, use multiple parallel NISession instances.

Android: UwbManager from Jetpack Core UWB (androidx.core:core-uwb). Supported devices: Samsung Galaxy (S21 Ultra+, S22+, S23, S24, Z Fold3+), Pixel 6 Pro+, some Xiaomi. Check support: UwbManager.isAvailable().

UWB anchors (hardware): For infrastructure positioning, third-party anchors are needed: Qorvo DWM3000EVB, Decawave DWM1001, Sewio RTLS, Pozyx. They communicate via IEEE 802.15.4z and have SDKs for configuration.

Platform Comparison: iOS vs Android

Platform Limitations

Apple Nearby Interaction is peer-to-peer only between two Apple devices or with MFi-certified accessories. For infrastructure indoor positioning (anchors → phone) directly via NISession, it works only with Qorvo-compatible anchors via a special NIConfiguration.

NISession requires exchanging NIDiscoveryToken between devices beforehand — typically via Multipeer Connectivity, Bluetooth, or a server. After token exchange, NISession.run(configuration:) starts measurements.

How to Integrate UWB into a Mobile App?

Practical Case: Navigation in a Shopping Mall (from Our Practice)

Scenario: a shopper looks for a specific store. GPS is unavailable. BLE navigation is not accurate enough for 3-meter-wide corridors. UWB anchors are installed on the ceiling every 10-15 meters.

Pozyx Creator anchors (UWB, PoE, self-localization) → central Pozyx server collects positioning data → REST API provides tag device coordinates in the building's coordinate system.

Mobile app: upon entering the building, the device "connects" to the system (via BLE handshake for identification), then every 100-200 ms receives coordinate updates via WebSocket (x, y, floor).

Coordinates are overlaid on the building plan (SVG floor scheme). Smooth marker movement: Kalman filter to smooth noisy UWB measurements. Without the filter, the marker "jumps." A Kalman filter on the mobile device is 20-30 lines of code but significantly improves UX.

Navigation to a point: A* pathfinding on a graph of passages (the graph is built from the SVG scheme, with forbidden zones — walls and display cases). If deviation from the route exceeds 1m, recalculate.

Integration with Apple NearbyInteraction

For device-to-device scenarios (courier → client, warehouse worker → specific pallet):

import NearbyInteraction

class UWBSession: NSObject, NISessionDelegate {
    let session = NISession()

    func startSession(with peerToken: NIDiscoveryToken) {
        session.delegate = self
        let config = NINearbyPeerConfiguration(peerToken: peerToken)
        config.isCameraAssistanceEnabled = true // iOS 16+: AR overlay
        session.run(config)
    }

    func session(_ session: NISession, didUpdate nearbyObjects: [NINearbyObject]) {
        guard let peer = nearbyObjects.first else { return }
        if let distance = peer.distance {
            print("Distance: \(distance) m")
        }
        if let direction = peer.direction {
            // SIMD3<Float> - direction in 3D
            print("Direction: \(direction)")
        }
    }
}

isCameraAssistanceEnabled enables Precision Finding — an AR arrow over the camera shows direction to the object (like in AirTag Precision Finding). Requires ARKit and NSCameraUsageDescription.

Token Exchange

NIDiscoveryToken cannot be created programmatically — only obtained from session.discoveryToken. To start a UWB session, both devices must exchange tokens beforehand. Typical scheme: both devices publish the token via Bluetooth Peripheral → scan each other → receive tokens → start NISession.

Using CloudKit or a server — for scenarios where devices are not physically close during initialization.

Typical Integration Problems

• Multipath interference. UWB signal reflects from metal surfaces (shelves, equipment) — false distance measurements. Solution: NLOS (Non-Line-of-Sight) detection via analysis of First Path Power vs Total Received Power. Pozyx and Decawave return these metrics in the raw packet.
• NISession suspended. iOS pauses the UWB session when the app goes to background. sessionWasSuspended(_ session:) — save last position; on sessionSuspensionEnded, restart. UWB does not work in background — platform limitation.
• Anchor calibration. Anchor coordinates in space must be measured precisely — a 5 cm error shifts all calculations. Self-localization of anchors (Pozyx, Sewio) automatically determines their coordinates at first startup via UWB TWR between themselves.
• Accuracy in motion. At high speed (> 2 m/s), TDoA systems give more errors than TWR. For pedestrians, TWR with 10 Hz update is sufficient.

What Is Included in the Work?

• Audit of infrastructure and use scenarios
• Selection of UWB platform and equipment
• SDK integration (iOS NearbyInteraction, Android UwbManager, anchors)
• Kalman filter and navigation graph development
• Load testing (up to 100+ devices)
• Documentation, support, and team training

Project Process

1. Audit of use scenario and equipment
2. Selection of UWB platform (Apple NI / Qorvo / Pozyx)
3. Pilot on a test zone with accuracy measurement
4. Integration with the mobile app
5. Kalman filtering and navigation graph
6. Load testing (100+ simultaneous devices)
7. Anchor deployment and commissioning

Timeline

A pilot with Apple NearbyInteraction on two devices takes 1-2 weeks. A full indoor navigation system with infrastructure anchors, Kalman filter, and building map takes 2-4 months depending on the facility's scale. The cost is calculated after assessing the infrastructure and target scenarios.

Contact us for a consultation on your project. Order a turnkey UWB integration — get precise indoor positioning.

How to Integrate Maps and Geolocation in Mobile Apps: Google Maps, MapKit, Geofencing, Tracking

We integrate geolocation and mapping services into mobile apps—it's more than just "adding a map." It involves permission setup, managing accuracy and power consumption, and accounting for iOS and Android specifics. Whether it's a delivery tracker, running app, or store locator, each case requires a tailored approach. Contact us for a free project assessment within 2 hours.

Permissions: One of the Most Common Sources of Bad Reviews

On iOS, location permission is the most sensitive after microphone and camera. Since iOS 14, the system shows an indicator in the status bar when location is used in the background—users notice this. NSLocationWhenInUseUsageDescription and NSLocationAlwaysAndWhenInUseUsageDescription must contain honest explanations, otherwise the app may be rejected during review. Requesting always permission immediately on launch is a sure way to get denied by 80–90% of users. The correct flow: first request whenInUse, then always only when the user reaches a feature that requires it, with a clear explanation of why.

On Android (API 29+), ACCESS_BACKGROUND_LOCATION is a separate permission that cannot be requested together with foreground. First request foreground permission, then background separately. Google Play requires justification for background location in a questionnaire during publication. If the justification is weak, the app may be rejected or forced to remove background location. Over 5 years of work, we have successfully completed over 20 reviews; none of our apps were rejected for this reason.

Accuracy and Power Consumption: How to Avoid Battery Drain

Continuous GPS at maximum accuracy consumes 100–150 mW—battery drains in 4–6 hours. For most tasks, this is excessive.

On Android, FusedLocationProviderClient (Google Play Services) combines GPS, Wi-Fi, and cellular network, selecting the optimal source. LocationRequest.Builder with priorities:

• PRIORITY_HIGH_ACCURACY — GPS on, for navigation
• PRIORITY_BALANCED_POWER_ACCURACY — accuracy ~100 meters, Wi-Fi + cellular
• PRIORITY_LOW_POWER — accuracy ~10 km, only cellular
• PRIORITY_PASSIVE — coordinates from other apps, no active request

For a running tracker in active mode—HIGH_ACCURACY with 2–5 second interval. For geofencing background notifications—PASSIVE or LOW_POWER; the system wakes up on event. GPS accuracy is well-documented.

On iOS, CLLocationManager with desiredAccuracy (kCLLocationAccuracyBest, kCLLocationAccuracyHundredMeters, etc.) and distanceFilter—minimum movement in meters before next update. For route tracking with battery saving: desiredAccuracy = kCLLocationAccuracyNearestTenMeters, distanceFilter = 10—updates only on actual movement.

Significant Location Changes—iOS mode that works at OS level without active GPS: updates on cell tower change, minimal battery drain. Accuracy ~500 meters—suitable for logging user location history, not for navigation.

How to Choose a Mapping SDK? Comparative Analysis

Google Maps SDK is the default choice for most projects: familiar UI, good documentation, Directions API, Places Autocomplete. Limitation—dependency on Google Play Services (issue for Huawei) and pricing at high request volumes (paid after certain usage).

Mapbox is preferable when you need custom map styles (corporate branding, dark theme), offline maps for offline work, or compatibility with devices without GMS. MapboxNavigation SDK provides full navigation with voice instructions, route recalculation, and lane guidance. Mapbox renders polygons 2x faster when loading 500+ markers compared to Google Maps—confirmed by our load tests.

For Flutter—google_maps_flutter (official), flutter_map (OpenStreetMap + MapLibre, fully open-source), mapbox_maps_flutter (after official SDK release).

Example: App with Offline Maps and Geofences for 100+ Points

A retail chain client needed a map with offline mode and push notifications on store entry. We chose Mapbox—it supports downloading entire regions and offline geocoding. Result: zero network failures, 30% battery reduction due to PASSIVE mode.

Why Does Geofencing Have Delays?

Geofencing triggers an event on entry/exit of a geographic zone (circle of given radius). In practice, delay can be 1–3 minutes—the cost of energy efficiency.

On Android—GeofencingClient from Google Location Services. Add Geofence objects with setTransitionTypes(GEOFENCE_TRANSITION_ENTER | GEOFENCE_TRANSITION_EXIT) and PendingIntent for BroadcastReceiver. Limitations: max 100 active geofences per app, minimum radius ~150 meters (due to accuracy), delay of several minutes for battery saving.

On iOS—CLCircularRegion + CLLocationManager.startMonitoring(for:). Limit: 20 regions per app. The OS decides when to check—developer cannot control delay. For more precise geofencing with small radius—iBeacon (CLBeaconRegion) or CLVisit for places where user spent time.

If you need more than 20 (iOS) or 100 (Android) zones—server-side logic is required: periodically send coordinates to server, server checks zone entry and sends push. Less time-accurate but scales to thousands of zones. Geozone working principles are well-documented.

Route Tracking and Background Geolocation

Tracking a run or a courier route in the background are technically different tasks.

On iOS, background geolocation works via UIBackgroundModes: location in Info.plist. Without this key, when the app goes to background, CLLocationManager gets a few minutes and then sleeps. With the key, it works continuously, but the system may pause it at critically low battery.

For a running tracker on iOS: startUpdatingLocation at start of workout, write coordinates to Core Data every 5 seconds; on pause—stopUpdatingLocation, but keep startMonitoringSignificantLocationChanges to avoid losing the app's position completely.

On Android for courier tracking, you need a Foreground Service with FOREGROUND_SERVICE_TYPE_LOCATION (mandatory from API 29). Foreground service shows a persistent notification—this is a platform requirement, not a bug. Without it, Android Doze will kill location updates. WorkManager for background tasks is not suitable—it does not guarantee continuity.

Algorithmic part of route tracking: raw GPS coordinates are noisy. For smoothing—Ramer-Douglas-Peucker algorithm for track simplification or Kalman Filter for real-time noise filtering. Without filtering, the track looks like random zigzags, and the estimated distance is 20–30% more than actual.

How We Implement Maps and Geolocation: Step-by-Step Process

1. Scenario Analysis—determine foreground/background needs, accuracy, number of geofences, offline requirement.
2. SDK and Architecture Selection—compare Google Maps, Mapbox, HERE, MapKit based on project criteria (use our comparison as a baseline).
3. Integration and Permission Setup—configure Info.plist / AndroidManifest.xml, test review checks (App Store Review Guidelines Sections 4.2/5.1, Google Play policy).
4. Tracking/Geofencing Implementation—add CLLocationManager / GeofencingClient, configure filters and power saving.
5. Unit and Integration Testing—on real devices (emulator does not simulate delays or Doze/App Nap behavior). Test at least 50 scenarios.
6. Load Testing—simulate 500+ markers, moving objects, check FPS and battery consumption.
7. Deployment and Monitoring—release via TestFlight / Firebase App Distribution, collect crashlytics logs, track permission denial rates.

Timeline and Deliverables

What you get in any case:

• Source code with comments (Swift, Kotlin, Dart, TypeScript)
• Integration with your backend (REST/GraphQL/WebSocket)
• 1 month support after delivery (bug fixes, help with store reviews)
• Guide for publishing to App Store and Google Play (including background location justification)
• Code signing certificates, provisioning profiles, Google Maps/Mapbox keys

Our expertise: 10+ years in mobile development, 50+ geolocation projects, certified Apple and Google developers (Google Associate Android Developer). Every app undergoes triple code review and load testing.

Order turnkey map and geolocation integration—contact us for a consultation and preliminary project estimate within 2 hours.