UWB Integration with Nearby Interaction in iOS Apps

UWB (Ultra Wideband) — not Bluetooth, not iBeacon, not GPS. It's a technology with sub‑meter precision: the app receives distance in meters with ±10–15 cm accuracy and direction — a 3D vector to the device in space (on iPhone 14 Pro and later via bidirectional antennas). UWB is essential for precise pointing in file sharing and payments, lost item search (like AirTag), smart home control, and AR apps with spatial anchoring. It provides 10x better accuracy than Bluetooth (10 cm vs 1 m). We have extensive experience developing iOS apps with UWB and ensure compliance with App Store Review Guidelines and data privacy. With 5+ years of experience and 20+ completed UWB projects, we guarantee reliable integration.

A UWB session requires user permission (NSNearbyInteractionAllowOnceUsageDescription), and Apple strictly controls the use of location data. Testing UWB is only possible on physical devices — the simulator does not support the U1/U2 chip. Therefore, we conduct testing on real iPhones, guaranteeing correct operation.

UWB vs Bluetooth: Key Differences

Bluetooth provides accuracy of about 1 meter and does not determine direction. UWB is 100 times better for precise distance measurement — ±10 cm vs. 1 meter, which is critical for indoor navigation and AR. For example, UWB is 100x better than Bluetooth for precision. However, UWB only works at distances up to 9 m, does not support background mode, and requires line of sight. The choice of technology depends on the scenario: for broad coverage — Bluetooth, for pinpoint operations — UWB.

UWB integration process

The core component is NISession. Create a session, set the delegate, and run with a NINearbyPeerConfiguration. The code below demonstrates a basic implementation:

import NearbyInteraction
import MultipeerConnectivity

class UWBSessionManager: NSObject, NISessionDelegate {
  private var niSession = NISession()
  private var peerToken: NIDiscoveryToken?

  override init() {
    super.init()
    niSession.delegate = self
  }

  func startSession(with peerToken: NIDiscoveryToken) {
    let config = NINearbyPeerConfiguration(peerToken: peerToken)
    config.isCameraAssistanceEnabled = true
    niSession.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 {
      print("Direction: \(direction)")
    }
  }

  func session(_ session: NISession,
               didInvalidateWith error: Error) {
    // Error handling
  }
}

Token Exchange via MultipeerConnectivity

The most common P2P approach: use MCSession to transfer the token, then launch NISession. Important: NIDiscoveryToken cannot be transmitted as a string — encode via NSKeyedArchiver:

let tokenData = try NSKeyedArchiver.archivedData(
  withRootObject: niSession.discoveryToken!,
  requiringSecureCoding: true
)
mcSession.send(tokenData, toPeers: peers, with: .reliable)

On the receiving side:

let token = try NSKeyedUnarchiver.unarchivedObject(
  ofClass: NIDiscoveryToken.self,
  from: data
)

Attempting to send the token via JSON does not work — NIDiscoveryToken is not Encodable.

Common Problems During Integration

Error handling is a critical part of the session. Here are typical errors and their solutions:

Why Camera Assistance Matters

On iPhone 14 Pro and 15 series, the mode isCameraAssistanceEnabled = true is available. The system displays a native AR overlay with a direction pointer. It activates only when camera permission is granted. Adds a ~200 ms delay until first direction data is received, but significantly improves user experience.

What's Included in the Work

• Scenario analysis and device capability check (NIDeviceCapability)
• Architecture design: choosing the token exchange method
• Implementation of NISession with P2P or accessory configuration
• Real-time distance/direction update handling
• Testing on two physical devices (simulator does not support UWB)
• Deployment in compliance with App Store Review Guidelines
• Full documentation and source code delivery
• Post-deployment support and developer training
• Access to our team for questions and updates

Our team has over 5 years of experience with Nearby Interaction framework and has successfully delivered 20+ UWB integration projects. Our fixed‑price model saves you up to 30% compared to hourly billing.

UWB Integration Steps

1. Analysis — review the scenario, check compatibility.
2. Design — choose the token transmission method (MultipeerConnectivity, Bluetooth, REST).
3. Implementation — write NISession with configuration and delegate.
4. Test — run on two real devices (simulator does not support UWB).
5. Deploy — publish following App Store rules.

UWB Integration Timelines and Cost

Approximately 5 days for a typical P2P project with MultipeerConnectivity: 1 day analysis and architecture selection, 2 days session implementation and token exchange, 1 day testing on two physical iPhones, 1 day documentation and handover. For projects with accessories (third-party UWB chip) or Camera Assistance AR overlay, the timeline increases to 7–8 days. Cost is calculated individually after scenario analysis. Starting price: $2,500 (≈€2,300). Contact us — we will evaluate your project and propose the optimal solution.

Get a consultation on UWB integration — we'll help solve your task with sub‑meter precision. If you need UWB implementation, contact us for a project evaluation.

Nearby Interaction Documentation — official Apple documentation

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.